DYNAMIC NAME SCHEME USING SYSPREP

[marwood_tech]

Basically my question is how to accomplish dynamic name scheming using the sysprep.inf file.

I have created a base image using Symantec Ghost, uploaded the image without issue; reboot and runs thru the mini-setup fine until it reaches the "computername" section and halts there as the wildcard syntax I am using doesn't work. However, the same syntax worked with our old imaging system using a RIS server and WIM file. I don't believe the image file type should make a difference, once it reaches the mini-setup point in Windows, its all the same sysprep file.

the syntax i am using for the computer name is as follows:

[userData]

ProductKey=XXXXXXXXXXXXXXX

FullName="XXXXXXX"

OrgName="XXXXXXX"

ComputerName="TEST-%03#"

I even extracted the same sysprep file that worked in the old image and it would not work, this is very perplexing, hopefully someone has an answer that does not involve VB scripts and runonce options. I would appreciate any logical answers, thanks.

[cluberti]

No, but the RIS part is the key. It was the RIS server that was handling the variables, NOT the XP setup engine. By the time XP's setup got it, it had already been changed in the temp SIF file RIS places down. XP's setup doesn't handle variables, but RIS does.

[marwood_tech]

ok, that makes sense....so is there a workaround for that? would Symantec Ghost or any Symantec product have a way of performing these variables automatically in an unattended bare metal install?

The goal is to have a fully automated imaging process, I have worked with Ghost before but not on a global level, just individual system imaging and it has worked fine. Introducing the whole network image process and this presents somewhat of an issue, but i was under the impression that symantec ghost addressed this very functionality. Other than the name scheming, the imaging works perfectly well, it joins the domain, and adds the system to the custom OU i created, however, the name scheming process halts the mini-setup.

[cluberti]

ok, that makes sense....so is there a workaround for that? would Symantec Ghost or any Symantec product have a way of performing these variables automatically in an unattended bare metal install?

The goal is to have a fully automated imaging process, I have worked with Ghost before but not on a global level, just individual system imaging and it has worked fine. Introducing the whole network image process and this presents somewhat of an issue, but i was under the impression that symantec ghost addressed this very functionality. Other than the name scheming, the imaging works perfectly well, it joins the domain, and adds the system to the custom OU i created, however, the name scheming process halts the mini-setup.

I'm not familiar with Ghost anymore, as I've not used it in about 10 years. However, I'm using SCCM 2007 and WDS and it is fully automated. I'm sure you could find some vbscripts out on the 'net to configure computer names from a database, etc. That might do what you want.

[marwood_tech]

Really? and how does the SCCM 2007 work for you? I see you said you also use WDS; is this dependent of the SCCM or does one rely on the other for complete automation?

We actually used a RIS server for our old imaging system and we are looking to replace that with something mroe automated; we chose ghost as this appeals to that particular function. With the RIS, we still have to fix the MBR and perform a few other small steps in the process as opposed to just uploading the ghost image and being able to install bare-metal fully automated w/ the option to dynamically name the machine according to our naming scheme.

If SCCM 2007 or WDS can accomplish this, then I would look in that direction.

[cluberti]

SCCM is huge, it does all of our software management, windows update management, and OS deployment, and it has WDS and WSUS "underneath". Take a look here for starters - it's a LOT to wrap your head around if you've never used SMS.