1. VMware hardware meeting minimum specs and 2 NIC ports recommended:
   http://www.netdevgroup.com/ae/vmware.htm

2. Install Windows Server 2003 (recommended for VMware Server)

3. Install VMware Server (free):
   http://www.vmware.com/products/server/

4. Review the VMware Remote PC Guide (vmPC_Gd for short)
   http://www.netdevgroup.com/doc/NETLAB_VMware_Remote_PC_Guide.pdf
   a. Create NETLAB user account for VMware API (vmPC_Gd sec5.3)
   b. Grant the permissions for Virtual Machines directory (vmPC_Gd sec5.4)

5. a. If your hardware has 2 NIC ports reference vmPC_Gd sec4.2
   b. If your hardware has 1 NIC port reference vmPC_Gd sec4.3
   c. Make sure to install the Intel driver supporting 802.1q as per vmPC_Gd sec5.1

6. a. Focus on installing one PC first (install the VM O/S and set up in NETLAB pod)
   b. Create a new Virtual Machine (custom install)
      MAKE SURE TO SELECT THE EXACT SETTINGS AS PER vmPC_Gd sec6.1
      MAKE SURE TO SELECT THE EXACT SETTINGS AS PER vmPC_Gd sec6.1
      MAKE SURE TO SELECT THE EXACT SETTINGS AS PER vmPC_Gd sec6.1
      (80% of permissions and/or API failures result from a mis-configured setting from this section)
   c. Make sure the virtual NIC for the newly created VM is configured as per vmPC_Gd sec6.2
   d. A good practice is disabling the CD-ROM drive for each virtual machine you create
      Goto the CD-ROM from Hardware menu and uncheck "Connect at power on"
   e. Review the snapshot feature and set properly as per vmPC_Gd sec6.3
   f. Install the O/S (vmPC_Gd sec6.4)
   g. Install VMware tools (vm PC_Gd sec6.5)
   h. Make sure display properties of the VM are set correctly (vmPC_Gd sec6.6)
   i. This is a good point to save your work with a snapshot (vmPC_Gd sec6.7)

7. Configure the NETLAB pod settings and add the VNC lines to the VMX file
   a. Review sections 6.9-6.11 very thoroughly
   b. Make sure to take a new snapshot after adding the VMX file settings in vmPC_Gd sec6.10

8. Review the proper pod-specific guide (depends on which pod you installed):
   http://www.netdevgroup.com/ae/documentation.htm
   Now that the pod test passes and VNC is correctly configured, we need to verify the network connectivity
   a. Determine which VLAN ID# is assigned for this PC
      i)   For BRPv2 pods reference BRPv2 Guide sec7.2
      ii)  For BSPv2 pods reference BSPv2 Guide sec7.2
      iii) For other pods that use PC's there will be similiar section guidance
   b. Create this VLAN ID# from the VLAN pool to the VMware Server trunking port as per vmPC_Gd sec5.1
      MAKE SURE THE VLAN ADAPTER YOU CREATE HAS TCP/IP DISABLED
      MAKE SURE THE VLAN ADAPTER YOU CREATE HAS TCP/IP DISABLED
      MAKE SURE THE VLAN ADAPTER YOU CREATE HAS TCP/IP DISABLED
      i)   For BRPv2 pods reference BRPv2 Guide sec7.3
      ii)  For BSPv2 pods reference BSPv2 Guide sec7.3
      iii) For other pods that use PC's there will be similiar section guidance
   c. Bind this VLAN to the appropriate VMnet
      i)   For BRPv2 pods reference BRPv2 Guide sec7.4 - 7.5
      ii)  For BSPv2 pods reference BSPv2 Guide sec7.4 - 7.5
      iii) For other pods that use PC's there will be similiar section guidance
   d. Configure the control switch port that connects to the VMware trunking port
      i)   For BRPv2 pods reference BRPv2 Guide sec7.6
      ii)  For BSPv2 pods reference BSPv2 Guide sec7.6
      iii) For other pods that use PC's there will be similiar section guidance
   e. PC pods that contain lab switchs must have additional control switch commands.
      i)   For any switch pod with PC support reference CSP Guide sec8.2
      ii)  Add these 5 commands to each CS port touching a lab switch
   f. If the VMware Server is on a different control switch than the lab devices
      i)   For BRPv2 pods reference BRPv2 Guide sec7.7
      ii)  For BSPv2 pods reference BSPv2 Guide sec7.7
      iii) For other pods that use PC's there will be similiar section guidance