OSD WIN 7  Sysprep Question
Hello all, We are beginning our migration from WinXP to WIN7 and I am learning about the differences in OSD deployment. I use Capture Media to capture my reference computers (I know this is not the best way but it is what I am familiar with) I am seeing there are differences in the way Sysprep works when capturing WIn7 as opposed to XP. I am trying to configure an unattend.xml with WSIM mostly to get the default profile copy so all my settings are captured in the .wim file, apply our WIN7 Enterprise MAK license key, and I would also like to have the setup ask me for a computername after the OS image is deployed. I am not sure I really need much else since we will do any other customizing after the image is installed. But I am open to suggestions since I am new to WSIM. My second question is where do I put the unattend.xml file for the CopyProfile=true command to work? Do i just put it in the Sysprep folder of the reference machine and it will handle it from there? As always thanks for the great advice in these forums. Steve
September 15th, 2012 6:43pm

have a look at this post Step by Step ConfigMgr 2007 Guides | Step by Step ConfigMgr 2012 Guides | I'm on Twitter > ncbrady
Free Windows Admin Tool Kit Click here and download it now
September 17th, 2012 10:15am

Thanks Niall, But I am still confused after reading the posts. I understand that I have to create the unattend.xml with WSIM. I am still not clear where to put this file when I am capturing the reference machine with SCCM. Does it go in the Sysprep folder on the reference machine? Or does it go somewhere else to be run after the image is deployed to a new machine?
September 17th, 2012 2:22pm

SCCM/ConfigMgr will create an unattend.xml file for you. It is however possible to create one yourself and use it in the task sequence. That way both files will be merged, and your specific settings will be used during OS deployment. So, Just create a unattend.xml file and create a software package of it. A program is not needed. Then use that package during the Apply OS Image step, and fill in the name there. Then the OS image can be used in different task sequences and/or answer files with different settings. You can also have a look here: http://scug.be/sccm/2010/02/02/sccm-windows-7-deployments-amp-unattended-xml/My blogs: Henk's blog and Virtuall | Follow Me on: Twitter | View My Profile on: LinkedIn
Free Windows Admin Tool Kit Click here and download it now
September 17th, 2012 3:20pm

Thank you Henk, So how does SCCM create an unattend.xml file? Is it done during the capture or is this something I can do as a step in the task sequence? I have created one with Windows System Image manager and that is the one that can be added to the Apply OS Image step if I understand you coreectly. I am interested to understand what you mean by SCCM will create one for me. Can you clarify that part a bit more? Thanks for your help.
September 17th, 2012 8:34pm

if you don't specify an unattend.xml file Configuration Manager will create one after the Apply Operating System image step, in the steps leading up to Setup windows and configmgr, you can pause the task sequence before apply windows settings and apply network settings to see the file being created and used, the following parts (1,4 and 6) may be of use to you as they directly talk about the unattend.xml file... Customising Windows 7 deployments - part 1. Changing the keyboard layout using unattend.xml Customising Windows 7 deployments - part 2. Specifying an Organisational Unit (OU) using the MachineObjectOU variable Customising Windows 7 deployments - part 3. Customising and changing power management using PowerCfg Customising Windows 7 deployments - part 4. Deploying Language Packs Offline using MDT 2010 Update 1 Customising Windows 7 deployments - part 5. Enabling Bitlocker in WinPE on Dell computers [Jul 2011] Customising Windows 7 deployments - part 6. Adding multiple keyboard layouts and multiple languages [Mar 2012] cheers niall Step by Step ConfigMgr 2007 Guides | Step by Step ConfigMgr 2012 Guides | I'm on Twitter > ncbrady
Free Windows Admin Tool Kit Click here and download it now
September 18th, 2012 4:34am

