Local accounts and custom profile

[balubeto]

Local accounts and custom profile [New]

Hi

I have Windows 7 SP1 and I want to create a custom default profile so that, when I will have to create the local accounts, they already will have the custom profile.

Thanks

Bye

 

[gregrocker]

Use backup imaging: Backup Complete Computer - Create an Image Backup

If Win7 becomes irreparable you can boot the DVD or Repair CD to do an easy System Image Recovery.

You can also SysPrep the installation before imaging so that it will start up on any hardware: SysPrep to move HD to another computer

 

[balubeto]

Use backup imaging: Backup Complete Computer - Create an Image Backup

If Win7 becomes irreparable you can boot the DVD or Repair CD to do an easy System Image Recovery.

You can also SysPrep the installation before imaging so that it will start up on any hardware: SysPrep to move HD to another computer

Apparently, this solution is not mine.

Thanks

Bye

 

[balubeto]

After reading the Customize the default local user profile when preparing an image of Windows article, I have some questions:

1) Where can I find Unattend.xml files already made ​​valid for each version and edition of Windows 7 SP1 to change the default profile using parameter CopyProfile?

2) I am obliged to enable the Administrator account and configure it or I could use my administrator account, already configured, to run the Sysprep utility?

Thanks

Bye

 

[balubeto]

These two xml files should be fine:

For Windows 7 SP1 32-bit:

<?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="[URL="http://schemas.microsoft.com/WMIConfig/2002/State"][U][COLOR=#0000aa]http://schemas.microsoft.com/WMIConfig/2002/State[/COLOR][/U][/URL]" xmlns:xsi="[URL="http://www.w3.org/2001/XMLSchema-instance"][U][COLOR=#0000aa]http://www.w3.org/2001/XMLSchema-instance[/COLOR][/U][/URL]">
<CopyProfile>true</CopyProfile>
</component>
</settings> <cpi:offlineImage cpi:source="wim://<computerName>/<Source_dir>/install.wim#Windows 7 <Edition>" xmlns:cpi="urn:schemas-microsoft-com:cpi" />
</unattend>

For Windows 7 SP1 64-bit:

<?xml version="1.0" encoding="utf-8"?>
<unattend xmlns="urn:schemas-microsoft-com:unattend">
<settings pass="specialize">
<component name="Microsoft-Windows-Shell-Setup" processorArchitecture="x64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS"
xmlns:wcm="[URL="http://schemas.microsoft.com/WMIConfig/2002/State"][U][COLOR=#0000aa]http://schemas.microsoft.com/WMIConfig/2002/State[/COLOR][/U][/URL]" xmlns:xsi="[URL="http://www.w3.org/2001/XMLSchema-instance"][U][COLOR=#0000aa]http://www.w3.org/2001/XMLSchema-instance[/COLOR][/U][/URL]">
<CopyProfile>true</CopyProfile>
</component>
</settings> <cpi:offlineImage cpi:source="wim://<computerName>/<Source_dir>/install.wim#Windows 7 <Edition>" xmlns:cpi="urn:schemas-microsoft-com:cpi" />
</unattend>

It is possible to merge the two xml files or not?

It is possible to create an xml file also valid for any edition?

In an installation of Windows 7 SP1, there is the install.wim or I must always specify its source path?

Thanks

Bye

 

[balubeto]

I created the CopyProfile.xml file:

<?xml version="1.0" encoding="utf-8"?>
<unattend xmlns="urn:schemas-microsoft-com:unattend">
<settings pass="generalize">
<component name="Microsoft-Windows-Security-Licensing-SLC" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="[URL="[URL]http://schemas.microsoft.com/WMIConfig/2002/State"][COLOR=#0000aa]http://schemas.microsoft.com/WMIConfig/2002/State[/COLOR][/URL[/URL]]" xmlns:xsi="[URL="[URL]http://www.w3.org/2001/XMLSchema-instance"][COLOR=#0000aa]http://www.w3.org/2001/XMLSchema-instance[/COLOR][/URL[/URL]]">
<SkipRearm>1</SkipRearm>
</component>
</settings>
<settings pass="specialize">
<component name="Microsoft-Windows-Shell-Setup" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="[URL="[URL]http://schemas.microsoft.com/WMIConfig/2002/State"][COLOR=#0000aa]http://schemas.microsoft.com/WMIConfig/2002/State[/COLOR][/URL[/URL]]" xmlns:xsi="[URL="[URL]http://www.w3.org/2001/XMLSchema-instance"][COLOR=#0000aa]http://www.w3.org/2001/XMLSchema-instance[/COLOR][/URL[/URL]]">
<CopyProfile>true</CopyProfile>
</component>
</settings>
<cpi:offlineImage cpi:source="wim://<computerName>/<Source_dir>/install.wim#Windows 7 <Edition>" xmlns:cpi="urn:schemas-microsoft-com:cpi" />
</unattend>

