Sign in
 
HomeLibraryWikiLearnGalleryDownloadsSupportForumsBlogs
Resources for IT Professionals >
> 
> 
> 
Sysprep XP SP3

Answered Sysprep XP SP3

  • Saturday, February 09, 2013 12:46 AM
     
     
    Sign In to Vote
    0
    Can anyone confirm the procedure for copying the Administrator profile to Default User when capturing an XP SP3 image?  Does the line in the sysprep file updateserverprofiledirectory=1 go under the sysprep and capture task sequence or the deployment task sequence.  I'm having trouble.
     

All Replies

  • Saturday, February 09, 2013 6:26 AM
     
     
    Sign In to Vote
    1
    UpdateServerProfileDirectory, like CopyProfile in later versions of Windows, tells Sysprep to copy the admin profile to the default user profile and is specifically for use when capturing an image.  When then using the captured image in a deployment task sequence, the changes you made are already part of the default user profile and no additional step is required (unless you do further customization during deployment that needs to be part of the default user profile, but that should be handled differently, if possible).

    David Coulter | http://DCtheGeek.blogspot.com | @DCtheGeek

     
  • Saturday, February 09, 2013 3:25 PM
     
     
    Sign In to Vote
    0

    Thanks for your help!  

    It's confusing because each (XP) task sequence you create has it's own sysprep.if file.  Even if you import a .wim file captured form MDT and select the option setup and sysprep files are not needed the sysprep.inf button appears in the OS tab of the task sequence properties.  I use 3 task sequences in my environment to build our images.  1. Creates base windows installs from source files in a VM.  2. Sysprep and Capture Task created by MDT. 3. Tasks to deploy the WIM's captured by MDT.  Through reading forums and so on it appears to me, and this appears to be what you are saying... The syprep.inf that needs to be edited to include UpdateServerProfileDirectory=1 is the one that is used to sysprep the computer... makes sense!  I have placed this line in the sysprep.inf of my sysprep & capture task sequence to no avail.  It's killing me.... It seems it should be just that easy!  Am I just missing something?

    As a side note - correct me if I'm wrong, but it appears that you only change the CopyProfile to true in the unattended.xml of Windows 7 task sequences in the one used for deploying, not building or capturing...?

     
  • Saturday, February 09, 2013 10:00 PM
     
     
    Sign In to Vote
    1

    This is what happens when you post late at night, your mind isn't always clear. : )

    Yes, you are correct, you use it during the deploy, not for capture.  Johan has a good article about it (and why the WAIK doco was wrong):
    http://www.deploymentresearch.com/Blog/tabid/62/EntryId/43/How-CopyProfile-really-works-in-Windows-7-Deployments.aspx

    David Coulter | http://DCtheGeek.blogspot.com | @DCtheGeek

     
  • Sunday, February 10, 2013 6:46 AM
     
     Answered
    Sign In to Vote
    0
    Well, after some more testing... the answer has appeared.  It's funny how things can be right in front of your face, but you still miss it.  In my initial task, the one that I use to build my reference image, the sysprep.ini file from that task sequence is copied to the folder C:\Sysprep.  I've been trying to add  UpdateServerProfileDirectory=1 to the sysprep.ini in the task sequence that I use to capture the image with.  Apparently, you can customize this all you want, but it will never be used as long as the original sysprep.ini file that was dropped in the c:\Sysprep folder by my initial build task sequence still exists.  So, in my case, the answer is: If you plan on copying the admin profile to the default user profile in Windows XP SP3, using MDT, the sysprep.ini file that you want to add the line UpdateServerProfileDirectory=1 is in the initial task sequence used in building the reference image.  I haven't tried deleting the file from the folder and seeing if it is replaced by the Sysprep & Capture task sequence sysprep.ini, but that will have to come later.  Thanks for your help
    • Marked As Answer by joe8878 Sunday, February 10, 2013 6:47 AM
    •