Nearly sorted out my sysprep but for one thing? Logs on as local user on reboot

[reggiep]

I have been trying to set up my sysprep for quite some time for our windows 7 image.

I have managed to get the unattend.xml file to log on the machine without asking for a name or user.

I then have fog kick in, rename it and join the domain.

 

The problem is that after all this the computer still logs on as the local administrator.

 

What am I doing wrong?

[camel]

We had a similar problem for only a few machines on our domain but we deployed using WDS.

 

I can't remember exactly the issue, but it had something to do with duplicate IP address. Yep, remember now; we had issues where there were static IPs on devices within the DHCP range but DHCP had no record and dished out the IPs anyway. Some old devices were setup a while back and no record of their IPS were recorded.

 

Once the old devices were moved to the IP range outside our DHCP allocated range, the devices imaged fine with the prompt for domain login.

[ChrisMiles]

You don't need sysprep to "log onto the machine" as you put it, it is simply that sysprep requires that you MUST create an admin account during sysprep so if you don't do it in the xml file it asks you manually.

 

The correct way to get this working is to have sysprep create a temporary admin account and then delete it afterwards, rather than trying to use the normal admin one or anything.

 

To achieve this you require the following as part of your unattended xml file (obviously you will probably already have the section for the Microsoft-Windows-Shell-Setup component in your oobe section so just merge in the UserAccounts part:

 

   
       
           
               
                   
                       
                           temppassword
                           true
                       
                       TempAdmin
                       Administrators
                       TempAdmin
                   
               
           
       
   

 

Then, in your actual image add a file C:\Windows\Setup\Scripts\SetupComplete.cmd with the following command:

 

net user TempAdmin /delete

 

You wont have any problems if you do this.

Edited March 1, 2012 by ChrisMiles

[reggiep]

 

Then, in your actual image add a file C:\Windows\Setup\Scripts\SetupComplete.cmd with the following command:

 

net user TempAdmin /delete

 

You wont have any problems if you do this.

 

Thaks Chris,

i already had the local user being created but not deleted afterwards. However the command to delete the user afterwards was new to me.

[ihaveaproblem]

In the sysprep file there is a section where you can list the number of times you want it to auto logon as well. I've forgot what the line is called though...

[kv102t]

What system are you using to deploy?

[reggiep]

What system are you using to deploy?

 

If you are asking me then FOG.

 

Thought about using WDS but we have so many packages installed on our image and FOG has always worked well for us.