Symptom: Command windows displays "Unable to determine server IP address from DHCP".
Solution: Add scope option 244 to DHCP. This is only going to resolve the issue for bootable USB or CD. It is also useful if you are PXE booting and system that is NOT running Microsoft DHCP. This setting replaces 66 (next-server or sname)
Symptom: Boot environment build fails after displaying blank command window for short period of time.
Solution: Check the hostname of the K2000 appliance, and make sure the K2000 appliance is accessible from the client.
Symptom: Client machine downloads the WinPE ISO file via TFTP, screen flashes, and client immediately reboots.
Solution: Client machine must have RAM of approximately 2x the ISO file size to boot via PXE. Increase RAM in the machine to 512MB or higher.
Symptom: Client machine displays command prompt instead of K2000 deployment UI.
Solution 1: Run ipconfig /all to verify that the client has a working network adapter and was able to get an IP address from DHCP. If no network adapters are listed, locate drivers for the machine's NIC, rebuild the boot environment, and try again.
Solution 2: If ipconfig shows that the client has a working network adapter and was able to get an IP address, verify the DHCP server configuration.
Run kgetdhcp 66 and kgetdhcp 244. One of these should print the IP address of the K2000 appliance. If neither print anything, check the DHCP server configuration and try again.
Solution 3: If the ipconfig and kgetdhcp settings are as expected, verify the reachability of the K2000 appliance from the client. Run ping %K2000_IP% to ping the K2000. If not, check networking and retry.
Solution 4: If ipconfig and kgetdhcp settings are as expected and the K2000 appliance is reachable, verify that the Y: and T: drives were mounted. Attempt to mount them again by running net use \\%K2000_IP%\petemp T: and net use \\%K2000_IP%\peinst Y:. If this succeeds, reboot the client and try again. If not, check network filtering for samba and try again.