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

How to import/export Active Directory?

I am currently installing Windows Server 2003 R2 Standard Edition on a new machine.  I need to export my entire Active Directory from the old machine that is running Windows Server 2003 Standard, and import it into the New Machine running Server 2003 R2 Standard.  How can I do this without recreating every user and setting?
0
JFrusci
Asked:
JFrusci
  • 3
  • 3
1 Solution
 
SLafferty1983Commented:
If you make the new server a domain controller Active Directory will replicate everything to the new server.
0
 
JFrusciAuthor Commented:
If I make it a domain controller, wont I have to give it the name of my domain?  By giving it the same domain name that already exists, wont there be a conflict when both servers are on the network?
0
 
SLafferty1983Commented:
Ok. I see, so you are changing domains?
0
Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

 
JFrusciAuthor Commented:
Well we want to keep the same domain name as well as giving the new server the same name as the old one
0
 
Brian PiercePhotographerCommented:
Don't give the server the same name a the old one - its unessessary and just complicates matters. Proceed as follows instead:

Install Windows 2003R2 on the new machine WITH A DIFFERENT NAME

Assign the new computer an IP address and subnet mask on the existing network

Make sure that the preferred DNS server on new machine points to the existing DNS Server on the Domain (normally the existing domain controller)

Join the new machine to the existing domain as a member server

As the new Windows 2003 server is the R2 version and the existing set-up is not then you need to run Adprep  from CD2 of the R2 disks on the existing Domain controller. Take CD2 from the R2 disks place in in the existing DC and run Adprep form the \CMPNENTS\R2\ folder on CD2
You need to run AdPrep /forestprep and then AdPrep /domainprep.

From the command line promote the new machine to a domain controller with the DCPROMO command from the command line Select Additional Domain Controller in an existing Domain

Once Active Directory is installed then to make the new machine a global catalog server, go to Administrative Tools, Active Directory Sites and Services, Expand ,Sites, Default first site and Servers. Right click on the new server and select properties and tick the Global Catalog checkbox. (Global catalog is essential for logon as it needs to be queried to establish Universal Group Membership)

Assuming that you were using Active Directory Integrated DNS on the first Domain Controller, Inststall DNS on the new Domain controller and DNS will replicated to the new domain controller along with Active Directory.

If you are using DHCP you should spread this across the domain controllers, In a simple single domain this is easiest done by Setting up DHCP on the second Domain controller and using a scope on the same network that does not overlap with the existing scope on the other Domain Controller. Dont forget to set the default gateway (router) and DNS Servers. Talking of which all the clients (and the domain controllers themselves) need to have their Preferred DNS server set to one domain controller, and the Alternate DNS to the other, that way if one of the DNS Servers fails, the clients will automatically use the other.

Both Domain Controllers by this point will have Active Directory, Global Catalog, DNS and DHCP. and the domain could function for a while at least should any one of them fail. It is normally recommended that you have at least 2 DCs to provide resiliance.

If you really want to remove the old DC then first transfer all the FSMO roles: See http://www.petri.co.il/transferring_fsmo_roles.htm

Made the other DC a global catalog (if you have not already done so). Go to Administrative Tools, Active Directory Sites and Services, Expand ,Sites, Default first site and Servers. Right click on the new server and select properties and tick the Global Catalog checkbox. (Global catalog is essential for logon as it needs to be queried to establish Universal Group Membership)

If the Old DC is running DHCP:
Install DHCP on the new DC, set up the scope and authorise it. remove DHCP from the old DC.

DNS: Make sure that all of your clients are set to use the new DC as their Preferred DNS server (either by static entries or DHCP options)

Power down to old DC and make sure that all is well, once satisfied power on the old DC again, then run DCPROMO for remove it's domain controller status. If you want to remove the machine from the domain then you can do so one it's DC role has been removed

NOW and ONLY NOW should you rename the new DC if you cannot bear to live with the new name: see http://www.petri.co.il/windows_2003_domain_controller_rename.htm

0
 
SLafferty1983Commented:
That is a very detailed layout of exactly what you need to do. Thanks KCTS.
0
 
JFrusciAuthor Commented:
Thank You...this is much appreciated
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

Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

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