and I put it in an USB stick.
So, I planned to install Windows 7 normally, install the additional drivers, update Windows, go to audit mode with the c:\windows\system32\sysprep\sysprep.exe /audit command, delete the account created during installation, customize the Administrator account. Finally, I run the c:\windows\system32\sysprep\sysprep.exe /oobe /reboot /generalize /unattend:<USB stick unit>:\CopyProfile.xml command to go into OOBE mode. Right? Is there a better way to do this?

Thanks

Bye

 

[WinOutreach2]

The easiest method to enter the Administrator account to customize it in order to customize the default profile is to use Audit Mode. When you have installed Windows and have been presented with mini-setup, which is where you are asked for the username, computer name, etc… press Ctrl+Shift+F3 and you will find yourself logged into the system without being asked any further questions, you will be logged in as Administrator, and will remain so until you run Sysprep, where you can supply your answer file and customize the default profile.

The above linked unattend.xml files should work fine, however you may also want to consider installing the Windows Automated Installation Kit (WAIK) which includes a variety of deployment tools from Microsoft including the Windows System Image Manager (WSIM) which automates creating answer files if you are considering making additional changes to your answer files. It also includes ImageX, the free imaging utility provided by Microsoft. There are instructions on how to perform a basic deployment using WAIK available in the TechNet article: Step-by-Step: Basic Windows Deployment for IT Professionals.

Lastly, and perhaps just a minor tip, remember that the default user profile image is not a part of the default user profile. To customize this image, you will need to replace user.bmp in C:\ProgramData\Microsoft\User Account Pictures\ which is 128x128 pixels. It’s a small thing, but it can end up being the only thing holding you back from a really professional looking default profile.

 

[WinOutreach2]

Finally, I run the c:\windows\system32\sysprep\sysprep.exe /oobe /reboot /generalize /unattend:<USB stick unit>:\CopyProfile.xml command to go into OOBE mode. Right? Is there a better way to do this?

I would recommend copying the answer file to the C:\ local drive, just in case your system somehow shuffles drive letters upon reboot and the Sysprep file becomes inaccessible.

 

[balubeto]

So, my CopyProfile.xml file and my procedure is wrong?

Thanks

Bye

 

[F5ing]

Apparently you've gotten some good advice there. Maybe the following can help you as well:

http://www.sevenforums.com/tutorial...w-create-general-system-image-audit-mode.html

 

[balubeto]

Apparently you've gotten some good advice there. Maybe the following can help you as well:

http://www.sevenforums.com/tutorial...w-create-general-system-image-audit-mode.html

The generalize option of Sysprep does not remove the additional drivers installed in Audit mode. Right?

Is true that some drivers have difficulty to be installed and to work in Audit mode?

If I wanted download and install all updates of Windows 7 from Windows Update in Audit mode, when I should run its activation?

Thanks

Bye

 

[Kari]

Apparently you've gotten some good advice there. Maybe the following can help you as well:

http://www.sevenforums.com/tutorial...w-create-general-system-image-audit-mode.html

The generalize option of Sysprep does not remove the additional drivers installed in Audit mode. Right?

WRONG! The generalize option removes all hardware drivers replacing them with general hardware independent windows drivers!

Is true that some drivers have difficulty to be installed and to work in Audit mode?

No.

If I wanted download and install all updates of Windows 7 from Windows Update in Audit mode, when I should run its activation?

Audit Mode is to customize your Windows installation for further deployment. Activation should be done first after finalizing the setup, after first OOBE boot. Never when in Audit Mode.

Kari

 

[balubeto]

