Domain rename issue with XDR-Fixup tool RRS feed

  • Question

  • Hello all,

    I was performing an Active Directory domain rename over the weekend and ran into an issue with the XDR-Fixup tool which is used to update the Exchange attributes in Active Directory after the domain rename. I was unable to get past this issue which meant I had to revert the changes I made and rename the domain back to its original name.

    Here is an outline of the environment:

    Domain Controllers: Windows Server 2003 SP2
    Exchange server: Microsoft Exchange 2003 Standard SP2
    Renaming from a single label DNS name to a two-part DNS name. NETBIOS name remaining the same.

    I have followed the domain rename procedure as per Microsoft Technet documentation and the domain rename using rendom goes through successfully with no issues. The issue I run into is with the XDR-Fixup tool. When running the tool with the following commandline:

    XDR-fixup /s:domainlist-save.xml /e:domainlist.xml /trace:tracefile /changes:changescript.ldf /restore:restorescript.ldf

    I get the following error:

    Operation failed:

    No other details are displayed. The changescript.ldf file does not end up being created. The restorescript.ldf file is created but at 0kb with no content.

    If I look at the tracefile, the following is listed:

    ===== XDR-FIXUP TRACE LOG BEGINS AT 3/28/2011 3:12:19 PM +08 =====
    Using GC: DC1.companyname
    Malformed entry in domainlist file: guid=2b5cc218-e6c0-47cd-b2c9-93568b7b22bb, dns=DomainDnsZones.companyname, netBios=
    Malformed entry in domainlist file: guid=41859596-5131-4fbd-852a-e8edd51c44ab, dns=ForestDnsZones.companyname, netBios=
    9ee4ac53-d720-408f-bbf1-04565637e8d6: dns(local) netBios(COMPANYNAME)
    Malformed entry in domainlist file: guid=2b5cc218-e6c0-47cd-b2c9-93568b7b22bb, dns=DomainDnsZones.companyname.local, netBios=
    Malformed entry in domainlist file: guid=41859596-5131-4fbd-852a-e8edd51c44ab, dns=ForestDnsZones.companyname.local, netBios=
    9ee4ac53-d720-408f-bbf1-04565637e8d6: dns(vicpark.local) netBios(VICPARK)
    DNS mapping: companyname -> companyname.local
    Org container: LDAP://CN=companyname,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=companyname,DC=local
    Specified argument was out of the range of valid values.
    Parameter name: Index was out of range.  Must be non-negative and less than the size of the collection.
       at System.Collections.CollectionBase.System.Collections.IList.get_Item(Int32 index)
       at System.DirectoryServices.PropertyValueCollection.get_Item(Int32 index)
       at Microsoft.Exchange.Tools.ExRenDom.QueryDCsInForest()
       at Microsoft.Exchange.Tools.ExRenDom.Main(String[] args)

    The malformed entry stuff just seems to be because the NETBIOS name is not listed in my domainlist.xml file (auto generated by rendom /list and then modified for new domain). Manually adding the NETBIOS name between the <NetBiosName> tags in the xml file removes the errors but the command still errors out. I assume the malformed entry errors can be ignored and are not part of the issue.

    ===== XDR-FIXUP TRACE LOG BEGINS AT 3/26/2011 11:28:54 AM +08 =====
    Using GC: DC1.companyname
    2b5cc218-e6c0-47cd-b2c9-93568b7b22bb: dns(DomainDnsZones.companyname) netBios(COMPANYNAME)
    41859596-5131-4fbd-852a-e8edd51c44ab: dns(ForestDnsZones.companyname) netBios(COMPANYNAME)
    9ee4ac53-d720-408f-bbf1-04565637e8d6: dns(companyname) netBios(COMPANYNAME)
    2b5cc218-e6c0-47cd-b2c9-93568b7b22bb: dns(DomainDnsZones.companyname.local) netBios(COMPANYNAME)
    41859596-5131-4fbd-852a-e8edd51c44ab: dns(ForestDnsZones.companyname.local) netBios(COMPANYNAME)
    9ee4ac53-d720-408f-bbf1-04565637e8d6: dns(companyname.local) netBios(COMPANYNAME)
    DNS mapping: DomainDnsZones.companyname -> DomainDnsZones.companyname.local
    DNS mapping: ForestDnsZones.companyname -> ForestDnsZones.companyname.local
    DNS mapping: companyname -> companyname.local
    Item has already been added.  Key in dictionary: "COMPANYNAME"  Key being added: "COMPANYNAME"
       at System.Collections.Hashtable.Insert(Object key, Object nvalue, Boolean add)
       at System.Collections.Hashtable.Add(Object key, Object value)
       at Microsoft.Exchange.Tools.ExRenDom.CreateDnsAndNetBiosMaps(String startDomainFile, String endDomainFile)
       at Microsoft.Exchange.Tools.ExRenDom.Main(String[] args)

    The errors seem to be .NET errors that don't make much sense to me but I have tried running the XDR-Fixup tool on multiple computers with .NET 1.1 installed so I'm fairly certain this is not the issue.

    Monday, March 28, 2011 7:37 AM


