@wayne-workman Awesome, thank you for that tool. We have had some troubles in the past when trying to make changes to the system and are currently running our yearly imaging process, when we get done with that process probably end of next week we will definitely be running that.
Side question to the tool. Is this something that can be ran a couple times over years or should it only be used once?

Checking to see if I might have something setup wrong however, our system is not rolling old image numbers back in to the list of options. When we go to delete an image from the server the next time we image it takes the next highest number instead of taking the older lower number. Ex: last image was 60, deleted image number 2, uploaded new image and image number is 61 instead of 2.

Ok we will give that a go. Thank you for the help.

When you say to try the new SVN are you referring to updating fog from 1.2.0 to 3738 or is there an updated fogservice?

If I rename a computer using the Change Name/Domain Changes option in System Properties the machine entry in AD is simply renamed to the new name using the same SID, it does not create a new entry and SID. A machine named Temporary that is renamed to Temporary1 using the Change Name option, changes the name in AD to Temporary1. Changing a machine name using the hostnameregister creates a new entry and SID for that machine, which then leaves me with a broken entry of Temporary, and a new working entry of Temporary1.

I believe Legacy running FOG 1.2.0, we have the new coding for the hostnamechanger.dll though.

In our environment whenever we try to change a name through the fog server, it creates a second entry for that particular machine in active directory. As in I image a machine with name Alpha, then later change it to Bravo, instead of it updating the active directory entry for Alpha to Bravo, We end up with a new entry for Bravo, but Alphas entry remains. Is there anyway to get it to skip the un-join and just change the name? We have tried to bypass the un-join in the hostnamechanger which only netted us computer with a changed name but a broken trust relationship. Any help would be appreciated.