shariq77

Annnnnnnnnnnnnnnnd......... we are in business Finally got the Windows 2008 installation kicking through WDS The problem was MS Virtual Server. there was no issue in my setup or boot file. Thanks for the help Tripredacus. it is much appreciated.

I have moved to vmware today..... the windows loading screen which was taking more than an hour on Microsoft Virtual Server is now taking 1 minute on VMWare Previously on MS Virtual Server I was only able to run 3 to 4 tests per day, now I can run as many as I want Win 2008 booted successfully and gave the error of missing Network Card Driver this time.... which is acceptable..... I'll put the netowrk card driver in the image and will be back to post my findings.

I put boot.wim and install.wim from Vista x86 DVD and the result was same, except that it was giving me error that it cannot contact the WDS Server. then I booted with Win 2008 boot.wim came back to error of initializing WDS Mode. Press SHIFT+F10. run ipconfig command. Now, my DHCP Server is configured to assign ip's between 10.0.1.1 to 10.0.1.10 but the IP acquire by Server at WDS initialization error is 10.237.0.17. (strange) IP Assigned at the time of PXE Boot was 10.0.1.1 according to ipconfig /all DHCP server used was 10.237.0.1 It has virtual ethernet card of Intel 21140-Based PCI Fast Ethernet Adapter (Emulated) With IP Address Assigned as 10.237.0.17 (Preffered) I cannot ping DHCP Server 10.237.0.1 I dont have any other server on this virtual link except my DC and client. then I run this command to set the ip on client pc netsh interface ip set address "Local Area Connection" static 10.0.1.1 255.255.0.0 10.0.0.1 1 and now i can ping my WDS Server from client but cannot ping my client from WDS Server atleast there is no issue with the ethernet card driver.

My RemoteInstall folder is on C drive, should I move it to some other partition?

I installed WAIK and install the winpe.wim from its PETools\x86 folder as a boot image in WDS. Now there are 2 boot images in WDS. I've changed the default boot image in options as put the new image in both x86 and x64 Now while booting the client pc it show me the selection menu for boot images, I selected the VISTA PE. After loading, it is showing a command prompt with 2 entries X:\Windows\system32> wpeinit X:\Windows\system32> I think my troubleshooting is off the road now as I dont know what does this means?

1. I am using Windows Server 2003 Enterprise Edition 32 bit with SP2 2. Windows Server 2008 is also 32 bit 3. I got the WIM from the Windows Server 2008 DVD sources directory (following standard procedure for adding image files in WDS), I am not doing unattended installation 4. both DC and client have 512 MB of RAM 5. in WDS cpl, in "Boot Images", boot image was picked automatically when i install the images, also in boot option in WDS properties i have "Boot\x86\images\boot.wim" for both x86 and x64 I am trying to follow your guide right now... I am not using AIK... i have enabled WDS from add remove programs as I have SP2 installed

hi, I am trying to setup WDS in NATIVE mode on Windows 2003 SP2 on virtual server 2005 I am trying to install Windows 2008 on client pc using WDS My Client PC (on virtual server) is booting with PXE option enabled. Host PC is a DC with DHCP Server and WDS. I have option 060, 066 and 067 enabled on DHCP Server. WDS Server settings: in DHCP Tab, Do not listen on port 67 and configure DHCP option 60 to PXEClient are checked. also Do not create account in the domain is also checked in client tab. It took around 1 hour for the client to load windows setup screen after pressing F12 for network service boot, also as the windows loads, it gave me error "WdsClient: There was a problem initializing WDS mode." WDSMGMT.log and WDSServer.log are attached WDSMGMT.log.txt WDSServer.log.txt