if you don't specify an unattend.xml file Configuration Manager will create one after the Apply Operating System image step, in the steps leading up to Setup windows and configmgr, you can pause the task sequence before apply windows settings and apply network settings to see the file being created and used, the following parts (1,4 and 6) may be of use to you as they directly talk about the unattend.xml file... Customising Windows 7 deployments - part 1. Changing the keyboard layout using unattend.xml Customising Windows 7 deployments - part 2. Specifying an Organisational Unit (OU) using the MachineObjectOU variable Customising Windows 7 deployments - part 3. Customising and changing power management using PowerCfg Customising Windows 7 deployments - part 4. Deploying Language Packs Offline using MDT 2010 Update 1 Customising Windows 7 deployments - part 5. Enabling Bitlocker in WinPE on Dell computers [Jul 2011] Customising Windows 7 deployments - part 6. Adding multiple keyboard layouts and multiple languages [Mar 2012] cheers niall Step by Step ConfigMgr 2007 Guides | Step by Step ConfigMgr 2012 Guides | I'm on Twitter > ncbrady
September 18th, 2012 4:34am

You can start a command prompt with F8 during OS deployment (enabled in boot image). During "Apply Windows Settings" and "Apply Network Settings" the unattend.xml file will be generated. During "Setup windows and ConfigMgr" the file is used for having a unattend installation. The unattend.xml will be created/placed in the "C:\Windows\Panther\Unattend" folder.My blogs: Henk's blog and Virtuall | Follow Me on: Twitter | View My Profile on: LinkedIn
Free Windows Admin Tool Kit Click here and download it now
September 18th, 2012 10:43am

You can start a command prompt with F8 during OS deployment (enabled in boot image). During "Apply Windows Settings" and "Apply Network Settings" the unattend.xml file will be generated. During "Setup windows and ConfigMgr" the file is used for having a unattend installation. The unattend.xml will be created/placed in the "C:\Windows\Panther\Unattend" folder.My blogs: Henk's blog and Virtuall | Follow Me on: Twitter | View My Profile on: LinkedIn
September 18th, 2012 10:43am

That makes sense. Thank you for taking the time to explain this. Just so I am sure I am following you.. I can create my unattend.xml with WSIM which will include whatever settings I need like the the CopyProfile=True statement to get my default settings to all users thaat login to the machine. I create a package and add it to the Apply Operating System Image step in my task sequence and I should be good to go from there.
Free Windows Admin Tool Kit Click here and download it now
September 18th, 2012 8:22pm

Thank Henk.
September 18th, 2012 8:23pm

Ok, so I have read all the posts I can find including the good advice here. I guess this has been just enough to confuse me because I have not been able to get a working image for Windows 7 using SYSPREP and it is getting to be crunch time for deployment. I have created an Unattend.xml with WSIM. I have setup a reference machine with the sttings the way I want it (mostly). for testing I run sysprep.exe from an elevated command prompt that calls my unattend.xml. Sysprep runs fr awhile then I get a message that it could not parse the unattend.xml file in the specialize pass and then it bricks the machine. I basically have to completely reinstall windows 7 to make another test and I get the same results. I have read so much about what needs to go where in the unattend.xml that I am just thoroughly confused now. I am sure I am doing something or multiple things incorrectly but at this point I have no idea where to start looking to find out how to get this corrected. Any suggestions?
Free Windows Admin Tool Kit Click here and download it now
September 26th, 2012 2:59pm

i'd recommend you use virtual hardware to do all your testing here, that way you can snapshot before the event to figure out whats going on and save time troubleshooting the issue if windows pops up an error about not being able to parse the unattend.xml file then the error will be logged in your smsts.log file, so what does it say there, also look at the setupact.log file if the previous one doesn't help, this post should also give you some clues. Step by Step ConfigMgr 2007 Guides | Step by Step ConfigMgr 2012 Guides | I'm on Twitter > ncbrady
September 29th, 2012 3:52pm

I have already built another machine to test with. So if it happens again I will attempt to get to those logs but the computer seems to go into an endless loop and I was not able to do anything with it to view any logs. I am going to try with a more basic unattend.xml to see if I can get it to work at all. Another question, so from my reading, no settings will pass to all users without running sysprep and using an unattend.xml it seems. What are the options if I have deployed machines already and I need to make a settings change for all users on the machine? Do I still have to run sysprep and use an updated unattend file? This seems like a very bad way of having to make a simple change to an existing users Windows 7 install since it appears you have to run sysprep with the generalize command. Am I misunderstanding what I am reading about this?
Free Windows Admin Tool Kit Click here and download it now
October 1st, 2012 10:26am

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

Other recent topics Other recent topics