Jump to content
DeployCentral

Default Local Profile Windows 10


ditasn2000

Recommended Posts

Is there a recommended or suggested method of customizing the default local user profile for Windows 10 with the current version of SmartDeploy?

I tried creating a new profile, customizing the profile, renaming the profile, using the registry to load ntuser.dat etc., but not all settings are carried over when a new user profile is created.

Any help will be appreciated.

Link to comment
Share on other sites

Hello,


Here are the steps to copy the default profile with SmartDeploy:


Enter audit mode: You can either start from a fresh Windows 7 install and at the screen where it asks for user information (the OOBE Windows Welcome screen) press Shift + CTRL + F3, alternately if you already have the OS installed run “sysprep /audit /reboot” to enter audit mode.

Once the machine reboots you should be auto logged into the Administrator account. Make any changes that you would like to become part of the default user profile.

Once you have completed your changes run the “sysprep /generalize /OOBE /reboot /unattend:[path to the unattend file]” the machine will reboot and you can now create new profiles that will use the same settings you edited while in audit mode.

To test, it may be a good idea to login to the VM and create a new user profile. Login to the new profile and make sure all settings are as copied as desired.

The next step would be to capture an image from your VHD. To do this run through the normal steps using Capture Wizard.

Once you have captured your image create your deployment media using Media Wizard as normal and boot your target machine to the SmartPE environment.

Deploy Your image as normal. On boot all of your settings should be maintained when creating new users.


Below are examples of answer files with copy profile setting. One is for Windows x86 and the second for Windows x64.


x86


<?xml version="1.0" encoding="utf-8"?>

<unattend xmlns="urn:schemas-microsoft-com:unattend">

<settings pass="generalize">

<component name="Microsoft-Windows-Security-SPP" 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">

<SkipRearm>1</SkipRearm>

</component>

</settings>

<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>

<cpi:offlineImage cpi:source="catalog:d:/os media/en_windows_7_enterprise_with_sp1_x86_dvd_620186/sources/install_windows 7 enterprise.clg" xmlns:cpi="urn:schemas-microsoft-com:cpi" />

</unattend>


x64

<?xml version="1.0" encoding="utf-8"?>

<unattend xmlns="urn:schemas-microsoft-com:unattend">

<settings pass="generalize">

<component name="Microsoft-Windows-Security-SPP" 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">

<SkipRearm>1</SkipRearm>

</component>

</settings>

<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>

<cpi:offlineImage cpi:source="catalog:d:/smartdeploy/tools/install_windows 7 ultimate.clg" xmlns:cpi="urn:schemas-microsoft-com:cpi" />

</unattend>
Link to comment
Share on other sites

  • 2 weeks later...

Can the above steps be re-run until the default profile is tweaked to my liking or do I have to get it right the first time? Meaning... if I run sysprep then realize there's a couple of settings that need to be changed, can I go back into audit mode, make the additional changes, then run sysprep again to capture the updated default profile?

Link to comment
Share on other sites

Can the above steps be re-run until the default profile is tweaked to my liking or do I have to get it right the first time? Meaning... if I run sysprep then realize there's a couple of settings that need to be changed, can I go back into audit mode, make the additional changes, then run sysprep again to capture the updated default profile?

I was able to do this multiple times before finally capturing the completed image. It works great on Win7. I basically just copied the x64 portion from above and pasted it into a notepad and saved as unattend.xml in the c:\windows\system32\sysprep directory of the machine that you are working on. I was unable to run the command “sysprep /generalize /OOBE /reboot /unattend:[path to the unattend file]” due to sysprep currently running already. In the sysprep box that is on the screen, make sure you check the generalize box. The dropdowns should be set as "enter system out of box experience" and "Reboot". Press OK and the system will begin to sysprep the machine.

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...