Apparently you've gotten some good advice there. Maybe the following can help you as well:

http://www.sevenforums.com/tutorial...w-create-general-system-image-audit-mode.html

The generalize option of Sysprep does not remove the additional drivers installed in Audit mode. Right?

WRONG! The generalize option removes all hardware drivers replacing them with general hardware independent windows drivers!

So, how do I remove the Administrator account, all system-specific information, any system restore points and the event logs and reset the SIDs without using the generalize option?

Thanks

Bye

 

[WinOutreach2]

You can use the same Answer File which specifies to copy the default profile from administrator to specify to keep all device drivers intact through the generalize command, but you will have to generalize the machine in order to run OOBE which is required to use the unattend file and to remove the system from Audit Mode. Details on the PersistAllDevices setting can be found under the Sysprep Process section of the TechNet article How Sysprep Works under the header Persisting Plug and Play Device Drivers During Generalize.

In response to your question regarding your procedure, it is definitely correct; you have a good handle on things. Just beware that the answer file can be called during the setup procedure of Windows once the environment boots after Sysprep has been run. As such, if your USB stick is removed, your image may fail. The easiest way to avoid this is to place the Sysprep file in the image itself, on the C: drive, so that it is copied to each system as part of the image and is always accessible.

 

[balubeto]

So, if I change my CopyProfile.xml file in:

<?xml version="1.0" encoding="utf-8"?>
<unattend xmlns="urn:schemas-microsoft-com:unattend">
    <settings pass="generalize">
        <component name="Microsoft-Windows-Security-Licensing-SLC" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="[URL="http://schemas.microsoft.com/WMIConfig/2002/State"]Error[/URL]" xmlns:xsi="[URL]http://www.w3.org/2001/XMLSchema-instance[/URL]">
            <SkipRearm>1</SkipRearm>
        </component>
       <component name="Microsoft-Windows-PnpSysprep" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS">
          <PersistAllDeviceInstalls>true</PersistAllDeviceInstalls>
       </component>
    </settings>
    <settings pass="specialize">
        <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="[URL="http://schemas.microsoft.com/WMIConfig/2002/State"]Error[/URL]" xmlns:xsi="[URL]http://www.w3.org/2001/XMLSchema-instance[/URL]">
            <CopyProfile>true</CopyProfile>
        </component>
    </settings>
    <cpi:offlineImage cpi:source="" xmlns:cpi="urn:schemas-microsoft-com:cpi" />
</Unattend>

the c:\windows\system32\sysprep\sysprep.exe /oobe /reboot /generalize /unattend:c:\CopyProfile.xml command, run in Audit mode, not remove the additional drivers installed in OOBE and Audit mode. True?

Thanks

Bye

 

[WinOutreach2]

Running Sysprep with those settings in the answer file will cause the Administrator profile which had been configured in Audit Mode to be copied to the default profile and all drivers to be preserved. The environment will boot to the Out of Box Experience (OOBE) or Windows Welcome where you will be prompted for computer name, user name, etc.

Bear in mind your linked answer file is for a 32 bit environment. It also will not reset the activation information as specified with SkipRearm.

 

[balubeto]

Running Sysprep with those settings in the answer file will cause the Administrator profile which had been configured in Audit Mode to be copied to the default profile and all drivers to be preserved. The environment will boot to the Out of Box Experience (OOBE) or Windows Welcome where you will be prompted for computer name, user name, etc.

Bear in mind your linked answer file is for a 32 bit environment. It also will not reset the activation information as specified with SkipRearm.

Why the SkipRearm=1 statement does not reset the activation?

Thanks

Bye

 

[WinOutreach2]

The purpose of the SkipRearm setting is to control whether activation is reset or not. A setting of 1 skips the activation reset, a setting of 0 allows the /generalize command to reset activation information in preparation for receiving new licensing. The details can be found here on TechNet.

 

[balubeto]

Before executing the sysprep /generalize /oobe /reboot /unattend:c:\CopyProfile.xml command, I have to run the "disk cleanup" utility of Windows to delete any unnecessary files or the generalize option already performs ​​this work?

If I copy the CopyProfile.xml file to the c:\windows\panther directory and I renamed it in Unattend.xml, I could remove the unattend option from the sysprep command?

Thanks

Bye