Cloned PC's not showing up in HPSIM 4.2 SP2

[Joel Hernandez]

Hello,

I have a problem that I hope someone could help me solve. In the all systems tab I have on PC that was created with WINXP Pro with all the application we using in our Org, and we imaged it and created 10 more PC's from the image(they are using Volume License Keys). The problem is that The first PC is the only one that shows up, the others do not. When I click on the Diagnose tab in HPSIM and select ping, it would ping the client and it shows 11 different IP addresses,(the same 11 IP's that each client is using in our network). It is even using an IP that is for a manager PC that was cloned from the image. I can't seem to figure out how to correct this so that all the PC's that were cloned will show up instead of just one.

thanks....Joel

[Mike Strako · Accepted solution]

Have you used Sysprep on your master image? If not, you won't see all clones because they don't have unique GUID's or SID's.

[Joel Hernandez]

Ok Mike,

Now I understand. So If I change the SID's on each machine, I should not have this problem. I guess If I changed each one prior to adding them to our domain, HPSIM would recognize them as individual clients.

I just downloaded SysInternals NEWSID application which will allow me to change the SID. Thanks for the insight

[Joel Hernandez]

Ok....

I managed to change all of the SIDS to their own unique SID. But when I delete the old client and try and get HPSIM to discover them I get only one Client, the others still do not show. If I do it manually, the first will appear and when I add another client the new one will appear with both ip addresses again. Man what gives...

[Mike Strako]

1 more thing that you can look at is the NIC team virtual address, in the hp network configuration utility, highlight team, goto properties, settings then compare MAC address with default, click "use default". When cloning, the MAC keeps the original image's MAC. Bet that's your second problem.

[Joel Hernandez]

Um...Mike,

Where would I find the HP Network Configuration Utility? I don't see it on the HPSIM.

[Mike Strako]

It's on the server(s) themselves. Let me know how it's going.

[Joel Hernandez]

Mike,

I got a little confused. The clients are actually Compaq EVO desktops, they are not servers. The Servers that I do have are working perfectly, they are all showing. The problem is with our desktops, and they do not have the HP Network Configuration Utility.

[Mike Strako]

Opps, your right. I was thinking servers. Anyway, back to your issue, I know of Winternals but have not used it since my NT 4.0 days, Sysprep is a tool from microsoft that you may want to try also, un-install agents on a desktop, reboot, install the desktop management agents back. What I'm trying to do here is give that desktop it's own unique identifier. Also, while do that, delete all entrys in SIM, then re-discover them. When installing agents, also install DMI, and configure SIM to see DMI as well and properly SNMP strings.. Hope this clarifies some.

[Justin Mattey_1]

I think this will help you. I had the same problem when installing SIM 4.2 with 20 servers that weren't syspreped. After I ran sysprep I had the same problem. Doing the following fixed all problems.


This is a symptom of deploying the servers using some sort of imaging technology (Altiris eXpress, Symantec Ghost, or simply breaking a mirrored drive pair.) This results in the agents on those servers all having the same GUID, or Globablly Unique IDentifier. To reset the servers GUID (to ensure uniqueness) perform the following steps. For Windows based systems, stop the Foundation Agent service on the server. Delete the GUID registry key "HKLM\Software\Compaq Insight Agent. " Restart the Foundation Agent service. Once this is done, the agent will generate a unique identifier for that server. Finally, have Compaq Insight Manager 7 rediscover the server and delete the Orphan_X listings.
To prevent this problem from occurring, delete the GUID from the source system prior to taking the image or breaking the mirrored pair.
-----------------------------

[Joel Hernandez]

Hello,

I Think there is some confusion. The problem is with my Compaq Desktop Clients, not with my Servers. Could I still do what you said about the GUID and it would correct the problem?

[Justin Mattey_1]

Yes, will work on and Computer the agents are installed on.
Del the key from the reg, restart the foundation agents and a new key will be generated(New GUID) I spent days working this out before HP told me this was the soloution. If it doesn't work I buy you a create of beer. :-)

[Joel Hernandez]

Justin,

The WinXp Clients do not have Foundation Agents(FA), only the Server. So are you saying that I should stop the FA on the Server, delete the GUID key on the client then restart the FA on the server? Or is all of this suppose to take place on the Client Machines?. Sorry, I know I'm asking a lot of questions.

[Mike Strako]

Joel, I think he's saying on the client, not the CMS box. Do you have DMI or any HP foundation agents installed or running on the client now?

[Joel Hernandez]

Mike,

I only have the agents Compaq Agents that came with the clients. Do I have to download the foundation agents for Clients?

[Mike Strako]

Once you un-install the agents on the client, then I would download the latest and greatest from HP, and install them. Let me know how it works for you.

[Joel Hernandez]

Sorry for the delay in responding. Guys you are great. It worked. Deleted the Agents, removed the Guid from the registry, rebooted the machine and installed the new Agent and Bingo. HPSIM now sees it as a separate machine. Thanks guys I really appreciate this......Joel

[Joel Hernandez]

Mike and Justin's response on deleting the GUID Key from the registry and uninstalling the Management agent, rebooting, and installing the Agent again was the right steps I needed to get my Cloned PC's showing up as individual PC's in HPSIM.