All replies

  • To rename AD domains, refer to these Microsoft articles:



    For Exchange questions, I think it will be better to post in Exchange Forums.


    This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.Microsoft Student Partner
    Microsoft Certified Professional
    Microsoft Certified Systems Administrator: Security
    Microsoft Certified Systems Engineer: Security
    Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration
    Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration

    Monday, March 28, 2011 8:08 AM
  • Thanks for the tips guys. As you can imagine, I think I've gone through just about every article online in regards to renaming an Active Directory domain so I have read through these many times before and have been unable to find any answers. Much research was done into this project before we commenced the domain rename.

    If I am unable to find a resolution to this issue, we will be forced to remove Exchange to perform the domain rename.

    Monday, March 28, 2011 9:04 AM
  • Hello,

    are all of the machines rebooted twice after the rename operation or once?

    Best regards Meinolf Weber Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.
    Monday, March 28, 2011 9:09 AM
  • I can understand you, but i haven't actually performed domain rename in production,i tried once performing in lab everything got crashed.

    I even don't recommend to my client for domain rename as its not sure shaot method & there is lot of complexity involved even though after domain rename is performed, the best way is to create a new forest/domain & migrate everything either using Quest or ADMT tool, because so much of risk involved & success rate is 20%, so i would recommend go with migrating it which is better & recommended solution.

    Quest & ADMT both are good but quest offer one solution package where as ADMT is free.



    Awinish Vishwakarma| MY Blog

    Disclaimer: This posting is provided AS-IS with no warranties or guarantees and confers no rights

    Monday, March 28, 2011 9:11 AM
  • Meinolf, Microsoft documentation does not state to restart the control station before running the XDR-Fixup tool however as a precaution I have tried rebooting all associated computers/servers several times before commencing XDR-Fixup.

    Awinish, I agree. In this case, the client was going to do it whether we recommended it or not so we thought it better to hold their hand than come in later if the client had made errors.
    Monday, March 28, 2011 2:49 PM
  • No single link posted above helped you. Since, you already searched so many, i guess someone from MS will jump to assist you further.

    I got one more link, take a look.




    Awinish Vishwakarma| MY Blog

    Disclaimer: This posting is provided AS-IS with no warranties or guarantees and confers no rights.

    Monday, March 28, 2011 3:36 PM
  • I haven't done this before, but, I can tell you that what is happening in the second error is the dictionary is being keyed off of the NetBIOS name. You can't have more than one entry in a dictionary with the same key hwich is what happens when you specify the same NetBIOS name for all those DNS NDNCs.

    The first error looks like it may not be getting any DCs back.

    My Book - Active Directory, 4th Edition
    My Blog - www.briandesmond.com
    Monday, March 28, 2011 4:45 PM
  • Thanks for the response Brian. I figured the second error was caused by me defining the NetBIOS name twice (as a test) and am fairly confident the "Malformed entry in domainlist file" warning can be ignored. Afterall, this is the same domainlist.xml file that I used to successfully rename the domain!

    I have made a test environment and cloned the appropriate servers as new virtual machines so I can perform testing. Although the production environment has multiple DCs at different sites, I have honed the test environment down to a single DC, an Exchange server, and a control station. This environment produces an identical error when running XDR-Fixup.

    During testing, I ran Process Monitor filtered on the XDR-Fixup process and the program does seem to establish an LDAP connection with the domain controller. As to what data (if any) goes across that connection, I don't know. I'm not sure if its possible to do more advanced monitoring/tracing of LDAP connections from an Active Directory service perspective to try and see what attributes XDR-Fixup is trying to modify or where the connection is bombing out (if this is in fact the case)? Has anyone had any experience with this?

    With everything now in a separate test lab, I am happy to try things which would not be recommended for production to try and find the answer!



    Monday, March 28, 2011 5:00 PM
  • Hi,


    According to the problem description, I realize that the domain renaming worked fine, but the Exchange renaming failed.


    For the Exchange related issue, it is better to submit a new question to Exchange Forum which is the best resource for you for further assistance as “Mr X” mentioned.


    Exchange Server



    For more information regarding Exchange renaming, please refer to the following Microsoft articles:


    Supplemental steps for using the Exchange Server Domain Rename Fixup tool together with the Windows Server 2003 domain rename tools



    Exchange and Domain Rename Operations



    Be The Master Of Your Domain Rename With Exchange





    Arthur Li

     TechNet Subscriber Support  in forum

    If you have any feedback on our support, please contact tngfb@microsoft.com . 

    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
    Tuesday, March 29, 2011 2:46 AM