locked
Unable To Skip User Account Creation During Windows 7 Unattended Install RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hello,

    I am trying to create a fully unattended Windows 7 SP1 installation using Windows Deployment Services (WDS) and an image created using ImageX.  I have created two unattend files, one for WDS (works flawlessly) and one for the OOBE setup screens.

    Despite trying different configurations in my unattend file, I cannot get it to stop prompting to create a new user account.  I've been searching forums and trying different settings for days, but am having no luck.  I just tried the suggestion from the bottom of this article - http://technet.microsoft.com/en-us/library/cc732729(WS.10).aspx - which says to add a domain account to the Administrators group through the unattend file.  This did not work.  I have also tried adding a local account through the unattend file.

    I have no issue with the pc joining the domain (I prestage in AD first) and am not prompted for anything else (time zone, computer name etc.).  Could someone tell me what I need to do differently to make this work?  I need this to be fully automated so that I can deploy remotely to branch office.  Below is my unattend XML file:

     

    <?xml version="1.0" encoding="utf-8"?>
    <unattend xmlns="urn:schemas-microsoft-com:unattend">
        <settings pass="specialize">
            <component name="Microsoft-Windows-Security-SPP-UX" 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">
                <SkipAutoActivation>true</SkipAutoActivation>
            </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">
                <CopyProfile>false</CopyProfile>
                <ComputerName>%MACHINENAME%</ComputerName>
                <ShowWindowsLive>false</ShowWindowsLive>
                <TimeZone>Eastern Standard Time</TimeZone>
                <RegisteredOwner>FCFC</RegisteredOwner>
                <RegisteredOrganization>FCFC</RegisteredOrganization>
            </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>
                    <UnsecureJoin>True</UnsecureJoin>
                    <JoinDomain>FCFC.ONE</JoinDomain>
                </Identification>
            </component>
        </settings>
        <settings pass="oobeSystem">
            <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>en-us</InputLocale>
                <SystemLocale>en-us</SystemLocale>
                <UILanguage>en-us</UILanguage>
                <UserLocale>en-us</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">
                <OOBE>
                    <HideEULAPage>true</HideEULAPage>
                    <NetworkLocation>Work</NetworkLocation>
                    <ProtectYourPC>3</ProtectYourPC>
                </OOBE>
                <RegisteredOrganization>FCFC</RegisteredOrganization>
                <RegisteredOwner>FCFC</RegisteredOwner>
                <TimeZone>Eastern Standard Time</TimeZone>
                <UserAccounts>
                    <AdministratorPassword>
                        <Value>VwAyAGsAYQBkAG0AaQBuACMAMAAxAEEAZABtAGkAbgBpAHMAdAByAGEAdABvAHIAUABhAHMAcwB3AG8AcgBkAA==</Value>
                        <PlainText>false</PlainText>
                    </AdministratorPassword>
                    <LocalAccounts>
                        <LocalAccount wcm:action="add">
                            <Password>
                                <Value>VwAyAGsAYQBkAG0AaQBuACMAMAAxAFAAYQBzAHMAdwBvAHIAZAA=</Value>
                                <PlainText>false</PlainText>
                            </Password>
                            <Name>win7user</Name>
                            <Group>administrators</Group>
                        </LocalAccount>
                    </LocalAccounts>
                </UserAccounts>
            </component>
        </settings>
        <cpi:offlineImage cpi:source="wim://testisa/shared/dgm/windows7/win7_03_04_11.wim#Win7_03_04_11" xmlns:cpi="urn:schemas-microsoft-com:cpi" />
    </unattend>

    Justin Stabenow (I don't bother with all the dang titles)
    Monday, March 7, 2011 1:59 PM

Answers

  • Question
    Sign in to vote
    1
    Sign in to vote

    Hi,

     

    I suggest trying the suggestion in http://technet.microsoft.com/en-us/library/cc732729(WS.10).aspx again. Please test it using a Windows 7 image. It should work. Otherwise, maybe SP1 change this? Please sysprep the reference computer and use WDS Capture Wizard to capture the image.

     

    When I am joining clients to a domain, can I avoid creating a local user account on the computer?

     

    Yes. To do this, create an image unattend file that adds a domain account to the Administrators group. In addition, you must delete the <LocalAccounts> section if it is present in your unattend file (simply commenting it out will not work). An example file is below. Note that if domain join fails, Windows Deployment Services will not use the unattend file so you will be able to create a local account.

     

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

    <unattend xmlns="urn:schemas-microsoft-com:unattend" xmlns:ms="urn:schemas-microsoft-com:asm.v3" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State">

        <settings pass="oobeSystem">                               

            <component name="Microsoft-Windows-Shell-Setup" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" processorArchitecture="amd64">

                <UserAccounts>

                    <AdministratorPassword>

                        <Value>password</Value>

                        <PlainText>true</PlainText>

                    </AdministratorPassword>

                    <DomainAccounts>

                        <DomainAccountList wcm:action="add">

                            <DomainAccount wcm:action="add">

                                <Group>Administrators</Group>

                                <Name>DomainAdmin</Name>

                            </DomainAccount>

                            <Domain>DomainName</Domain>

                        </DomainAccountList>

                    </DomainAccounts>

                </UserAccounts>

            </component>

       </settings> 

    </unattend>

     

    Tim Quan

    TechNet Subscriber Support in forum

    If you have any feedback on our support, please contact tngfb@microsoft.com  

    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.  

    • Marked as answer by Tim Quan Wednesday, March 9, 2011 1:30 AM
    Tuesday, March 8, 2011 7:01 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Ok this is working correctly now.  All I did was simply create a new unattend file and used the same exact settings at the old unattend file.  Apparently even though the old unattend file had the correct settings, the file itself must have been corrupted somehow.  When I used the old file it either prompted me to enter a user account, or hung at "Setup is checking video performance". 

    This is the only possible explanation for this.  I am not kidding...the settings are identical when compared in Windows System Image Manager.  D*mn corrupt file!

     I tried this with no expectation that it would work, but it did.  I would recommend trying this if you are in the same scenario I was where everything seems correctly formatted, but you aren't getting the results you expect.  My unattend file is pasted below...it is a very simple one.  I have removed any information pertinent to my environment and replaced with asteriks:

    <?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">
                <ComputerName>%machinename%</ComputerName>
                <RegisteredOrganization>****</RegisteredOrganization>
                <RegisteredOwner>****</RegisteredOwner>
            </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>
                    <JoinDomain>********</JoinDomain>
                    <UnsecureJoin>true</UnsecureJoin>
                </Identification>
            </component>
        </settings>
        <settings pass="oobeSystem">
            <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>en-us</InputLocale>
                <SystemLocale>en-us</SystemLocale>
                <UILanguage>en-us</UILanguage>
                <UserLocale>en-us</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">
                <OOBE>
                    <HideEULAPage>true</HideEULAPage>
                    <NetworkLocation>Work</NetworkLocation>
                    <ProtectYourPC>3</ProtectYourPC>
                </OOBE>
                <UserAccounts>
                    <AdministratorPassword>
                        <Value>************</Value>
                        <PlainText>false</PlainText>
                    </AdministratorPassword>
                    <LocalAccounts>
                        <LocalAccount wcm:action="add">
                            <Password>
                                <Value>*************</Value>
                                <PlainText>false</PlainText>
                            </Password>
                            <Name>win7user</Name>
                            <Group>Administrators</Group>
                            <DisplayName>win7user</DisplayName>
                        </LocalAccount>
                    </LocalAccounts>
                    <DomainAccounts>
                        <DomainAccountList wcm:action="add">
                            <DomainAccount wcm:action="add">
                                <Name>Domain Users</Name>
                                <Group>Administrators</Group>
                            </DomainAccount>
                            <Domain>********</Domain>
                        </DomainAccountList>
                    </DomainAccounts>
                </UserAccounts>
                <RegisteredOwner>****</RegisteredOwner>
                <RegisteredOrganization>****</RegisteredOrganization>
                <TimeZone>Eastern Standard Time</TimeZone>
            </component>
        </settings>
        <cpi:offlineImage cpi:source="***************************" xmlns:cpi="urn:schemas-microsoft-com:cpi" />
    </unattend>

    Justin Stabenow (I don't bother with all the dang titles)
    • Marked as answer by Tim Quan Wednesday, March 9, 2011 1:30 AM
    Tuesday, March 8, 2011 8:43 PM

All replies

  • Question
    Sign in to vote
    1
    Sign in to vote

    Hi,

     

    I suggest trying the suggestion in http://technet.microsoft.com/en-us/library/cc732729(WS.10).aspx again. Please test it using a Windows 7 image. It should work. Otherwise, maybe SP1 change this? Please sysprep the reference computer and use WDS Capture Wizard to capture the image.

     

    When I am joining clients to a domain, can I avoid creating a local user account on the computer?

     

    Yes. To do this, create an image unattend file that adds a domain account to the Administrators group. In addition, you must delete the <LocalAccounts> section if it is present in your unattend file (simply commenting it out will not work). An example file is below. Note that if domain join fails, Windows Deployment Services will not use the unattend file so you will be able to create a local account.

     

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

    <unattend xmlns="urn:schemas-microsoft-com:unattend" xmlns:ms="urn:schemas-microsoft-com:asm.v3" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State">

        <settings pass="oobeSystem">                               

            <component name="Microsoft-Windows-Shell-Setup" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" processorArchitecture="amd64">

                <UserAccounts>

                    <AdministratorPassword>

                        <Value>password</Value>

                        <PlainText>true</PlainText>

                    </AdministratorPassword>

                    <DomainAccounts>

                        <DomainAccountList wcm:action="add">

                            <DomainAccount wcm:action="add">

                                <Group>Administrators</Group>

                                <Name>DomainAdmin</Name>

                            </DomainAccount>

                            <Domain>DomainName</Domain>

                        </DomainAccountList>

                    </DomainAccounts>

                </UserAccounts>

            </component>

       </settings> 

    </unattend>

     

    Tim Quan

    TechNet Subscriber Support in forum

    If you have any feedback on our support, please contact tngfb@microsoft.com  

    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.  

    • Marked as answer by Tim Quan Wednesday, March 9, 2011 1:30 AM
    Tuesday, March 8, 2011 7:01 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Tim,

    I have tried this, but will try again in case I messed up a step and then post the results.

    Justin Stabenow (I don't bother with all the dang titles)
    Tuesday, March 8, 2011 1:34 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Ok this is working correctly now.  All I did was simply create a new unattend file and used the same exact settings at the old unattend file.  Apparently even though the old unattend file had the correct settings, the file itself must have been corrupted somehow.  When I used the old file it either prompted me to enter a user account, or hung at "Setup is checking video performance". 

    This is the only possible explanation for this.  I am not kidding...the settings are identical when compared in Windows System Image Manager.  D*mn corrupt file!

     I tried this with no expectation that it would work, but it did.  I would recommend trying this if you are in the same scenario I was where everything seems correctly formatted, but you aren't getting the results you expect.  My unattend file is pasted below...it is a very simple one.  I have removed any information pertinent to my environment and replaced with asteriks:

    <?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">
                <ComputerName>%machinename%</ComputerName>
                <RegisteredOrganization>****</RegisteredOrganization>
                <RegisteredOwner>****</RegisteredOwner>
            </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>
                    <JoinDomain>********</JoinDomain>
                    <UnsecureJoin>true</UnsecureJoin>
                </Identification>
            </component>
        </settings>
        <settings pass="oobeSystem">
            <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>en-us</InputLocale>
                <SystemLocale>en-us</SystemLocale>
                <UILanguage>en-us</UILanguage>
                <UserLocale>en-us</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">
                <OOBE>
                    <HideEULAPage>true</HideEULAPage>
                    <NetworkLocation>Work</NetworkLocation>
                    <ProtectYourPC>3</ProtectYourPC>
                </OOBE>
                <UserAccounts>
                    <AdministratorPassword>
                        <Value>************</Value>
                        <PlainText>false</PlainText>
                    </AdministratorPassword>
                    <LocalAccounts>
                        <LocalAccount wcm:action="add">
                            <Password>
                                <Value>*************</Value>
                                <PlainText>false</PlainText>
                            </Password>
                            <Name>win7user</Name>
                            <Group>Administrators</Group>
                            <DisplayName>win7user</DisplayName>
                        </LocalAccount>
                    </LocalAccounts>
                    <DomainAccounts>
                        <DomainAccountList wcm:action="add">
                            <DomainAccount wcm:action="add">
                                <Name>Domain Users</Name>
                                <Group>Administrators</Group>
                            </DomainAccount>
                            <Domain>********</Domain>
                        </DomainAccountList>
                    </DomainAccounts>
                </UserAccounts>
                <RegisteredOwner>****</RegisteredOwner>
                <RegisteredOrganization>****</RegisteredOrganization>
                <TimeZone>Eastern Standard Time</TimeZone>
            </component>
        </settings>
        <cpi:offlineImage cpi:source="***************************" xmlns:cpi="urn:schemas-microsoft-com:cpi" />
    </unattend>

    Justin Stabenow (I don't bother with all the dang titles)
    • Marked as answer by Tim Quan Wednesday, March 9, 2011 1:30 AM
    Tuesday, March 8, 2011 8:43 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    If you want the OOBE to be skipped in terms of account creation and/or computer name, in Windows 7 you need to skipmachineOOBE. Make sure that you have not filled in the computer name in the Specialize-phase (Shell-Setup), otherwise there will be a conflict that will halt the system during first startup due to problems in the answer file. Please note that this also works if you are not joining the computer to a domain.

    <OOBE>
   <SkipMachineOOBE>true</SkipMachineOOBE>
</OOBE>

    Please note what is said about this in the System Image Manager Help section:

    SkipMachineOOBE should be used only in a test environment, and you should never ship a computer with the SkipMachineOOBE setting configured to true.

    If you use this setting in Windows® 7, Windows Welcome will be skipped, and any settings that a user selects during Windows Welcome will not be configured. For example, user-account creation, language, and time-zone settings will not be configured. Some Windows features may not function, as they depend on Windows Welcome values such as ProtectYourPC, which does not include a default value.


    • Edited by Joel Lehtonen Tuesday, March 19, 2013 11:43 AM Adding information
    Tuesday, March 19, 2013 11:40 AM
  • Question
    Sign in to vote
    0
    Sign in to vote


    To Skip User Account Creation

    please add or edit the following to your unattend.xml  settings pass=" speicalize "  

    <settings pass="specialize">
        <component name="Microsoft-Windows-Deployment" 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">
            <RunSynchronous>   
                <RunSynchronousCommand wcm:action="add">
            <Description>delete Admin folder</Description>    
             <Order>1</Order>
            <Path>cmd /c rd /s /q c:\users\administrator"</Path>
         </RunSynchronousCommand>       
        <RunSynchronousCommand wcm:action="add">
                    <Description>EnableAdmin</Description>
                    <Order>2</Order>
                    <Path>cmd /c net user Administrator /active:yes</Path>
                </RunSynchronousCommand>
                <RunSynchronousCommand wcm:action="add">
                    <Description>UnfilterAdministratorToken</Description>
                    <Order>3</Order>
                    <Path>cmd /c reg add HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System /v FilterAdministratorToken /t REG_DWORD /d 0 /f</Path>
                </RunSynchronousCommand>
                <RunSynchronousCommand wcm:action="add">
                    <Description>disable user account page</Description>
                    <Order>4</Order>
                    <Path>reg add HKLM\Software\Microsoft\Windows\CurrentVersion\Setup\OOBE /v UnattendCreatedUser /t REG_DWORD /d 1 /f</Path>
                </RunSynchronousCommand>
            </RunSynchronous>
        </component>
        <component name="Microsoft-Windows-Security-SPP-UX" 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">
            <SkipAutoActivation>true</SkipAutoActivation>
        </component>
        <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">
            <ComputerName>*</ComputerName>
            <CopyProfile>true</CopyProfile>
            <DisableAutoDaylightTimeSet>true</DisableAutoDaylightTimeSet>
            <ShowWindowsLive>false</ShowWindowsLive>
            <RegisteredOwner></RegisteredOwner>
            <RegisteredOrganization></RegisteredOrganization>
            <TimeZone>China Standard Time</TimeZone>
        </component>
    </settings>


    • Edited by qyua007 Sunday, May 19, 2013 10:53 AM
    • Proposed as answer by laufer.ben Thursday, October 17, 2013 4:32 PM
    Sunday, May 19, 2013 10:50 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    I've been struggling with getting this to work for nearly two days, and I found all this information not helpful at all. Sorry.

    Here's my workaround for this:

    https://dl.dropboxusercontent.com/u/90275400/unattend.png (since pasting xml files is lame)

    IV Specialize:

    - Shell-Setup_neutral:

    fill in ComputerName, ProductKey, RegisteredOrganization, RegisteredOwner, TimeZone

    - UnattendedJoin_neutral:

    fill in domain name in Identification > JoinDomain, UnsecureJoin: false

    fill in Credentials, delete Provisioning

    VII oobeSystem:

    - Shell-Setup_neutral:

    Once again fill in RegisteredOrganization, RegisteredOwner and TimeZone.

    Also fill in AutoLogon info and password.

    Fill in first four settings in OOBE.

    Enter AdministratorPassword (its for the Admin account which is not used by default).

    Fill in DomainAccounts and make sure that at least one account MATCHES the one from AutoLogon.

    Add one account in LocalAccounts (it has to be there, you can delete it after installation).

    Delete unused boxes (like in attached picture).

    And that's it! Windows will now automatically join a domain, then login using domain account. The local account will be created but it can be safely deleted when setup is complete.

    What happens if you don't add a local account:

    Windows setup will prompt for a name of a local user. After adding one it will still login using domain account, but 'RegisteredOwner' setting will change to match the local user name.

    Hope this helps!

    Tested on Windows 7 SP1 x64
    Thursday, May 1, 2014 5:27 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    After SP1, i have had to mount the Wim file after i have captured it and then load the software registry hive into regedit and add this key.  Prior to SP1, we didn't need to do this but this eliminates our user account creation after we sysprep and then deploy a Win7 SP1 based image.  

    Add HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup\OOBE

    UnattendCreatedUser   

    REG_DWORD    0x1

    Friday, July 18, 2014 8:41 PM
  • Question
    Sign in to vote
    1
    Sign in to vote

    After SP1, i have had to mount the Wim file after i have captured it and then load the software registry hive into regedit and add this key.  Prior to SP1, we didn't need to do this but this eliminates our user account creation after we sysprep and then deploy a Win7 SP1 based image.  

    Add HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup\OOBE

    UnattendCreatedUser   

    REG_DWORD    0x1

    this holds true in Windows 10 Deployments too and allows 'thick image' creation. :)
    • Proposed as answer by Jason R Henley Tuesday, November 12, 2019 8:12 PM
    Monday, February 20, 2017 4:55 AM