Video Screencast Help

Imaging Laptops, System Config renaming machine to existing name and knocking off domain

Created: 17 May 2012 | 4 comments
mmathews's picture

Our current environment is SMP 7.1.  We are currently having issues when imaging a laptop using initial deploy.  Our defined computer range is 250-259 currently.  Most of our systems were originally imaged with 6.9 instead of 7.1.  When we image a system it will image and join to the domain but has a tendency to utilize a name which is already in existence and will knock the pre-existing system off of the domain.  Has anyone else experienced this or know what needs to be done to address the issue.  We need to get this solved as soon as possible.  This only happens to our laptop images.

 

 

Comments 4 CommentsJump to latest comment

mclemson's picture

There is no check performed to see if a name already exists.  You should provide a unique range if part of the current range has already been used by a previous imaging process.

I recommend that naming conventions like desktop=DT0016 and laptop=LT00159, or LT-CHI-IL-US-00159 and DT-CIN-OH-US-00160 are not used.  Altiris has much better methods of determining what a computer is than a computer name.

Why not key on something unique like serial number?

Additionally, there is an issue with the v3 roll-up when applied to the v2 roll-up, which is fixed in the v4 roll-up. So you may want to apply hotfix v4.

Mike Clemson, Senior Systems Engineer, ASC
Intuitive Technology Group -- Symantec Platinum Partner
intuitivetech.com

mmathews's picture

Our naming convention is standard for our company: 

 

Desktops are PC(then department initials)#

Laptops are LT(then department intials)#

The numbers are in chronological order unless one has been replaced and in that case it may skip a number or too.  But there are not any numbers in the ranges or above the ranges specified in the initial deployment settings. 

 

Could DNS be an issue?

mclemson's picture

Your standard is LT(dept initials)#, e.g. LTIT240, but no laptop exists with a number in the range 250 to 259, which is what you currently have the task set to.  But systems in different number ranges (for example, LTHR188) drop off the domain when you image a new laptop whichi  snamed LTPR255?

Am I understanding the issue correctly?

Mike Clemson, Senior Systems Engineer, ASC
Intuitive Technology Group -- Symantec Platinum Partner
intuitivetech.com

mmathews's picture

Yes, that is correct.  I've been asked to address the issue immediately as it's effecting any new systems imaged.  I'm assuming it's related to the fact that the machines it's knocking off were imaged in DS 6.9 SP5  and since the new machines are being imaged with DS 7.1 SP 1 Rollup V4, that it would have to do something with the fact they haven't been issued in the 7.1 PXE/initial deployment tables.  I am trying to identify which tables this information would be identified in to verify my hypothesis.