Server rename issue?

[John Flanagan_2]

When I rename a W2K server that was in CIM, it tends to have a difficult time registering itself within CIM w\ the new name, it just seems to hold onto the old server name.
DNS entries have been checked along w\ reverse lookup names and they look good, as in old entries are gone.
I've had to go as far as uninstalling CIM agents, reinstalling CIM agents, removing all servers from the database, rebooting the CIM SQL server, then allow it to rediscover all the devices.
When I've tried to just delete the old server name from the DB, CIM doesn't seem to want to automatically discover that IP address since I explicitly deleted it.

Any ideas or other techniques I could try next time?

[David Claypool]

Note: If this question is regarding IM7, it should be posted in the IM7 forum at http://forums1.itrc.hp.com/service/forums/categoryhome.do?categoryId=266

The steps you outline above should not be necessary. The key in the IM7 database is a globally unique ID (GUID) which is the same as the ProLiant's serial number (at least in agents 6.2 and later). Because of that, if the DNS name or IP address change, IM7 can re-identify it in the case of DNS name change (when the Daily Device Identification task is run) or re-discover (in the case of IP address change).

[John Flanagan_2]

Thank you, I will post in IM7 section.
Unfortunately, IM7 does not appear to be working for me as you so eloquently describe it's process.

[Rob Buxton]

Are you using some kind of manual addition here? local hosts file or something?

Generally I find the Server goes critical and I just delete that and the discovery and identification processes pick up the new device.
If a server name change is due, you could try shutting down the Server and then deleting it from the database. When the new Server name was visible, rerun the Discovery and Identification tasks. It should be rediscovered as required.