O/S Deployment Thread, HELP!!! Sysprep is driving me mad in Technical; I have set up MDT and have a reference machine ready.
I am trying to follow MS instructions on setting ...
18th July 2013, 08:39 AM #1
HELP!!! Sysprep is driving me mad
I have set up MDT and have a reference machine ready.
I am trying to follow MS instructions on setting up a Default User Profile. The instructions say to remove all accounts except the built in administrator. Login as administrator (we have set an administrator password) and set your profile up as you want it. Log off and then open a session to the MDT server run the litetouch.vbs from within windows. MDT Captures the image and the result i get is it finished with 0 errors and the machine can be rebooted. Once the reference machine reboots and I try to login the administrator account has been disabled and I have no way of logging into my reference machine!!!
I havent tried deploying the image yet to see if the admin account gets re-enabled by MDT on the deployed machine.
How are you supposed to login to the reference machine again if you need to make changes?
where have I gone wrong?
18th July 2013, 09:11 AM #2
Ah yeah, I found that quite annoying - Sysprep does disable the local Admin account unless you enable it in your sysprep answer file.
From what I remember, you have to add it in two places:
In the oobeSystem pass you set the password and tell it to auto-logon:
and then in the specialize pass you have to set it back to active:
net user administrator /active:yes
18th July 2013, 09:32 AM #3
@Valyyn - Im new to MDT and havent used sysprep since XP. Is the answer file you mention the same as the unattend.xml that is found when you go into the task sequence and click on osinfo?
18th July 2013, 09:36 AM #4
I'm the other way and I've not really used MDT! It is the unattend.xml though, yes
It's the one you call with Sysprep
(e.g. C:\Windows\System32\sysprep\sysprep.exe /oobe /generalize /shutdown /unattend:unattend.xml)
18th July 2013, 09:38 AM #5
As long as you set the admin password in the ts. It should add it to the answer file. I prefer seperate ts for capture and deploy.
18th July 2013, 09:41 AM #6
I do have a separate task sequence for capture & separate one for deploy
Originally Posted by free780
Where do you set it for the capture ts?
Last edited by fiza; 18th July 2013 at 09:42 AM.
18th July 2013, 09:59 AM #7
just checked my answer file.
For my Capture task I have ;
Under this setting I have "Path cmd /c net user Administrator /active:yes"
Under the Ooobe Autologon
Under password I have set my own password
Under UserAccounts I have matched the AdministratorPassword to be the same
So in theory this should capture my image and then when I reboot my reference machine the answer file should enable the admin account? But it didnt!
Last edited by fiza; 18th July 2013 at 10:01 AM.
18th July 2013, 10:09 AM #8
I found this webpage useful when setting up a sysprep unattend.xml file
Sysprep a Windows 7 Machine
18th July 2013, 10:24 AM #9
According to that article I should have
1. Password: Administrator Password
Description: Local Administrator
AdministratorPassword: Administrator Password
Which I didnt but have now added. Will see how it goes and let you know.
18th July 2013, 12:01 PM #10
i had issue with this so didnt set the password for the local admin and do that manually at the moment as i had an attack of "omg the password is in plain text in the answer file"
18th July 2013, 01:15 PM #11
You do not need to edit your sysprep or the unattended file.
So i had exactly the same error a while ago.
Did you use an original windows seven DVD to install your reference machine ?
Did you at some point modify the original windows 7 with RT Lite Touch or something similar ?
My reference machine was fine and I could run the sysprep and capture with no error but I was block on the admin logon as soon as the computer was restarting.
My W7 was a W7 that I modified myself using RT7 lite touch.
To solve the problem I had to star all over with W7 pro original, and install all the updates manually.
I also had to make sure that the administrator password was the same on my local machine and also my task sequence (even if the sysprep gets ride of it).
Hope that helps
Last edited by steewy; 18th July 2013 at 01:16 PM.
18th July 2013, 01:20 PM #12
I started from scratch with W7 volume Licence (EES) version. I didnt use RT Lite. The password is the same in the ts and the reference machine.
Originally Posted by steewy
18th July 2013, 01:24 PM #13
I never activated my refrerence machine. I leave the activation blank.
Originally Posted by fiza
You might need to try an other ISO. It's a pain but it fixed the problem for me.
To do so I had a virtual machine with snapshots. Just install the machine with admin account same password as the TS and Deployment task.
Capture the image without any software or updates.
Also to know if your windows is "OK" you can run the sysprep manually without using MDT.
If it fails you know that your issues comes from your windows and not your server.
Take a snapshot of your virtual machine and run C:\Windows\System32\sysprep.
Does it work without getting any errors ?
18th July 2013, 01:29 PM #14
One extra thing not sure it helps but every time I capture an image I change the MDT rules and bootstrap to keep it simple without affecting the image and since I do that no more admin login isues.
It might look short but it's all you need.
Could you show me your rules and bootstrap ?
18th July 2013, 01:53 PM #15
Last edited by fiza; 18th July 2013 at 01:57 PM.
By gill in forum Educational Software
Last Post: 3rd October 2012, 01:08 PM
By cheredenine in forum Virtual Learning Platforms
Last Post: 4th May 2012, 01:49 PM
By witch in forum Windows
Last Post: 15th September 2010, 10:30 PM
By witch in forum General Chat
Last Post: 15th September 2010, 09:54 AM
By cheredenine in forum Windows
Last Post: 30th July 2008, 11:49 AM
Users Browsing this Thread
There are currently 1 users browsing this thread. (0 members and 1 guests)