Win 7 Reference Deployment fails because of missing Sysprep
Hi, I have successfully inistalled ConfigMgr R2 a few weeks ago, but my first Operating System Deployment just won't work. It boots, installs windows etc. but fails during sysprep at the end. SMSTS.log on the client shows he same output as is described here: http://cid-37e6ca43f5d0737a.spaces.live.com/blog/cns!37E6CA43F5D0737A!180.entry . Unfortunately the advice given on this blog won't seem to help, I already re-created the Client package, redistributed it and re-created the install media, same error. The mentioned blog post was the only helpful info I found about this problem so I am getting kinda frustrated. With regards, Pharao2k
October 20th, 2010 2:22pm

Here is a small part of the smsts.log: http://img146.imageshack.us/img146/9563/smstslog.png
Free Windows Admin Tool Kit Click here and download it now
October 20th, 2010 2:40pm

The task sequence contains the following elements (no screenshot since it would be german, which is also the reason why the translation may not be 100% correct) -> Restart in Windows PE -> Partition Disk 0 -> Apply Operating System -> Apply Windows Settings -> Apply Network Settings -> Setup Windows and ConfigMgr -> Install "Adobe Reader 9.3" (just for testing purposes) -> Prepare ConfigMgr-Client -> Prepare OS -> Capture the Reference Machine I followed the Book "System Center Configuration Manager 2007 Unleashed" when I created that task sequence, but I left most options as default to reduce possibility of problems.
October 20th, 2010 3:13pm

Okay, the reference machine task sequence worked now, thanks to Niall. I just assumed ConfigMgr 2007 R2 included the Service Pack 2, after I installed it the tip from the link of the beforementioned blog post worked and the task sequence could find sysprep. But now I've got another problem ;) After the .wim image was created, I built another task sequence for deployment, created a collection with both Unknown Computer Objects in it (Unknown Computer support is activated) and created an advertisement. But now, when I boot up via PXE, WinPE starts, initializes its network config etc., but right before it should start the task sequence and deploy windows, it just reboots. It sounds to me that it doesn't know what to do and since there is nothing to do it exits, but as far as I know the advertisement should suffice. The advertisement collection contains the 2 "virtual" Unknown Computer (x86+x64) objects and an imported computer association with the mac address and guid of the targeted client.
Free Windows Admin Tool Kit Click here and download it now
October 22nd, 2010 3:12pm

unknown computer support is enabled on the pxe service point. I created a new collection for Reimaging purposes because I want the option to reimage known computers, too, which I guess I shouldn't add to the unknown computer collection. Like I said, WinPE starts, shows the ConfigMgr background image, displays that it starts itself and initializes network connections, but it reboots before something task sequence-related is started. Since WinPE is only open for ~10-12 seconds I cannot look in the client-side logs, and the server-side don't seem very helpful.
October 22nd, 2010 4:24pm

command line support is already enabled, but unfortunately the ~10 seconds are by far not enough to access and read through the logs. Besides, I think the necessary log part would be at the one right before the reboot.
Free Windows Admin Tool Kit Click here and download it now
October 22nd, 2010 4:42pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics