Hello,

is there a script to automaticly do a sysprep /generalize /oobe after an image has been deployed?

thanx
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
Not built into the box, but you could definitely do it.

Just add your sysprep answer file as a post install task.

Create a bat script to copy the file to C:\windows\system32\sysprep and run the command line.

Just make sure its your last task.
Answered 02/01/2011 by: dchristian
Red Belt

Please log in to comment
0
is it by the way possible to apply a new computername (or one fetched from a pre-install script) without having a syspreped image?
the supplied example script is only for syspreped images without errors.
Answered 02/02/2011 by: petrybosch
Senior Yellow Belt

Please log in to comment
0
There's a built in naming rule type of task that uses WSNAME. In postinstall, go to Choose Action dropdown and select naming rule; WSNAME can either be automated to use an answer file database (Our default), or build naming scheme with automated criteria.

Name database expects a text file with a variable (usually MAC address or Serial Number) and hostname to match to. Criteria based command line can get complex; see http://mystuff.clarke.co.nz/MyStuff/wsname.asp for more details on usage.
Answered 02/02/2011 by: cblake
Red Belt

Please log in to comment
0
the build-in task requires a sysprep (see the vbs code of it).
i just need to have something like that (or like newSID) but without a sysprep
Answered 02/02/2011 by: petrybosch
Senior Yellow Belt

Please log in to comment
0
Check the "Choose Action" dropdown; there's a type of task called Naming Rule. This leverages the WSNAME tool and can be used in Scripted installs or System images.
Answered 02/02/2011 by: cblake
Red Belt

Please log in to comment
0
i found it, thank you

using it without any parameters gives a form where you can enter the correct computer name.
after that you need to join/re-join the computer to the domain
Answered 02/03/2011 by: petrybosch
Senior Yellow Belt

Please log in to comment
0
petrybosch,

You might want to look at calling wsname with the /rcid switch.

This will rename the existing computer in the domain for you.

Ex:
wsname.exe /N:NewName /ricd /user:domain\adminsitrator /pass:password /deleteexisting
Answered 02/03/2011 by: dchristian
Red Belt

Please log in to comment
0
I find it strange that I don't have to use the /rcid switch when I re-image a machine that was already part of our domain. I am not sure why I don't, but I actually got WSName failures when I tried this. It works fine without it though.

ORIGINAL: dchristian

petrybosch,

You might want to look at calling wsname with the /rcid switch.

This will rename the existing computer in the domain for you.

Ex:
wsname.exe /N:NewName /ricd /user:domain\adminsitrator /pass:password /deleteexisting
Answered 02/03/2011 by: dyehardfan
Second Degree Blue Belt

Please log in to comment
0
dyehardfan,


Have you tried calling wsname with the logging command to see the error?
wsname.exe N:newname /LOGFILE:C:\namelog.txt
Answered 02/03/2011 by: dchristian
Red Belt

Please log in to comment
0
no, just rolling with it at the time being since it's working the way I want it to. if/when I start encountering problems I'll follow up on it. too many other irons in the fire at present.

ORIGINAL: dchristian

dyehardfan,


Have you tried calling wsname with the logging command to see the error?
wsname.exe N:newname /LOGFILE:C:\namelog.txt

Answered 02/03/2011 by: dyehardfan
Second Degree Blue Belt

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