Sysprep is change my Image

[denmyos]

I have spend a long time setting up MDT/WDS for deploying a image.

It's all on a Vmware 10

 

Finally i got a image done, with apps

(Office 2007, skype, picasa, open office, quicktime)

 

2 user profiles (adminstrator, and a "normal" user called Laaner)

Netplwiz (control userpasswords2) was sat up so User "Laaner" would automaticly login.

Did some mmc policy change so "Laaner" wouldn't have access to the control panel etc.

 

Did a sysprep and capture my image.

And deployed it to a virtuel client.

 

I ended up with Administrator account disable,

Netplwiz resat (so no automat login)

And no policy change.

 

And right now when i look a the client desktop all the icon images are missing. :(

 

 

 

I'm i missing something here.?

 

What am i doing wrong?

 

EDIT: it looks like my Golden Image has change as well after it got sysprep.

I just wanna capture the raw Image i made, EXACTLY like I made, and deploy it looking EXACTLY the way I made it.

Edited July 11, 2014 by denmyos

[fairm010]

Are you using the Generalize switch?

[denmyos]

Are you using the Generalize switch?

 

No, i dont get one.

Should I get one.?

[Joanne]

 

The check box like this?

[clareq]

What command are you using to run sysprep? I'm assuming you're running it from an elevated command prompt?

[Joanne]

I run sysprep from c:\Windows\system32\sysprep

 

You get a nice GUI then

[fairm010]

Ah, you didn't mention which OS this is. Which OS is it?

[free780]

Autologin is a security risk. If you do have to do it push out the reg keys using gpp. Sysprep does reset windows in a way.

[denmyos]

I'm running the sysprep from the MDT server, BUT

I'm starting the Litetouch.vbs from within the client.

 

More or less like this

How to run a Sysprep and Capture Task Sequence From MDT 2010 - Ask the Core Team - Site Home - TechNet Blogs

 

**A common mistake at this point is to boot the reference computer from your LiteTouch image and start this task sequence. The sysprep and capture task sequence is designed to be run from the desktop of the reference machine similar to a post OS installation task sequence. To launch this, you will need to establish connectivity to the deployment share and launch LiteTouch.WSF manually.**

 

When i do it that way, I don't get the generalize switch.

 

The reason I'm doing it from the client and NOT from MDT TS is that i got a lot of errors

As described here, more or less.

 

 

Error starts at 24:35min (but watch the whole thing, it's great watching.)

 

I'm using the solution that starts at 28:29min, BUT mine does not get a error, like he does.

I capture, reboot and everything is nice and dandy, BUT i don't get the generalize switch, it's just starts sysprep.

Thus the image i'm getting has the administrator account disable, Netplwiz resat, no policy change.

Acording to Bernard (guy in the video) its because i'm not in audit mode (oobe)

The reason for that is that my Image is already installed, and I installed program, tweaks etc.

I should get into audit mode by pressing the ctrl+shift+F3, when I get the oobe screen, But I'm not getting a oobe screen.

 

Need help on getting the oobe screen.

I have been trying to install a fresh win7 (in vmware) but I'm not getting a oobe screen, I'm just getting right to the desktop.

 

 

I just what to duplicate the image, so I can deploy them out to my other machines, by next week.

 

 

My set up is:

 

Server 2012

MDT 2012

WDS

Client windows 7 x86

 

it's all running on vmware 10 invironment.

 

 

For the hell of it I try to pxboot from a client (outside the vmware invironment) to see if i could get a deployment going, but no cigar.

it fails to reach my wds server.

My (outside) client can ping my server (inside vmware)

 

Need help on getting from outside the vmware to inside.?

 

 

 

 

 

 

[free780]

You can enable the local admin account in the answer file.

With MDT you need to follow Microsofts best practice its not ghost.

[denmyos]

Please tell me why why WHY this sysprep is so fancy!!

 

My image has two accounts a local administrator and a normal user.

 

When i go to audit mode to set up my image, add the normal user, install software etc,

 

I then login into my newly created normal account, and install software etc.

 

BUT then when i want to get back into my administrator its disable,,,,why WHY!!!!!!

 

 

What is it i don't understand, what i'm i doing wrong.

 

I'm new to mdt/wds sysprep etc

 

I just want to capture my Image, the way i made it, so i can deploy it to my computers.

 

Why is that so hard to do.!!!! ????

[denmyos]

Well, I ended up capturing the image without sysprep it first, (I turned off a switch in TS)

 

BUT that leads to another problem.

 

It seems like I can't deploy any applications, customsetting.ini, language packs etc to the image.?

 

Is that because its not sysprep first?

 

 

There as to be a way to do this, so I get the image I want and can be able to deploy applications etc on to it, as I please.?

[free780]

By default the local administrator account is disabled when a PC is syspreped. Unless you have an answer file that enables it. You should sysyprep an image as it is best practice. If you have applications you want included in the image specify them in customsettings.ini or use the ltisuspend.vbs script this will pause the task sequence. You can install applications then resume the task sequence by clicking on the shortcut on the desktop.