WDS - When to use different install and boot images


i curious, following thread , came issues.

http://social.technet.microsoft.com/forums/en-us/windowsserver2008r2general/thread/ec32faf5-6488-4dcc-a3e6-dce284f200c7/

everytime try capture 2003 server, used windows 2008 (non r2) disc boot image from, finish install , right when windows symbol coming start windows. bluie screens on me. im guessing hardware drivers. try attach driver groups x86 version or x64 version, whichever verion im trying capture @ time , not allow me add driver packages. option greyed out. on boot images 2008 servers option not greyed out.

i'm trying figure out how make image (with boot.wim server 2008 disc) , capture 2003 server image , deploy other servers. have been working on awhile , have come nothing. missing?

 

note: using vsphere test these deploys , captures

i have tested on physical servers , have had still no luck 2003 installs 2008 capture/deploys work.

i tried create answer files (which don't know with) , sysprep 2003 servers in different ways still no luck.

 

steps replicate problem:

 

on wds server:

go add boot image file, select boot image windows server 2008 (non-r2) disc

check rest of appropriate boxes.

the create capture image boot image.

fill out appropriate boxes , prepare 2003 server capture.

on server:

load windows server 2003 x86/x64

load updates

add in roles : iis, application services, file services. check more updates if any.

copy deploy.cab server 2003 disc , extract files root , run either:

 

sysprep: hit reseal , make capture capture image.

or

setupmgr.exe: fill out want show on unattended install , save inf file same deploy.cab folder.

then run sysprep

 

once shutdown reboot , capture image, make machine ready , load image on , blue screen.

eric,
have couple suggestions hope help. first, correct; first time windows attempts start cannot locate compatible mass storage drive in critical device database getting 0x0000007b. there no servicing in window xp/2003 have list names of mass storage controller drivers want included in image. not related vmware either. can manually walk through process of building reference image , manually adding drivers sysprep.inf, yes, there better way. download , use free tool microsoft deployment toolkit 2010 update 1. customers starting rollouts of windows 7/r2 , deployment process has changed quite bit. also, have no quality control in doing, there should no manual steps referencing spreadsheet, not efficient use of time, mdt solution accelerator designed automate deployment , capture of images, should running sysprep 1 time. toolkit not make things easier can integrate wds.


recommend evaluate toolkit save loads of time in future. there number of videos , blog should how started , if want can install toolkit on wds server.

 

 


dave guenthner [msft] posting provided "as is" no warranties, , confers no rights. http://blogs.technet.com/b/davguents_blog


Windows Server  >  Setup Deployment



Comments

Popular posts from this blog

WIMMount (HSM) causing cluster storage to go redirected (2012r2 DC)

Failed to delete the test record dcdiag-test-record in zone test.com

Azure MFA with Azure AD and RDS