I think if the hostid stays the same than you won't need to unlicense the server from the licensing site.
But just to be safe, following your procedure is what you need to do.
We don't have any 'autounlic' yet, though it's been asked for a lot. I think some folks have tried to script it but I haven't seen a good result yet.
Oh ok... I noticed somewhere else on the forum there was a feature request that was entered back in 2005. The ticket number mentioned was 7252 but there was no recent update about it.
How would the hostid stay the same?
On windows the hostid is based on the first hard disk's serial number, on unix it should be based on the 'hostid' command result (I can't find the KB article that shows this)
So it's possible to rebuild the box and end up w/ the same hostid.
Thanks Bill... I will follow the procedure I mentioned above because I know in the past we have had duplicate license entries on the BL license site (not sure how).
Looking into this further, the hostid on the Unix side has been the IP address in hexadecimal (at least on RHEL 3, AIX 5.3).
On Red Hat:
In my case, since only the server name is changing, and NOT the IP address, would licensing the new server name create a duplicate entry on the BL site (if we didn't remove the original one first)? Or would it leave the original one there with the old server name?
So I'm not sure here. In the list of your licenses I do see duplicate entries where one is active, one inactive. Same hostid and servername.
But for other customers I know I've had a job that runs the licensing script across all their servers (licensed or not) and we didn't have any duplicates.
It's possible the way the licensing site handles entries has changed from when I had the 'relicense everything' setup.
So I'd stick w/ your process of unlicense, rebuild, license - I think that's the safest bet, unless you want to run some tests and do a rebuild, license and then see if you've got dupes.