Problem:

Solution:

Problem:    

Solution:  

root@SRX# load replace terminal    
[Type ^D at a new line to end input]
interfaces 
    ge-0/0/0 {
        unit 0 {
            family inet {
                address 192.168.1.1/24;
            }
        }
    }
    ge-0/0/1 {
        unit 0 {
            family inet {
                    address 192.168.1.2/24;
            }
        }
    }
}
load complete
[edit]
root@SRX# commit

Problem:    

1. SRX 300 Series:
   
   {primary:node0}
    smj@SRX> request routing-engine login node 1
   
   
2. SRX 1500 Series:
   
   smj@SRX% rlogin -T node1

Fun with Virtual Smart Cards!

Outline:

Assumptions:

Virtual Smart Card Configuration:

tpmvscmgr.exe create /name VSC /pin prompt /puk prompt /adminkey random /generate

Reset the Virtual Smart Card:

tpmvscmgr.exe destroy /instance root\smartcardreader\0000

PINs, PUKs, and Keys:

1. Smart Card Personal Identity Number (PIN).  The PIN is essentially a password.  The PIN can be changed by the end user from any domain computer:
   
    CRTL-ALT-Delete → Change Password → Change PIN.
   
2. Smart Card Personal Unlock Key (PUK).  Windows locks the PIN after three unsuccessful attempts.  End users can use their PUK to unblock their PIN:
   
    CRTL-ALT-Delete → Change Password → Unblock Smart Card.
   
   The PUK is optional but I recommend it.   It's simply too easy to lock the PIN! 
   
   The PUK changes the PIN.  Keep the PUK safe and only use it when its absolutely necessary.
   
   In addition, Windows does not include native tools to change the PUK. In order to choose a new PUK, the virtual smart card must first be deleted (i.e., destroyed) and then recreated.  Of course, this process deletes all certificates on the smart card.
   
3. Admin Key.  The key benefit to the admin key is that it allows Administrators to generate certificate keys for enrolling-on-the-behalf of others.  Organizations that do not use enrollment stations should simply generate a random admin key.    

References:

Problem: 

• The Windows Update GUI provides a long list of KB updates.  
• Updates are organized by date and not by KB numbers.  
• It lacks a built-in search function! 

Figure 1.  Windows Update History: No search for you (CRL+F)!   :(

Solution:

wmic qfe list

wusa /uninstall /kb:xxxxx