Use LEFT and RIGHT arrow keys to navigate between flashcards;
Use UP and DOWN arrow keys to flip the card;
H to show hint;
A reads text to speech;
13 Cards in this Set
- Front
- Back
|
Step 1 |
Verify DHCP/PXE/TFTP services are running successfully. |
|
|
Step 2 |
Validate the Network boot is enabled in BIOS. |
|
|
Step 3 |
Disable Spanning Tree Protocol or enable Port Fast on any port the switch uses for PVS traffic. |
|
|
Step 4 |
Enable verbose mode under the bootstrap: When the target device boots, validate that it is getting an IP address connecting to the TFTP server. Run the following tftp command to test TFTP from the target device to the PVS server:tftp get ardbp32.bin Note: TFTP can be tested by installing TFTP protocol in a Windows 7 within Add Remove Windows Features, and within Windows 2008 in the Add Features server role. In a broadcast domain, only one PXE server can be configured. Some environments might have another third party software running the PXE protocol, such as Norton Ghost. Note: When using DHCP scope options, PXE Server does not need to be configured in an environment. If PXE or DHCP options fail to boot a device, configure a BDM file to test boot a target device. Configure BDM with a static IP address and it will bypass the DHCP Server. |
|
|
Step 5 |
On the server and target device, the following ports are used:If using a virtual machine, validate the Network Interface Card (NIC) used to connect to the PVS server at the top of the list of polling order of network cards. For the Stream service: UDP 6910, 6911, 6912, 6913, 6914, 6915, 6916, 6917, 6918, 6919, 6920, 6921, 6922, 6923, 6924, 6925, 6926, 6927, 6928, 6929, and 6930.For the console: TCP 54321 and 54322. TFTP: Port 69. |
|
|
Step 6 |
Disable the Windows Firewall on the target device and server. After verifying the firewall, open the ports: UDP 6890 – 6909 for communication between servers. |
|
|
Step 7 |
Uninstall the Antivirus software. After the target device boots, install the Provisioning Services (PVS) target software in private mode. |
|
|
Step 8 |
Verify you are able to ping the target device to the PVS server. Note: Use the IP address of the server rather than the Fully Qualified Domain Name (FQDN). |
|
|
Step 9 |
Disable IPv6 on the server and target device by editing the registry and modifying the following key:HKLM\SYSTEM\CurrentControlSet\Services\Tcpip6\Parameters\DWORD DisabledComponents = 0xff |
|
|
Image Creation Step 1 |
Remove hidden network cards from Device Manager. (Note: Do not remove hidden (ghost) Network Cards from a XenServer Target. Only remove them from Hyper-V, VMWare or Physical targets) |
|
|
Image Creation Step 2 |
Uninstall any software on the target device that configures a third party NIC driver, such as IBM Tivoli. |
|
|
Image Creation Step 3 |
If the target device or PVS Server is configured with bonded network cards, break the bond and test with only one NIC active. This will simplify the environment and validate if the bonding network cards could be causing an issue. |
|
|
Image Creation Step 4 |
If the environment is configured with vSphere 5 and using VMXNET3 drivers, either enable Interrupt safe mode in the bootstrap or upgrade to vSphere 5.1 or later. |
