How to create a custom default user profile for a Windows Vista or newer OS when using ConfigMgr 2007 OSD

How to create a custom default user profile for a Windows Vista or newer OS when using ConfigMgr 2007 OSD

  • Comments 1
  • Likes

GrayAndYellowGearsWhen building a Windows Vista or newer reference image (Windows 7, Windows Server 2008, Windows Server 2008 R2), to create a custom Default User profile based on modifications done on the local Administrator profile normally the CopyProfile option is used in an Unattend.xml file. However, since System Center Configuration Manager 2007 creates its own Unattend.xml file the CopyProfile option cannot be specified.

Resolution

After making the required changes and customizations to the local Administrator profile, capture the Windows reference image using the normal methods (i.e., ConfigMgr 2007 Capture Media). The custom Default User profile does not have to be created at Sysprep/Capture time. It can be created at deployment time.

The CopyProfile option can be specified in a custom Unattend.xml file that is then injected and merged with the Unattend.xml file generated by the ConfigMgr 2007 OSD Task Sequence when the Windows OS is deployed.

To create the custom Default User profile during the ConfigMgr OSD Task Sequence that deploys the Windows OS:

1. Open Notepad.

2. Choose the appropriate architecture below of the Windows OS being deployed, copy the lines below the architecture, and paste them into the Notepad. When pasting in Notepad, make sure that the Word Wrap option is turned off so that the below lines paste properly:

x86

<?xml version="1.0" encoding="utf-8"?>
<unattend xmlns="urn:schemas-microsoft-com:unattend">
    <settings pass="specialize">
        <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
            <CopyProfile>true</CopyProfile>
        </component>
    </settings>
</unattend>

x64
<?xml version="1.0" encoding="utf-8"?>
<unattend xmlns="urn:schemas-microsoft-com:unattend">
    <settings pass="specialize">
        <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
            <CopyProfile>true</CopyProfile>
        </component>
    </settings>
</unattend>

Note: In both examples above, the "component name" line (everything between the "settings pass" and "CopyProfile" lines) should all be on one line. Make sure that the line does not wrap when pasting in Notepad.

3. Save the Notepad file with the name copyprofile.xml.  When saving the file, make sure that "All Files (*.*)" is selected next to "Save as type:" so that it does not append the .txt extension to the file.

4. In the ConfigMgr 2007 Admin console, under the "Computer Management" --> "Software Distribution" --> "Packages" node, create a new package that contains the copyprofile.xml file created in Steps 2 & 3. A Program does not need to be created for the Package. After creating the Package, make sure to copy the Package to the Distribution Points.

5. In the Configuration Manager 2007 Admin Console, under the "Computer Management" --> "Operating System Deployment" --> "Task Sequences" node, right click on the Task Sequence that deploys the OS and choose "Properties".

6. In the "Apply Operating System" task:

    • Check the option "Use an unattended or sysprep answer file for a custom installation
    • Next to the "Package:" field, click on the "Browse..." button and select the package created in Step 4
    • Next to the field "Filename:", enter:  copyprofile.xml

7. Click on the "Apply" button to save the Task Sequence.

Notes:

1. If an existing custom XML file is already being used in the "Apply Operating System" task, then the appropriate lines from Step 2 should be added to the appropriate sections in the existing XML file. When doing so, make sure not to duplicate any lines. When finished modifying the existing custom XML file, make sure to update the DPs for the package that the XML file is contained in.

2. As an alternative, Steps #1-3 above can be replaced by using Windows System Image Manager (WSIM) instead. WSIM, which is part of the Windows Automated Installation Kit (WAIK), can be used to create the appropriate XML file with the CopyProfile section in it. If an existing custom XML file is already being specified as noted in Note #1 above, WSIM can also be used modify the existing custom XML file by adding the CopyProfile section to the existing XML file.

Frank Rojas | System Center Support Escalation Engineer

The App-V Team blog: http://blogs.technet.com/appv/
The WSUS Support Team blog: http://blogs.technet.com/sus/
The SCMDM Support Team blog: http://blogs.technet.com/mdm/
The ConfigMgr Support Team blog: http://blogs.technet.com/configurationmgr/
The OpsMgr Support Team blog: http://blogs.technet.com/operationsmgr/
The SCVMM Team blog: http://blogs.technet.com/scvmm/
The MED-V Team blog: http://blogs.technet.com/medv/
The DPM Team blog: http://blogs.technet.com/dpm/
The OOB Support Team blog: http://blogs.technet.com/oob/
The Opalis Team blog: http://blogs.technet.com/opalis

clip_image001 clip_image002

Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment
  • This is ridiculous, SCCM deployment is even more of a mess and even more convoluted than doing a manual sysprep and imaging process. I thought SCCM was meant to make everything easier. SCCM os deployment is disgustingly designed.