Windows 7 Sysprep File

[tbharris09]

I am currently working on the deployment plan for my company. I have ran in to a snag with the Windows 7 sysprep file. I would like for it to stop and all me to me to give the machine a name but not allow the creation of a local user account. Since all machines will be part of our domain they will use that account instead. I am able to set the machine name and create a local user name but have not found a solution to just create the machine name.

Has anyone found a way to do this?

[Ric_]

Did you use MDT 2010 to create the unattended setup files? There is quite fine grained control in there.

[jsnetman]

You can also use a utility called MySysprep which is a rewrite of MS Sysprep.

http://tsaysoft.com/mysysprep2/

[tbharris09]

Yes I used the MDT. I will check out the other tool listed.

Like I said I can get it to put in a generic name or stop let me set the name. If it is set to let me create a name I have to also create a local ID.

[Ste_Harve]

I've just finished tweaking my unattend.xml for win 7. I use WDS to deploy and have it set to unattended install. All my machines are pre-staged in AD so it pulls the name from there. It stops to ask me for a product key and thats it. If this is any use let me know and i'll post it here.

[Tricky_Dicky]

If this is any use let me know and i'll post it here.

I don't know about the original poster but I'd love a look at that.

Rich

[Ste_Harve]

Well here's my xml file. Will probably get a few more tweaks done as i learn more!!

<?xml version="1.0" encoding="utf-8"?>
<unattend xmlns="urn:schemas-microsoft-com:unattend">
<settings pass="generalize">
<component name="Microsoft-Windows-PnpSysprep" 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">
<PersistAllDeviceInstalls>true</PersistAllDeviceInstalls>
<DoNotCleanUpNonPresentDevices>true</DoNotCleanUpNonPresentDevices>
</component>
<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-IE-InternetExplorer" 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">
<DisableFirstRunWizard>true</DisableFirstRunWizard>
<SuggestedSitesEnabled>false</SuggestedSitesEnabled>
</component>
<component name="Microsoft-Windows-International-Core" 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">
<InputLocale>0809:00000809</InputLocale>
<SystemLocale>en-gb</SystemLocale>
<UILanguage>en-gb</UILanguage>
<UILanguageFallback>en-gb</UILanguageFallback>
<UserLocale>en-gb</UserLocale>
</component>
<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">
<ComputerName>%MACHINENAME%</ComputerName>
<CopyProfile>true</CopyProfile>
<RegisteredOrganization>Walton-le-Dale Arts College</RegisteredOrganization>
<RegisteredOwner>Walton-le-Dale Arts College</RegisteredOwner>
<ShowWindowsLive>false</ShowWindowsLive>
<TimeZone>GMT Standard Time</TimeZone>
<BluetoothTaskbarIconEnabled>false</BluetoothTaskbarIconEnabled>
</component>
<component name="Microsoft-Windows-UnattendedJoin" 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">
<Identification>
<Credentials>
<Domain>WALTONLEDALE.ARTS</Domain>
<Password>PASSWORD</Password>
<Username>administrator</Username>
</Credentials>
<JoinDomain>WALTONLEDALE.ARTS</JoinDomain>
</Identification>
</component>
<component name="Microsoft-Windows-DNS-Client" 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">
<DNSDomain>WALTONLEDALE.ARTS</DNSDomain>
<UseDomainNameDevolution>true</UseDomainNameDevolution>
</component>
<component name="Microsoft-Windows-SystemRestore-Main" 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">
<DisableSR>1</DisableSR>
</component>
<component name="Microsoft-Windows-TerminalServices-LocalSessionManager" 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">
<fDenyTSConnections>false</fDenyTSConnections>
</component>
</settings>
<settings pass="oobeSystem">
<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">
<OOBE>
<HideEULAPage>true</HideEULAPage>
<HideWirelessSetupInOOBE>true</HideWirelessSetupInOOBE>
<NetworkLocation>Work</NetworkLocation>
<ProtectYourPC>1</ProtectYourPC>
</OOBE>
<WindowsFeatures>
<ShowMediaCenter>false</ShowMediaCenter>
</WindowsFeatures>
<UserAccounts>
<LocalAccounts>
<LocalAccount wcm:action="add">
<Password>
<Value>dwA0ACEAdAAwAG4AUABhAHMAcwB3AG8AcgBkAA==</Value>
<PlainText>false</PlainText>
</Password>
<Description>Local Admin</Description>
<DisplayName>Admin</DisplayName>
<Group>Administrators</Group>
<Name>Admin</Name>
</LocalAccount>
</LocalAccounts>
</UserAccounts>
</component>
</settings>
<settings pass="auditSystem">
<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">
<UserAccounts>
<AdministratorPassword>
<Value>dwA0ACEAdAAwAG4AQQBkAG0AaQBuAGkAcwB0AHIAYQB 0AG8AcgBQAGEAcwBzAHcAbwByAGQA</Value>
<PlainText>false</PlainText>
</AdministratorPassword>
</UserAccounts>
<Display>
<ColorDepth>32</ColorDepth>
<DPI>120</DPI>
<HorizontalResolution>1280</HorizontalResolution>
<RefreshRate>60</RefreshRate>
<VerticalResolution>800</VerticalResolution>
</Display>
</component>
</settings>
<cpifflineImage cpi:source="wim://services/e$/win7prox86/sources/install.wim#Windows 7 PROFESSIONAL" xmlns:cpi="urn:schemas-microsoft-com:cpi" />
</unattend>

