• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 181
  • Last Modified:

Domain Rename Unsuccessful

We have a single label AD domain with one Exchange 2003 server.  We want to get to Exchange 2010.  We went through the process of the domain rename operation yesterday using the 2003 rendom tools on a 2003 control station and it does not appear to have worked.

2003 functional level
2 - 2003 domain controllers
2 - 2012 R2 domain controllers
1 - 2003 Exchange server
All clients are WinXP or Win7
Domain name is abcde and we want to get to abcde.local
The NetBIOS name can remain the same.

LDAP lookups still work with old domain naming convention but not with the new one.
We are considering restoring the system state on all domain controllers to before we started.
Any help or a step by step would be greatly appreciated.  There has got to be an easier way.
0
JadedFan
Asked:
JadedFan
1 Solution
 
JohnBusiness Consultant (Owner)Commented:
We are considering restoring the system state on all domain controllers to before we started.

I suggest you do this and see if you can get back to your original domain name. It is a very complicated undertaking - one that I would not do. Can you live with your existing name?

I have looked at the following Microsoft Article before and backed away.

https://technet.microsoft.com/en-us/windowsserver/bb405948.aspx
0
 
JadedFanAuthor Commented:
We have to do this to get to Exchange 2010.

Am I wrong?
0
 
JadedFanAuthor Commented:
Here are the current results from rendom /list

<?xml version="1.0" ?>
- <Forest>
- <Domain>
- <!--  PartitionType:Application
  -->
  <Guid>02be16a8-b594-401c-a5b6-d6fcca2c59a4</Guid>
  <DNSname>ForestDnsZones.********.local</DNSname>
  <NetBiosName />
  <DcName />
  </Domain>
- <Domain>
- <!--  PartitionType:Application
  -->
  <Guid>e51c27c5-603f-4567-8b75-bfd6ffea06e0</Guid>
  <DNSname>DomainDnsZones.********.local</DNSname>
  <NetBiosName />
  <DcName />
  </Domain>
- <Domain>
- <!--  PartitionType:Application
  -->
  <Guid>969f2f93-e2ad-49ac-92f9-c5c861fd5e84</Guid>
  <DNSname>DomainDnsZones.********</DNSname>
  <NetBiosName />
  <DcName />
  </Domain>
- <Domain>
- <!--  PartitionType:Application
  -->
  <Guid>18d643b3-c41c-4a6c-82e8-8314c4640638</Guid>
  <DNSname>ForestDnsZones.********</DNSname>
  <NetBiosName />
  <DcName />
  </Domain>
- <Domain>
- <!--  ForestRoot
  -->
  <Guid>36b93f66-4141-4199-998e-9c65e6653ab6</Guid>
  <DNSname>recordtrak</DNSname>
  <NetBiosName>********</NetBiosName>
  <DcName />
  </Domain>
  </Forest>
0
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

 
JohnBusiness Consultant (Owner)Commented:
I have not needed to change domain names to get to the next level up of server. By now, however, all my clients are using hosted Exchange, so I have not had to move Exchange. Even for Exchange, I was under the impression there was not need to change.

I cannot tell explicitly from log, but it appears you might be trying to remove "local" from the systems. Is this what you wished to do?
0
 
JadedFanAuthor Commented:
No.  Trying to ADD local.  Cannot install Ex2010.  SLD not supported.
0
 
JohnBusiness Consultant (Owner)Commented:
Thanks for clearing up the log. Yes, you need .local in the domain name as far as I know. In one conversion I participated in, the domain name (company.local) did not change in the conversion from server 2003 to server 2012.

I have clicked on Request Attention to get some additional support.
0
 
Will SzymkowskiSenior Solution ArchitectCommented:
Is your AD replicaiton working? Check that first...
repadmin /replsum
repadmin /showprepl
repadmin /bridgeheads
DCDiag /v

Also changing an Active Directory FQDN is not supported with Exchange. What you will most likely have to do is the following...
- from the FSMO role Domain Controller perform an Authoritative Restore
- This will replicate to all DC's in your environment with the settings prior to the name change
*you do not have to do a system state restore to every DC, and you SHOULDN'T because you will have USN Roll back issues if you do this.
- Create a new AD Forest (with forest trust to current domain)
- Install Exchange 2010 in the new forest and migrate the mailboxes
- migrate all AD objects to the new forest (along with the mailboxes)
- make sure that your internal FQDN for the new domain is domain.com or local (preferably .com, but not a requirement)
- Install Exchange 2010 in the new Forest and migrate the mailboxes to it

These are the high level steps that need to be performed.

Will.
0
 
JadedFanAuthor Commented:
Thanks, Will.  I think of a resource domain and the word ugh comes to mind but I am keeping that as an option.
0
 
MaheshArchitectCommented:
With Exchange 2003 domain rename is supported

Have you followed exact process as mentioned in
https://technet.microsoft.com/en-us/library/cc738208(v=ws.10).aspx 

Step by step walk through
http://terrytlslau.tls1.cc/2011/04/domain-rename-with-exchange-server-2003.html
https://technet.microsoft.com/en-us/magazine/2005.05.domainrename.aspx

Also keep in mind, random is available as resource toolkit, however you need to separately download it.
https://technet.microsoft.com/en-us/windowsserver/bb405948.aspx

If you have any misconfigurations, probably you need to hire some directory consultant to fix that because this is tricky process.

By the way now at which state you have stuck if you could please explain?
0
 
JadedFanAuthor Commented:
We ended up pushing forward and manually removing the old DCs that were the issue.  After that we were able to successfully rename the domain.  Thanks!
0
 
JadedFanAuthor Commented:
We ended up fixing it ourselves by researching other sites.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Free Tool: ZipGrep

ZipGrep is a utility that can list and search zip (.war, .ear, .jar, etc) archives for text patterns, without the need to extract the archive's contents.

One of a set of tools we're offering as a way to say thank you for being a part of the community.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now