windows 7 sysprep keep asking for username

Page 1 of 2 12 LastLast

  1. Posts : 4
    windows 7 professional
       #1

    windows 7 sysprep keep asking for username


    i created an answer key with windows system image manager for windows 7 professional 64 bit. everything works fine. but when i run sysprep with it keeps asking me for a username is there a way to not ask for username during sysprep and only ask for computer name. i created a local profile on there that i want them to use. the computer is not on the domain. basically i just want it to ask for computer name and not a username to create a new acct. i have made two profiles admin and a standard user one. i don't want to create a 3rd account. i tried theitbros method it still keeps asking for it.
      My Computer


  2. Posts : 17,545
    Windows 10 Pro x64 EN-GB
       #2

    Hi Noobie7, welcome to the Seven Forums.

    I have some difficulties in understanding your issue? Sysprep does not ask username.

    Could you please try to explain your issue with a bit more information. It would also help if you could post the answer file you are using (tutorial: Screenshots and Files - Upload and Post in Seven Forums).

    Kari
      My Computer


  3. Posts : 4
    windows 7 professional
    Thread Starter
       #3

    when i run the cmd sysprep /generalize /oobe /shutdown /unattend:unattend.xml it would shutdown it down and do OOBE and ask for username and computer name. i want to just ask for computer name and automatic login to windows without creating a acct. i enabled the hidden admin account it still does that. i will try upload the answer key later
      My Computer


  4. Posts : 17,545
    Windows 10 Pro x64 EN-GB
       #4

    You need to create a normal administrative user account in answer file. Enabling the built-in administrator account in answer file does not count as OOBE boot needs at least one normal administrative account to be created, either automatically using an answer file or manually while finalizing installation.

    Anyway, that shouldn't be an issue. Why don't you just input the initial user credentials when finalizing installation?

    For what purpose are you creating the Windows image?

    Kari
      My Computer


  5. Posts : 4
    windows 7 professional
    Thread Starter
       #5

    the purpose is we purchased a bunch of laptop for emergency use in case the internet went down and can't log in to the domain. I want to create a image with a standard account called emergency on each of the laptop with all the default settings. I tried creating the account called emergency and running the sysprep. it still ask to create a new account I clicked copy profile true. on this answer key I created admin account still same thing.

    <?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="Error" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
    <SkipRearm>1</SkipRearm>
    </component>
    </settings>
    <settings pass="specialize">
    <component name="Microsoft-Windows-Deployment" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="Error" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
    <RunSynchronous>
    <RunSynchronousCommand wcm:action="add">
    <Order>1</Order>
    <Path>net user administrator /active:yes</Path>
    </RunSynchronousCommand>
    </RunSynchronous>
    </component>
    <component name="Microsoft-Windows-Security-SPP-UX" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="Error" 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="Error" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
    <CopyProfile>true</CopyProfile>
    <ShowWindowsLive>false</ShowWindowsLive>
    <TimeZone>Eastern Standard Time</TimeZone>
    </component>
    <component name="Microsoft-Windows-IE-InternetExplorer" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="Error" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
    <Home_Page>http://nybloodcenter.org</Home_Page>
    </component>
    </settings>
    <settings pass="oobeSystem">
    <component name="Microsoft-Windows-International-Core" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="Error" 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="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="Error" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
    <RegisteredOrganization>New York Blood Center</RegisteredOrganization>
    <RegisteredOwner>NYBC MIS</RegisteredOwner>
    <AutoLogon>
    <Password>
    <Value>TABUAGUANAAzADAAcABhAHMAcwB3AG8AcgBkAFAAYQBzAHMAdwBvAHIAZAA=</Value>
    <PlainText>false</PlainText>
    </Password>
    <Enabled>true</Enabled>
    <LogonCount>5</LogonCount>
    <Username>administrator</Username>
    </AutoLogon>
    <FirstLogonCommands>
    <SynchronousCommand wcm:action="add">
    <CommandLine>cscript /b c:\windows\system32\slmgr.vbs /ipk XXXXX-XXXXX-XXXXX-XXXXX-XXXXX</CommandLine>
    <Order>1</Order>
    <RequiresUserInput>false</RequiresUserInput>
    </SynchronousCommand>
    <SynchronousCommand wcm:action="add">
    <CommandLine> cscript /b c:\windows\system32\slmgr.vbs /ato</CommandLine>
    <Order>2</Order>
    <RequiresUserInput>false</RequiresUserInput>
    </SynchronousCommand>
    </FirstLogonCommands>
    <OOBE>
    <HideEULAPage>true</HideEULAPage>
    <NetworkLocation>Work</NetworkLocation>
    <ProtectYourPC>1</ProtectYourPC>
    </OOBE>
    <UserAccounts>
    <AdministratorPassword>
    <Value>TABUAGUANAAzADAAcABhAHMAcwB3AG8AcgBkAEEAZABtAGkAbgBpAHMAdAByAGEAdABvAHIAUABhAHMAcwB3AG8AcgBkA A==</Value>
    <PlainText>false</PlainText>
    </AdministratorPassword>
    <LocalAccounts>
    <LocalAccount wcm:action="add">
    <Password>
    <Value>TABUAGUANAAzADAAcABhAHMAcwB3AG8AcgBkAFAAYQBzAHMAdwBvAHIAZAA=</Value>
    <PlainText>false</PlainText>
    </Password>
    <Description>local administrator</Description>
    <DisplayName>administrator</DisplayName>
    <Group>administrator</Group>
    <Name>administrator</Name>
    </LocalAccount>
    </LocalAccounts>
    </UserAccounts>
    </component>
    </settings>
    <cpifflineImage cpi:source="catalog:d:/sources/install_windows 7 professional.clg" xmlns:cpi="urn:schemas-microsoft-com:cpi" />
    </unattend>
      My Computer


  6. Posts : 4
    windows 7 professional
    Thread Starter
       #6

    I think I figured it out I had to create two account admin and emergency account. now when I run the sysprep cmd all it ask for is just the computer name. is there a way to set the emergency as a standard account instead of admin.
      My Computer


  7. Posts : 17,545
    Windows 10 Pro x64 EN-GB
       #7

    You need to start again, that answer file contains so many errors.

    First, that answer file contains no information about user profile named "Emergency", so of course it's not possible for Windows to know that user should be created and logon automatically.

    The answer file contains auto logon credentials for built-in administrator account but as I have earlier told you, a local administrative user must be created, OOBE boot can not finish installation without at least one local account.

    At the end of the answer file you create a local administrative account named Administrator. You cannot do that as the name is reserved for built-in administrator account.

    My recommendation: Make a pot of coffee, take your time and read this tutorial thoroughly through: System Preparation Tool - Use to Customize Windows.

    Kari


    EDIT:

    Saw your last post only after posting the above. Well done.

    The first account, the initial user profile created when Windows installation is finalized in OOBE boot is and must always be an administrative account. There's no way to go around that.

    You might want to create two local accounts, for instance Admin (local administrator) and Emergency (local standard user), then set Emergency auto logon in answer file.
      My Computer


  8. Posts : 3
    Windows 8.1 Enterprise x64
       #8

    I know this is a super old post but i hate to make a new post with the same subject....

    Anyways, i'm creating an answer file for Windows 7 Enterprise x64 that does not prompt for the user to create a account just to Name the PC. I read that i'm suppose to create another administrator account other than the build-in administrator account are the oobeSystem section will not run. My question is, where in the answer file do i create the other administrator account and then how is it used for the oobeSystem?

    If someone could post or email a answer file that enables the local administrator account and creates a second administrator account and then show how it's used in the oobesystem so the username is not asked for, i would be most appreciative.
    Last edited by rkhuprus; 13 Jan 2015 at 09:15.
      My Computer


  9. Posts : 17,545
    Windows 10 Pro x64 EN-GB
       #9

    rkhuprus said:
    If someone could post are email a answer file that enables the local administrator account and creates a second administrator account and then show how it's used in the oobesystem so the username is not asked for, i would be most appreciative.
    Hi Rkhuprus, welcome to the Seven Forums.

    Below an example about how to create a local administrator account called "UserName".

    • In Windows SIM (System Image Manager), right click component xxx_Microsoft-Windows-Shell-Setup_z.z.zzzz.zzzzz_neutral adding it to Pass 7 OobeSystem (xxx = x86 or amd64, z.z.zzzz.zzzzz = Windows build, depending on Windows image you are using):

      windows 7 sysprep keep asking for username-2015-01-13_00h46_53.png
    • Expand it under Pass 7 OobeSystem in Answer File pane in the middle and you'll find UserAccounts item
    • Expand UserAccounts, right click LocalAccounts, select Insert New LocalAccount:

      windows 7 sysprep keep asking for username-2015-01-13_00h47_56.png
    • Add the user by filling / selecting the details in Properties in respective input fields:
      • Action > AddListItem
      • Description > Local Administrator (or any description you'd prefer)
      • DisplayName > UserName (what name you'd like to be displayed for this user)
      • Group > Administrators (must be existing Windows user group like Administrators, Users and so on)
      • Name > UserName (name of the user profile & profile folder)

      windows 7 sysprep keep asking for username-2015-01-13_00h50_13.png
    • Expand the item LocalAccount[name="UserName"], click item Password
    • In input field Value, enter your preferred password for this account:

      windows 7 sysprep keep asking for username-2015-01-13_00h50_57.png

    That's it. More information on Microsoft TechNet: UserAccounts

    Kari
    Last edited by Kari; 13 Jan 2015 at 06:39. Reason: Added screenshots
      My Computer


  10. Posts : 3
    Windows 8.1 Enterprise x64
       #10

    Thanks Kari! Just one more question, is that all that needs to be done for Windows 7 to not ask for User setup during initial installation?
      My Computer


 
Page 1 of 2 12 LastLast

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 01:21.
Find Us