Ste

[Fatmas]

I used a mixture of this guide (upto step #12):

Sysprep a Windows 7 Machine ? Start to Finish V2 - Blog.BrianLeeJackson.com


And this guide:

Windows 7 Sysprep – Tips & tricks TXT (dot) bitprocessor (dot) be


It's basically a VBS script which runs after the machine has been sysprepped. On the first run a window pops up and prompts for a computer name BEFORE it joins the domain.

That second link was very useful as it had a sysprep.xml file that could be changed.

Hope this helps, we have just started getting some success with deploying Windows 7 using this and Ghost

[57chevvy]

I used a mixture of this guide (upto step #12):

Sysprep a Windows 7 Machine ? Start to Finish V2 - Blog.BrianLeeJackson.com


And this guide:

Windows 7 Sysprep – Tips & tricks TXT (dot) bitprocessor (dot) be


It's basically a VBS script which runs after the machine has been sysprepped. On the first run a window pops up and prompts for a computer name BEFORE it joins the domain.

That second link was very useful as it had a sysprep.xml file that could be changed.

Hope this helps, we have just started getting some success with deploying Windows 7 using this and Ghost

Hi

Have none of you had difficulty with the copyprofile function as this is the only thing outstanding for me in Windows 7 preparation that is causing real hassle.?

Sysprep always fails when this is included. I have read many and various forums on this and it would appear to be not an uncommon problem but as nobody here mentioned this I would be pleased to know more if possible.

Basically, we are looking for a way of configuring a "default user" profile to use probably ultimately as a mandatory .v2 roaming from the server but cannot reliably create one locally for this purpose. This was a doddle for XP but Windows 7 appears not particularly enterprise friendly at the moment to me.

The Microsoft prose is to only have one account (say administrator) configure that as required with the required personalised settings etc. Make sure no other profiles exist on the workstation and as part of sysprep this will be copied to "default user" during sysprep and then all subsequent logons (to the workstation) will be given this personalised profile.

The base Microsft article How to customize default user profiles in Windows 7 and in Windows Server 2008 R2 on the subject is eloquent but does not work.

The Brian Lee Jackson one is also helpful but incomplete.

It is implied the "other" changes occur to the default profile during the sysprep process although no documentation is available to expand on this.

Having used sysprep for several years I am certainly familiar with its operation and am frankly surprised and disappointed by the copyprofile difficulty being encountered.

So if you folks have a magic bullet for this I would be pleased to learn more if possible.

Rgds

[garethedmondson]

Hi

Have none of you had difficulty with the copyprofile function as this is the only thing outstanding for me in Windows 7 preparation that is causing real hassle.?

Sysprep always fails when this is included. I have read many and various forums on this and it would appear to be not an uncommon problem but as nobody here mentioned this I would be pleased to know more if possible.

Basically, we are looking for a way of configuring a "default user" profile to use probably ultimately as a mandatory .v2 roaming from the server but cannot reliably create one locally for this purpose. This was a doddle for XP but Windows 7 appears not particularly enterprise friendly at the moment to me.

The Microsoft prose is to only have one account (say administrator) configure that as required with the required personalised settings etc. Make sure no other profiles exist on the workstation and as part of sysprep this will be copied to "default user" during sysprep and then all subsequent logons (to the workstation) will be given this personalised profile.

The base Microsft article How to customize default user profiles in Windows 7 and in Windows Server 2008 R2 on the subject is eloquent but does not work.

The Brian Lee Jackson one is also helpful but incomplete.

It is implied the "other" changes occur to the default profile during the sysprep process although no documentation is available to expand on this.

Having used sysprep for several years I am certainly familiar with its operation and am frankly surprised and disappointed by the copyprofile difficulty being encountered.

So if you folks have a magic bullet for this I would be pleased to learn more if possible.

Rgds

Did you manage to get anywhere with the copyprofile aspect of the sysprep process? This is my next step.

Gareth