Deployment Solution

We are seeing a very odd issue where computer records in the Deployment Console are changing their name randomly.

Our initial suspicion is database corruption. This may be caused by an hourly SQL job we have running on the server to change the group ID on each computer account to synchronise our Deployment Console with our Active Directory structure. The query has several lines like this in it

osql -E -S SERVER -d dsolution -Q "update computer set group_id = '59' where msnet_domain_ou in ('administration/information services/workstations')"

We have a line like this for each OU in Active Directory that we want to sync with Deployment Solution and these lines are in a batch file which runs every hour using a scheduled task.

When selecting a computer in the Deployment Console and scheduling a job, the computer name will randomly change to a different machine when looking at the job status.

I am using MAC address to identify computers, so they should be unique and the computer name is simply an identifier for human usage when scheduling jobs etc.

Any thoughts on what might be the problem and, if possible, how I might resolve this?

Anytime you edit the database directly you run a chance of corrupting it.

Do you have a backup that you can restore to before you started having this problem?

You might check your Primary Lookup Key setting in the DS console.  I've found the best setting is Serial number (had an issue a long time ago when this was set differently where I either started getting duplicate computers in the console or machines were changing names).

This can be found by clicking Tools --> Options.  Then click on the Global Tab.  It should be near the bottom of the window. 

I've tried serial number here but I've had problems when our tech's replace motherboards and don't change the serial number back to what it should be. Then I wind up with a bunch of computers using the same record. With it set to MAC address when they replace a motherboard I just end up with a new computer and I can delete the old computer with the same name.

Yeah, I figured that it might be running those manual queries against it that caused the issue.

I have now disabled the script.

I did look into synching with AD but at the time the "Add an SQL trigger" method from the Altiris Juice site, but this caused all sorts of odd things to happen in the console - it may be worth trying it again now it has been tweaked and updated with some syntax corrections.

I thought I had set the Unique Identifier to MAC address, but when I checked it was set to UUID. MAC address is probably better for us that serial number as several of our suppliers don't use the serial number field in the BIOS which is where WMI gets it from.

I have got the details from the Symantec KB for migrating records from a corrupt database to a fresh clean one and this is probably going to be the best option.

Will the clients simply start using the new database provided the server name and IP stay the same?

One thing to remember about using MAC addresses is if a unit has multiple NICs or uses VPN, the MAC address can change, facing you with a multitude of machines in DS for one physical client, this also means if you are close to your license limit, it could put you over.

I totally understand that when a tech changes out the system board and doesn't put the correct serial number back in (or none at all).  I don't know why that would use the same record.  It should create a new machine/instance as multiple MAC addresses would.

In our environment, we require the desktop techs (if they are doing the work) to put the correct serial number back in.  If they are not doing the work, we require that they double check (as part of their checklist) that the serial number is correct before the warranty person can leave.

There is no PERFECT solution, however, you can fine tune it to be as near perfect as you want.

Multiple NIC's in one computer only shows one record as long as all the NIC 's are active at the same time. The only problem we have is with laptops that are set to disable the wireless or on-board NIC when they are docked. That creates a new record.
When using serial number as the primary lookup key and multiple computers have no serial number they all show as the same record because it all the same serial number. At least that's what I've seen in the past. I think with DS 6.9 and being able to choose more than one primary lookup key that might not be the case anymore but I haven't tested that yet.

Yes, as long as the IP of the server is the same the clients will populate the new database as soon as they check in.

I have now implemented the SQL Trigger from here

https://www-secure.symantec.com/connect/articles/deployment-server-active-directory-synchronization

I have deleted all the computer records from the Deployment Console and it is currently re-populating with the MAC address as the unique identifier and putting machines into their correct OU in the group structure.

All seems to be going well now and I didn't have to re-create the database, which is a relief.

The computers that were randomly renaming have now stopped doing so and when I allocate a job it is run against the correct machine, which is essentially what we want.

Many thanks for all the hints and tips

Glad you got it working the way you wanted.