Deployment Solution

I'm in the process of migrating from DS 6.9 to 7.1 (SP2).  Working in a school, we get in around 175 computers each summer.  In 6.9 I would simply create a "New Computer" and could knock out a lab in about 5 seconds.  I'd drop the image job onto these computers and whenever my tech in the field got them plugged in, he'd boot and be prompted to associate the machine with a name.  It worked fantastic.

How do I do this in 7.1? 

 - I've seen the Predefined computer area, but that requires a MAC address.  This is cumbersome to say the least.

 - I've read about Initial Deployment, but this seems less than ideal for a few reasons.

I read in the 7.1 SP2 Beta notes this:

Predefined Computer Changes

• Right-click, New Computer in the console
• Import and use all data within pre-defined computer spreadsheet
• Choice of ID for Keys
• Support DS 6.9 “Virtual Computers”

However, as I'm running 7.1 SP2, it seems this did not make the cut.  Maybe I'm just not sure how to do it though.  Any assistance is appreciated.

Thanks! 

By default if you boot a machine that's not known to the console it will give it a random name. Something like minit-XXXXX. To avoid all our new machines being named incorrectly. we use a VB script that prompts at the start of the image job for the computer name. When entering the computer name it replaces the variable in the unattend file that names the computer. Once it boots up it names itself correctly and then checks in with the NS. If you don't enter a computer name it will eventually time out and continue. If that's the case it will name the computer whatever name is given in the console.

I believe SP2 for deployment solution isn't out yet. Or maybe it's Deployment Solution 7.2 that's supposed to come out in a few months. This version may have the ability to right click and add a new computer in the console.  

I just double checked - you are correct about SP2, I was wrong.  We're on CMS 7.1 SP2, but DS 7.1 SP1 MR1.

Your solution sounds fesible but still not ideal.  One reason being the way all our images were built in the past they're all sysprepped and then taken up as a backup image and deployed as such as well.  Not necessarily the correct or modern way, but it worked very well.

Well, maybe SP2 will come out before I have to deploy.  :)

Hidden in some "Idea":

https://www-secure.symantec.com/connect/ideas/imaging-deployment-solution-71

"For those of you waiting for 7.2, it was moved to 7.5 to better synchronize with the rest of the products, and adding more MAC support, among other things.  Yes, it's a delay, but it'll be better for the product.  I promise!

Thomas Baird
Endpoint Management Specialist"

...and there will be weeping and gnashing of teeth.

Though it doesn't imply that the entire feature set of "new computers" will be moved to 7.5.  Optimism, right?

I have an idea that we use here. In 6.9 you can create a new machine and drop the job on it but when the tech PXE boots the machine it will still require a little interaction in order to select the correct machine from the list (assuming you didn't add the MAC address). Since you need a little interaction already you could use a vbscript which will popup in PXE and ask for the computer name, then select the appropriate published job. The script, in the background, will copy your unattend file to X: (or wherever) temporarliy and replace the token inside the unattend with the computername supplied by the vbscript. When the image task is over the unattend file can be copied to the right place on the machine and you're good to go.

The downfall to this method is that you might have to create your own image task rather than use the built-in one. We have to do this for various reasons, mostly related to storage, but it does work and it works quite well so far.

After looking into this further and deciding to attempt to abandon 6.9 in favor of 7.1 I'm once again stuck on this issue.

It looks like I'd have to do what you do for new computers.  I want a known computer to keep its current name and a new computer to prompt.  Is that how you have it set up?  If so, are you willing to elaborate on how you did that?

I have a suggestion -

1) Boot a unknown client to PXE.

2) Create a Job of Deploy Image+ Reboot To Production + Apply System Configuration(For Appropriate Name Change).

3) Add this job to Initial Deployment Menu.

So Image will be deployed,machine will boot to production and approriate name change will also take place with Apply System Configuration.

That might be feasible for just a handful of computers, but you'd have to change the apply system config task for each machine or create a seperate task & job for each.  So for 175, that's not going to cut it.