Hello,

I'm trying to make a scripted install that will not arrive at the screen I attached.

I assume it is doing this because of the administrator account not logging on.  I tried adding the following to my xml file but my build still comes up to this screen:  http://www.itninja.com/blog/view/enable-administrator-deploying-windows-7-via-scripted-install

How do I skip this?

0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Community Chosen Answer

2

Create the second account in the unattend.xml

<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>
            <UserAccounts>
                <LocalAccounts>
                    <LocalAccount wcm:action="add">
                        <Password>
                            <PlainText>true</PlainText>
                            <Value>password</Value>
                        </Password>
                        <DisplayName>2ndUser</DisplayName>
                        <Name>Second User</Name>
                        <Group>Administrators</Group>
                    </LocalAccount>
                </LocalAccounts>
                <AdministratorPassword>
                    <PlainText>True</PlainText>
                    <Value>password</Value>
                </AdministratorPassword>
            </UserAccounts>
 </component>

Answered 10/08/2012 by: SMal.tmcc
Red Belt

  • The thing is I don't want a second account. I just want one account, called administrator.
  • If you don't already have the account in the image then you can use this to make the administrator account.
  • try what nheyne suggests
    <OOBE>
    <HideEULAPage>true</HideEULAPage>
    <NetworkLocation>Other</NetworkLocation>
    <ProtectYourPC>3</ProtectYourPC>
    <SkipUserOOBE>true</SkipUserOOBE>
    </OOBE>

    you can also try what this thread suggests, name the second account administrator also
    http://social.technet.microsoft.com/Forums/en-US/w7itproinstall/thread/1d4bfa09-2c48-4799-a438-ab90a24d1979/
Please log in to comment

Answers

1

The blog you posted should allow you to activate and use the administrator account, but I'd guess the OS still wants you to create an account for normal use.

Answered 10/05/2012 by: Ben M
Ninth Degree Black Belt

  • It can be skipped, as I had it working in Altiris. Does anyone know how to get by this?
  • And I don't think that you can use the name "administrator" for that account. I generally use admin or something similar.
  • Administrator can be used, we have it working that way in Altiris.
Please log in to comment
0

Hi,

I'm planning to use K2000 for deploying Windows 7 using scripted installation. I'm using the answer file wizard and there is the option to define Administrator account and automatically login with this account after the installation. I want to use the default administrator account but KACE wizard doesn't allow that. It wants something else than this Administrator. Is this a limitation?

Answered 05/29/2013 by: JFX
Orange Belt

  • I eventually got it working but I think I did it outside the wizard by editing the setup config manually. I believe the wizard will work for you as long as you don't want to do anything fancy. For example, the wizard will let you choose a PC name, or you can leave it blank for a random name. In my case, I wanted to have my name start with the letters "DL", then have the machine serial number as the rest of the name. In order to do this, I had to use nsname which isn't available in the wizard. Since I don't want it domained until I get the name right, I had to skip that part of the wizard as well making it just about useless :) I moved the naming and domaining of the machine to a post install task.

    If the wizard doesn't work, don't be afraid to mess with it and do it on your own.

    This is what I have in my setup config on my Windows 7 build to make the local administrator account and it works:

    <LocalAccounts>
    <LocalAccount wcm:action="add">
    <Password>
    <Value>(removed)</Value>
    <PlainText>true</PlainText>
    </Password>
    <Description/>
    <DisplayName>Administrator</DisplayName>
    <Group>Administrators</Group>
    <Name>Administrator</Name>
    </LocalAccount>
    </LocalAccounts>
Please log in to comment
0

Does the K2000 use the unattend.xml? If it is using the unattend.xml then the trick is to have a new user created during the scripted install. If a user is created as part of the install then it doesn't prompt to create one. I then have a script run at first login that deletes the user I created during the install (since there's no need for it to hang around).

 

Answered 10/05/2012 by: chucksteel
Red Belt

  • It uses an unattend.xml but you can't just use the WAIK and do whatever options you want. There are some options that fail. The best method is to create your xml directly in KACE using their very basic wizard, then edit their XML to add things you want to it.

    I'd like to have administrator created during the scripted install, like I set up in Altiris. We want it to hang around.
Please log in to comment
0

You can skip that screen if you have the <SkipUserOOBE>true</SkipUserOOBE> entry in your unattend.xml file.  Having that screen appear doesn't have anything to do with whether the built-in administrator account is enabled or not.  Unless I'm misunderstanding the question?

Answered 10/05/2012 by: nheyne
Red Belt

Please log in to comment
Answer this question or Comment on this question for clarity