How to Clean Up Active Directory after an Unsuccessful Migration

Article ID: 2647882 - View products that this article applies to.
Expand all | Collapse all

SUMMARY

This article contains steps to clean up the Active Directory when a Small Business Server 2011 Standard migration installation fails. If the setup of SBS 2011 Standard fails and the installation must be performed again, it is advisable to perform a system state restore on the source server and then retry the migration install. Sometimes it is not possible to perform a system state restore. This article contains the steps to clean up active directory so that a second attempt at installation will be successful.

MORE INFORMATION

The following steps can be used to clean up the active directory and redo the migration installation of SBS 2011.




The steps involve directly editting values in Active Directory. We strongly suggest you make a complete backup of the source server before you attempt these steps.


Cleanup Active Directory Entries for the New Domain Controller

These steps will clean up the Active Directory entries that make the new SBS 2011 server a domain controller. If you use following these steps, the SBS 2011 must be completely reinstalled.

Seize FSMO Roles and perform metadata cleanup

1. Power off the new SBS 2011 server.

2. On the source server, run NTDSUTIL

3. At the NTDSUTIL prompt, type roles

4. At the FSMO maintenance prompt, type connect

5. At the server connections prompt, type connect to server <source server name>, example connect to server contososerver

6. Type q to close out of server connections

7. At the FSMO maintenance prompt, type Seize Domain Naming Master, click yes to the warning prompt

8. At the FSMO maintenance, prompt, type seize infrastructure master, click yes to the warning prompt

9. At the FSMO maintenance, prompt, type seize pdc, click yes to the warning prompt

10. At the FSMO maintenance, prompt, type seize rid master, click yes to the warning prompt

11. At the FSMO maintenance, prompt, type seize schema master, click yes to the warning prompt

12. Type q to close out of FSMO maintenance

13. Type Metadata Cleanup

14. At the Metadata Cleanup prompt, type select operation target

15. At the select operation target prompt, type list domains

16. At the select operation target prompt, select domain <domain number>

17. At the select operation target prompt, type list sites

18. At the select operation target prompt, select site <site number>

19. At the select operation target prompt, type list servers in site

20. At the select operation target prompt, type select server <server number for the SBS 2011 server>

21. At the select operation target prompt, type q

22. At the metadata cleanup prompt, type remove selected server, you will see a warning dialog box, make sure that the server name in the warning is the name of the new SBS 2011 server that failed the setup. If the name matches, click yes to remove the server.

23. Type q twice to close out of NTDSUTIL

24. Open Active Directory Users and Computers, click view advanced features

25. Expand the Domain Controllers OU

26. If the server object for the new SBS 2011 server is not present skip to Step 29, otherwise Right click on the Server object corresponding to the new SBS 2011 server and go to properties

27. Click on the Security tab, make sure that the Administrators group has Full Control and click OK

28. Right click on the server object corresponding to the new SBS 2011 server and choose delete. Choose the option for This domain controller is permanently offline and can no longer be demoted using the Active Directory Installation Wizard (DCPROMO). Choose Yes to the warning about the object being a container.

29. Open Active Directory Sites and Services

30. Expand Sites

31. Expand Default-First-Site-Name

32. Expand Servers

33. Right click on the server object corresponding to the new SBS 2011 server and choose Delete


At this point, the new server is no longer listed in Active Directory as a Domain Controller. You must also use the following steps to clean up the entries for the failed Exchange Setup.

Clean Up Exchange Entries

1. Open Active Directory Users and Computers

2. Remove the user named FederatedEmail.GUID (Note: The user is typically located under the Users container or under cn=MyBusiness,cn=users,cn=sbsusers)

3. Remove the user named DiscoverySearchMailbox{GUID} (Note: The user is typically located under the Users container or under cn=MyBusiness,cn=users,cn=sbsusers)


4. Run ADSIEDIT.MSC (Note: ADSIEDIT.MSC is included in the Windows Support Tools. If the source server is Small Business Server 2003, the support tools are available on CDROM #2. Otherwise they can be downloaded from the Internet at: http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=15326


Warning If you use the ADSI Edit snap-in, the LDP utility, or any other LDAP version 3 client, and you incorrectly modify the attributes of Active Directory objects, you can cause serious problems. These problems may require you to reinstall Microsoft Windows 2000 Server, Microsoft Windows Server 2003, Microsoft Exchange 2000 Server, Microsoft Exchange Server 2003, or both Windows and Exchange. Microsoft cannot guarantee that problems that occur if you incorrectly modify Active Directory object attributes can be solved. Modify these attributes at your own risk.

5. Expand Configuration

6. Expand CN=Configuration

7. Expand CN=Services

8. Expand CN=Microsoft Exchange

9. Right click on the object for the Exchange Organization and go to properties (The object is typcially named the same as the Active Directory netbios domain name.)

10. Edit the attribute named ObjectVersion

Set the objectversion to one of the following values depending on what version of Exchange is installed on the source server:

For Exchange Server 2003, the objectVersion value should be 6936.
For Exchange Server 2007, the objectVersion value should be 10628

11. Click OK to close the properties

12. Expand CN=object for the Exchange Organization

13. Expand CN=Administrative Groups

14. Expand CN=Exchange Administrative Group (FYDIBOHF23SPDLT)

15. Expand CN=Servers

16. Delete the server object corresponding to the name of the new SBS 2011 server.

17. Expand CN=Databases

18. Click on each database and check the msExchOwningServer attribute. If the value contains the name of the new SBS 2011 server, then you must remove this database entry.

19. Once all the Exchange entries all removed you can choose to retry the setup. You must boot from the Small Business Server 2011 DVD and format the drive and redo the entire installation.


For additonal information on troubleshooting Small Business Server 2011 Standard installation see the following Blog Post: http://blogs.technet.com/b/sbs/archive/2011/07/01/sbs-2011-standard-migrations-keys-to-success.aspx


Note This is a "FAST PUBLISH" article created directly from within the Microsoft support organization. The information contained herein is provided as-is in response to emerging issues. As a result of the speed in making it available, the materials may include typographical errors and may be revised at any time without notice. See Terms of Use for other considerations.

Properties

Article ID: 2647882 - Last Review: February 24, 2012 - Revision: 4.0
APPLIES TO
  • Windows Small Business Server 2011 Standard
Keywords: 
KB2647882

Give Feedback

 

Kontaktieren Sie uns, um weitere Hilfe zu erhalten

Kontaktieren Sie uns, um weitere Hilfe zu erhalten
Wenden Sie sich an den Answer Desk, um professionelle Hilfe zu erhalten.