ashleyoneill

yes its really annoying because i like the way WDS works and dont like BDD as it seems to be a bit of a tacky tool

the answer to this is use BDD 2007 to deploy vista machines in an enterprise environment. WDS alone does not have the ability to support a domain based environment properly when building machines in respect to naming them.

slmgr -ilc <<name of cert>>.XRM-MS that command will install the certificate. You could put the product key in the unattend.xml and then also run the above command using the sychronous command setting either in specialize or oobe from the unattend.xml

lol trust me even broken WDS is better than ghost

still no-one has an answer on this ?

Hi, I have not used BBD2007 at all. Im using pure Vista images ripped from the DVD and using the unattended install xml files. If you have setuip an environment from scratch i dont see how you cant get it to work

Hi, I have not used BBD2007 at all. Im using pure Vista images ripped from the DVD and using the unattended install xml files. If you have setuip an environment from scratch i dont see how you cant get it to work

Hi, since im only using RIS and WDS in a test environment at the moment i will explain the process i went through. 1.Installed 2003 Server and setup all the pre-reqs to run RIS. (AD,DHCP, ETC) 2.Installed 2003 Server R2 3.Added a RIS Image 4.Installed 2003 Server SP2 5.Configured WDS 6.Added images etc This worked perfectly first time and when u do a network PXE boot you get the option to select between Remote Installation Services and and WDS Boot Images you have added.

i have RIS and WDS working together quite happily. hope you fix the problem.

has anyone got any further with this? in our environment i need to be able to add machines to the domain with a name specified by the engineer like you could with RIS.