jtsm

I took some time but we worked out what was causing our issue. (We had progressed on a different server) Our original test server was a HP DC7700p desktop with Inte VPro Nic, running Windows Server Standard 2003 R2. This appears to be a volitile combination and the NIC has data flow problems with this model and OS. changed network cards and the install now takes 10 minutes, compare to 3 days. BTW - I did try chunking the WIm files down to 300 MB parts and it did improve the load time to 1.7 days. So shows that it does help. But have seen no reason to do this while fully functional. Thanks for the hand... jtsm

I've been testing on a D7700p, D7100 and D530. But I have a setup issue with the performance at the moment and and the 7700 failed. But this isdue to imaging taking three days. (I let it run over the weekend). Once I fix the network issues, I can further testing. The D530 has 256MB ram, and have been testing with XP deployments, then will move to Vista.

Thanks, We are runing WDS in mixed mode with RIS, I'll test switching this out and see if i can get some improvement.

Just wanted to get a feel for how long it takes other people to deploy a WIM image. I have created a basic WinXpSP2 WIM image that is approx 1.6GB with no compression. Am deploying via WinPE\WDS. It is taking in excess of 10 hours to deploy an image to a PC. Any suggestions of what I can look at to help speed up the process or performance tips? Thanks, jtsm

I managed to work this one out for anyone else with this issues. To create the discovery image I first loaded the .\Sources\BOOT.wim file off a Vista installation. Then used that boot image to create the Discovery CD. jtsm

I'm having trouble creating a Windows PE Discovery Image, I go through the menu in WDS to create but get the following error at the end. "The image cannot be used to create a Discovery image as it does not have the required WDSClient binaries." has anyone else encountered this before or know what I am doing wrong? Thanks, jtsm

Do your physical adapters have the 'Virtual Machine Network Services' bind? If it is not.. you will need to log on as local admin, not a user account with admin rights.. then install.

Is there a way to make a Pinned menu default? So any new users that logon will get the modified pinned menu?