1. Download Serva
2. Run the download to unpack the files and copy the Serva files to any convenient folder on your Windows hard disk
3. Create a C:\SERVA_ROOT empty folder
4. Run Serva.exe and click on the Settings button at the bottom (if you get a Windows FireWall warning then ALLOW the program access through the firewall)
5. Click on the TFTP tab and set the Root directory to C:\SERVA_ROOT and tick the TFTP Server box as shown below:
6. Click on the DHCP tab and set proxyDHCP (if you already have a DHCP server or DHCP router)and tick the BINL box.
7. Quit the app and re-run the Serva.exe app again.
This is necessary because when Serva re-starts it will generate the PXE download files according to what folders you have created. Serva only does this when it starts. If you make any changes to the folders under C:\SERVA_ROOT then you should always quit and re-run Serva before you try a PXE boot.
8. Check that there are now some folders underneath the C;\SERVA_ROOT folder
10. Copy the contents of your Windows 7 (or Win8-10 or Vista or Server 2K8R2) DVD to a new folder – e.g. copy a Win 7 SP1 32-bit install DVD to C:\SERVA_ROOT\WIA_WDS\Win7_32_SP1
11. If you have more DVDs, just make a new folder for each of them under C:\SERVA_ROOT\WIA_WDS
13. Quit the Serva app and re-run it
14. Now try to PXE boot your target system
15. For a WDS install (Vista, Win7,Win8, SVR2K8R2), you will be prompted for a username and password – use your host PC computername\username and password – e.g. mynewHP\Administrator myhppwd.
That’s it – now try to PXE boot a system over Ethernet.
I would recommend using a Windows 7 or 8 32-bit install folder (copy of the install DVD) to start with as these will have the most network drivers in them already and will work on any CPU. The troubleshoooting documentation on the Serva website explains how to add OS network drivers if the standard Microsoft install files do not already contain the correct network driver for your target systems.
After connecting the network cable, watch the Windows SystemTray network icon – wait until the icon animation has stopped (usually 1-2 minutes) before you attempt to start Serva.
If you having problems, try disabling the Windows Firewall on your PC and temporarily stopping your Anti-Virus protection,.
If you are using a router as a hub, disconnect any other Ethernet cable except for the target PXE system and your Serva Windows PC.
Try a different PXE client notebook or PC – some PXE BIOSes are buggy (not all PXE BIOS ROMs support proxyDHCP PXE booting)!
If it starts to load the OS installation files and then stops with an error message – see here.
If the client is having communication problems with the Serva host PC (e.g. PXE client is not receiving the DHCP offer or lots of timeouts, etc.) try switching off and on your router – if still no joy, switch off your host PC, client PC and router. Then switch on the router, wait 1 minute and the switch on your host PC. Now try again!
Note: grldr and grub.exe will not work if the PXE server is using proxyDHCP mode. Grub4dos does not currently support this feature. To use grub4dos your PXE server must also be the DHCP server (i.e. do not use proxyDHCP mode and disable your DHCP server services whilst Serva is running).
Use Oracle VM VirtualBox to PXE boot from Serva
You can PXE boot using Oracle VM Virtual Box to test that PXE booting is working.
1. Add a new Virtual machine which has a virtual hard disk that you can install the OS onto.
2. Set up the Network Adapter to Bridged and set the Name to the physical network adapter on your host system (see below).
Note that Windows XP will require the correct network driver to be added. See the Serva website for instructions.
You can now install XP or Win7 to your virtual hard disk (if you wish).
Win7 logon pop-up. You may need to add the correct Win 7 network drivers if they are not already in Win 7 WinPE.