| T O P I C R E V I E W |
| ervi |
Posted - 02/13/2012 : 07:47:44 AM
I got this weird situation where x64 Win7 refuses to boot after WDS deployment. On the final boot after deployment Win7 gives BSOD complaining about iastor.sys file. When same image is deployded manually ie. using imagex or by using SCCM everything goes well. So i guess its not the image but something in WDS. SATA drivers in WDS driver console has already been disabled.
Can you somehow collect client logs to server in wds...like you can do in mdt..or do one have to search setupperr.log in client machines.
Sorry Johan for bugging you with these guestions all the time :O) |
| 6 L A T E S T R E P L I E S (Newest First) |
| ervi |
Posted - 02/16/2012 : 03:50:19 AM
Ok it actually go sorted out...when i looked setupact.log i found that storage drivers were still injected to image. When drivers were disabled using WDS console in Drivergroup level (rather that at driver level) image booted up normally. Thanks Johan
And yes it was a Win7 DVD image
|
| arwidmark |
Posted - 02/14/2012 : 12:17:47 PM
Is this a custom image, or the Windows 7 DVD default install.wim?
Did you really delete all storage drivers from WDS before trying again?
/ Johan |
| ervi |
Posted - 02/14/2012 : 05:51:02 AM
I looked setupact.log and found errors when setup is trying to open \boot\bootmgr file...it seems to be missing.
What i also found is that unattend.xml used for x64 Win7 deployment seems to be created with WAIK 1 becouse it seems to name system volume with name Vista. Also when i open it in WAIK 2 WSIM it complains about structure of the answerfile.
I guess WAIK 1 was for Vista and WAIK 2 if for -> Win7 |
| arwidmark |
Posted - 02/13/2012 : 09:48:13 AM
Well, in the mean time I would recommend to use MDT 2010 Lite Touch and WDS, so that you have at leasy a standalone deployment solution.
/ Johan |
| ervi |
Posted - 02/13/2012 : 08:47:40 AM
SCCM 2012 is going to be used in our organization when its finally released. |
| arwidmark |
Posted - 02/13/2012 : 08:01:59 AM
I'm sorry, but you should not use WDS for deploying the os image (the actual OS deployment)... WDS strength, and where it should be used, is to enable PXE boot and multicast for the REAL deployment solutions (MDT, SCCM or third party). Meaning that WDS should only be used to start the deployment process, by downloading the boot image, and then each real deployment solution takes over.
If you still insist on using plain vanilla WDS you will eventually end up troubleshooting issues that the real deployment solution have already addressed.
To solve your current problem, delete the troublesome driver from the WDS console and try again. Setupact.log, dism.log, cbs.log and setupapi.dev.log can help you troubleshoot the issue.
/ Johan
|
