Video Screencast Help

Different GUID each time machine is imaged....

Created: 24 May 2013 | 4 comments
chiefshb's picture

Ok's one that I can't figure out. Let me give the rundown...

I'm using DS 7.1 SP2 and have created a HII image and am testing it on different models. Each model I test it on, the job completes successfully...EXCEPT on HP Compaq dc7900's!! I have tried 2 different ones so far and the exact same thing happens.

I'm attaching a pic of the job for reference, but I don't think there's anything wrong with the job itself. The fact that I have tested it on 4 different models (5 including the dc7900's) and it works (with the already mentioned exception leads me to believe maybe there is something up with this model?

 When I send the image job to the machine...again, any boots to automation. It then successfully deploys teh image via RDeploy. The script maps a drive to the server for driver transfer and then the next script sopies the correct drivers based on a WMI lookup (or whatever you want to call it). Then the machine reboots into production. This is where the 7900's veer off course. The rest of the job never continues. When I look into it, I find there are now 2 computers found with this name and serial number and 2 different GUIDs. The original that began the image is waiting for the next task to be received and the new one has no jobs waiting, so the image job never finishes.

Has anyone ever seen this and if so, any ideas how to resolve it? It's strange that it only happens on one model...the problem with this being the model is we have about 1200 of them still. 

Thanks in advance and let me know if any other info is needed.

Operating Systems:

Comments 4 CommentsJump to latest comment

Thomas Baird's picture

We've seen something like this before and we're not 100% sure yet why.  Essentially, the resource keys you sent up in automation aren't matching what is being found in production.  Are these re-imaged systems?  If so (that is, not NEW) are you assigning them a generic name, or lettins us rename it via the job back to the original name?  If it's getting a random name to be renamed via a config task later, what I THINK is happening is that we're not recognizing it.

What we want to do here is try to find a way to capture the resource keys submitted during the "createresource.aspx" call when it boots to production.  It's hidden currently, so we can't tell if those match what we send up in automation or not.  :It is helpful to know it's only one model though.  Maybe some computers are changing their MAC in Windows or something funky.

Thomas Baird
Enthusiast for making things better!

chiefshb's picture

Hi Thomas...thanks for the reply. These are re-imaged computers (not new) that I am letting DS name whatever they are currently named.

Could you explain more about the resource keys and how to capture them?

Thanks, again.

chiefshb's picture

In addition...while testing more models, the HP 8560w is now doing the same thing.

JeffCarlson's picture

We are having the same type of issue.  Thomas is already helping us with it.  But you are not alone.  We are also using HP equipment and have tried it on several different models but mostly 8300's.