Configuring default settings for Windows image deployment - Update for Windows XP SP3
In my previous post on this topic, I mentioned that Windows XP Service Pack 2 will copy the Administrators settings to Default User (see sections B & C). The new profile copy is the default behavior in SP2 with no built-in way to disable it. To disable it you had to request the hotfix from KB887816 from Microsoft Customer Support.
This has changed with Windows XP Service Pack 3. The fix from KB887816 is included in SP3. (See KB946480 for a list of fixes included in SP3.) Therefore, the behavior for SP3 is no profile copy by default. To enable the profile copy, you now have to add UpdateServerProfileDirectory=1 to the [Unattended] section of Sysprep.inf before running Sysprep. Unfortunately, due to an oversight you will not find this documented in the Microsoft Windows Preinstallation Reference (ref.chm) included with the SP3 Deployment Tools. KB887816 is currently one of the only references for this setting, as far as I know. (KB908784 also references this setting with respect to a problem that the profile copy can cause on Windows Server 2003)
8/3/2008 Update
In this post I orginally provided some instrutions about slipstreaming SP 3 into an installation source with the Tablet PC Edition CMPNENTS folder in it. Well it turns out that slipstreaming SP3 into the CMPNENTS will not be supported. See my August 3rd post for details.
Disclaimer: The information on this site is provided "AS IS" with no warranties, confers no rights, and is not supported by the authors or Microsoft Corporation. Use of included script samples are subject to the terms specified in the Terms of Use .
This post was contributed by Michael Murgolo, a Senior Consultant with Microsoft Services - U.S. East Region.
Comments
Anonymous
January 01, 2003
PingBack from http://blogs.technet.com/deploymentguys/archive/2008/02/18/configuring-default-user-and-computer-settings-for-windows-image-deployment.aspxAnonymous
January 01, 2003
http://blogs.technet.com/deploymentguys/archive/2008/05/22/configuring-default-settings-for-windows-imageAnonymous
January 01, 2003
The comment has been removedAnonymous
January 01, 2003
Hi Andrea, There is a seperate CS.ini and bootstrap.ini file for each deployment point. You will find a sub-folder for each deployment under the control folder of the lab deployment point. I would suggest that you only edit these files through the deployment workbench. Thanks, BenAnonymous
January 01, 2003
Peter, I have not see any such issues with SP3. Perhaps a comparison of the setup logs (setup*.log in the Windows folder) from an SP2 and an SP3 image deployed onto the same hardware might reveal some differences. Michael MurgoloAnonymous
January 01, 2003
kjetilbs, I have not had to make any changes to the MDT LTI deployment scripts to an XP SP3 image successfully. What is the stop error code at the blue screen? Michael MurgoloAnonymous
January 01, 2003
The comment has been removedAnonymous
January 01, 2003
Hi Andrea, We would need to see the relevant lines from the BDD.log file before we can help you. Can you post these? Thanks, BenAnonymous
January 01, 2003
Hi Andrea, Check your deployment task sequence and see if you have the Mass Storage driver injection task enabled. You need to disable it when deploying a custom XP/2003 WIM. Thanks, BenAnonymous
May 22, 2008
Excellent explanation. Question was also posted on http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=3238294&SiteID=17 Regards, Arian van der PijlAnonymous
June 04, 2008
Ben, I captured a wim using the MDT 2008, XP sp3. I've created a task sequence to deploy the wim, but the task sequence returns an error (yellow warning screen) that it couldn't copy the source files from the minint folder to the windows folders? How do I stop that task? The folder is already there since it was created in the original task sequence. Thanks AndreaAnonymous
June 05, 2008
The comment has been removedAnonymous
June 10, 2008
Thanks Ben. Another question. I created a network deployment point in addition to the lab deploymetn point. After I updated the deployment points adn tested I saw that a folder was created on the lab point that held a cs ini and bootsrtap.ini file. It looked like when i ran a task sequence for the new network deployment point is was using the cs ini from the folder that was created, and not from the deployment control folder, is that right??? Am I missing something, again? ;)Anonymous
June 16, 2008
Ben, Thaks. I know that and it seemed that wehen I updated the cs ini for the network deployement point it used the one from the strange folder it created. i had hid some wizard pages adn added the join domain and stuff in thenetwork deployment cs ins, but when I ran the deployment (after updating) the customizations weren't being used. ??? AndreaAnonymous
June 16, 2008
Hi Ben, I'm trying to deploy,make some changes adn recapture my Xp image,whether I disable or enable the inject mass storage drivers I still get a deployment failure on the ztistoragegroup drivers. Is there something else I need to do to re-capture an image? Do i have to rebuild it from scratch?Anonymous
June 16, 2008
Thanks for the quick reply. Guess what I'm doing right now- rebuild/capture. ;) AndreaAnonymous
July 02, 2008
The comment has been removedAnonymous
July 30, 2008
Hello, i recently changed the base installation of our images from Windows XP with integrated SP2 to Windows XP with integrated SP3 and changed the sysprep files to the SP3 files, too. Everything works fine and in the same way as in the SP2 image, but the duration of the minisetup process, especially the hardware detection, takes much longer on on our target pcs and laptops with the same hardware, drivers and configuration. I already have posted this in the TechNet-Forum, but no-one seems to have the same issue... Regards PeterAnonymous
July 31, 2008
The comment has been removed