Changing Domain Names - Possible to retain ticketing systems accumulation of requests, solutions, assets, etc?
Basically we are growing our network and it's finally necessitated that we build a new DC (domain controller). In the process of building the new DC we will be changing the actual name of the network from blahblah.org to corp.blahblah.org. That means that when we go live we will be removing all PC's and servers from the old domain and joining them to the new one. We will also be recreating all the user accounts in Active Directory in the new DC, although a few may not end up the same groups they were before.
Here are our concerns:
- Is there a way to make sure that the users (who will have the same usernames as before, but slightly different domain name) will be able to log into the ticketing system and still see all the tickets they've opened in the past and interact with them?
- Possibly the same problem, but how should I go about importing users from the Active Directory of the new DC, without ending up with duplicates of everyone all over the place?
- What should we do with regard to assets and their association with users. We'll have all the same hardware, but it will be on a new domain. Would it be easier to just try a fresh scan, and manually fix all the assignments again?...
I think you get the idea. Has ManageEngine thought of, or prepared a method, to migrate an installation of ServiceDesk Plus from one domain to another while retaining the users, requests, assets, and general accumulation of useful data?
If not, has anyone found a way to deal with it, assuming they too were facing a situation where the DC and domain name where changing?