Active Directory Domain Rename
We wat to rename the domain from customerlocal.nl to customer.local including the NETBIOS name. I found some usefull documents from Microsoft regarding the rename.
What we want to know is what to do with the following devices / software
- VMware Virtual Center
- NetApp Storage
- Exact Software
Do we need to do anythin special for them or do we need some configuration changes?
What we want to know is what to do with the following devices / software
- VMware Virtual Center
- NetApp Storage
- Exact Software
Do we need to do anythin special for them or do we need some configuration changes?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
It's clear that I can get some DNS issues if an application uses FQDN. The hostname of the systems won't change.
Als they have some Linux and MAC computers. Those can be removed and added to the domain again.
They use a single domain and it's not a big company. They use central NetApp Storage. What I found on the net was that the NetApp stores the SIDs of the accounts. Thos will remain the same after a domein rename, so I should be able to rerun the CIFS wizard to reconnect it to the new domain.
Then Only the Exact (SQL Application) and VMware Virtual Center (Uses SQL Express and I think a Ldap connection to the domain) remains.
Als they have some Linux and MAC computers. Those can be removed and added to the domain again.
They use a single domain and it's not a big company. They use central NetApp Storage. What I found on the net was that the NetApp stores the SIDs of the accounts. Thos will remain the same after a domein rename, so I should be able to rerun the CIFS wizard to reconnect it to the new domain.
Then Only the Exact (SQL Application) and VMware Virtual Center (Uses SQL Express and I think a Ldap connection to the domain) remains.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
All applications that use DNS to resolve a name to a specific machine will be affected with this change. Normally all applications that give support to multiple domains will need to store FQDN to make sure that uniquely identify the machine. Applications are free to choose the way to store that info so only its developers can tell.
My suggestion is to have a DNS server responding to the old domain name with CNAME records that points to Host A record in the new domain name DNS server, this way you will have time to change settings in those applications to let them know the new name.