elcuco
asked on
Creating a backup domain controller in w2k
I've been assigned a project in where I have to install and create a win2k server with Exchange 2000 server and migrate our exchange 5.5 users and folders.
I wondering how to go about doing this, the current exchange server(5.5) is currently running on a windows NT server and is also our primary domain controller.
I have installed w2k on a new server and i'm in the midsts of installing AD but the problem that I'm running onto is that whenever i choose "additional domain controller for an existing domain" i get a message saying.. 'the domain "abc.com" is not an active directory domain, or an ac domain controller for the domain could not be contacted.
Right now i'm doing this on a test environment where I have a win NT4 server running exchange 5.5 that is also a primary dc.
All I really want to to do is make the w2k a backup dc and migrate all the users/folders from exchange5.5 on winNT and once all has migrated I want to make w2k a primary dc.
Any ideas??
I wondering how to go about doing this, the current exchange server(5.5) is currently running on a windows NT server and is also our primary domain controller.
I have installed w2k on a new server and i'm in the midsts of installing AD but the problem that I'm running onto is that whenever i choose "additional domain controller for an existing domain" i get a message saying.. 'the domain "abc.com" is not an active directory domain, or an ac domain controller for the domain could not be contacted.
Right now i'm doing this on a test environment where I have a win NT4 server running exchange 5.5 that is also a primary dc.
All I really want to to do is make the w2k a backup dc and migrate all the users/folders from exchange5.5 on winNT and once all has migrated I want to make w2k a primary dc.
Any ideas??
You need to use the Active Directory Connector to attach the two. Here: http://www.microsoft.com/technet/treeview/default.asp?url=/technet/itsolutions/guide/deploy/d_02_tt1.asp
The problem is that NT does not support Active Directory, therefore as long as you run an NT server and a 2000 server in the same domain you will not be able to promote the 2000 server to a domain controller. 2000 can only be promoted to a domain controller if it is the only server in your network or if all other servers are running 2000 as well.
jehob.. what is mixed mode for? It's not for supporting legacy clients, it's for replicating to NT 4 DCs.
Here is a Microsoft article which outlines exactly what you are trying to accomplish:
http://www.microsoft.com/technet/treeview/default.asp?url=/technet/prodtechnol/exchange/exchange2000/deploy/upgrdmigrate/6STEPAP.ASP
By the way MSGeek, I didn't mean to sound like I was disagreeing with your answer....you are aparrently just a faster typist than me so I didn't realize anyone had answered yet!
http://www.microsoft.com/technet/treeview/default.asp?url=/technet/prodtechnol/exchange/exchange2000/deploy/upgrdmigrate/6STEPAP.ASP
By the way MSGeek, I didn't mean to sound like I was disagreeing with your answer....you are aparrently just a faster typist than me so I didn't realize anyone had answered yet!
ASKER
Jehob thx for your replies, can in promote the w2k server as a backup dc and migrate all necessary files and then change the w2k server to a Primary DC?
Thanks for the replies thus far you guys rock.
Thanks for the replies thus far you guys rock.
The answer is yes, but read my link first!
ASKER
Jehob thx for your replies, can in promote the w2k server as a backup dc and migrate all necessary files and then change the w2k server to a Primary DC?
Thanks for the replies thus far you guys rock.
Thanks for the replies thus far you guys rock.
ASKER
Jehob thx for your replies, can in promote the w2k server as a backup dc and migrate all necessary files and then change the w2k server to a Primary DC?
Thanks for the replies thus far you guys rock.
Thanks for the replies thus far you guys rock.
ASKER
Jehob thx for your replies, can in promote the w2k server as a backup dc and migrate all necessary files and then change the w2k server to a Primary DC?
Thanks for the replies thus far you guys rock.
Thanks for the replies thus far you guys rock.
ASKER
sorry about the damm duplicate posts.. I guess whenever you refresh the page it re-submits my last questions.
Yes it does--use the "refresh this question" link at the top left.
As for what you're trying to do, we're in the final stages of doing the very same thing. Basically Exchange 2000 really needs to exist on a native mode Active Directory domain--it doesn't like mixed mode at all--so you first need to get your domain updated to Active Directory. (You can do this by upgrading your NT PDC to Windows 2000, then replacing all the other NT BDCs with 2K boxes and converting). You will also need the Exchange 5.5 Active Directory Connector installed on a domain controller before you switch the domain to native mode.
As for what you're trying to do, we're in the final stages of doing the very same thing. Basically Exchange 2000 really needs to exist on a native mode Active Directory domain--it doesn't like mixed mode at all--so you first need to get your domain updated to Active Directory. (You can do this by upgrading your NT PDC to Windows 2000, then replacing all the other NT BDCs with 2K boxes and converting). You will also need the Exchange 5.5 Active Directory Connector installed on a domain controller before you switch the domain to native mode.
Elcuco:
If you have a BDC
1) Promote your BDC to PDC (which automatically demotes the PDC)
2) Upgrade your PDC to Windows 2000
3) Install the AD connector on your BDC/Exchange 5.5 server
4) Build a Windows 2000 Server and join it to the domain as a member server
5) Install Exchange 2000 onto the Windows 2000 member server
6) Move users mailboxes and public folders onto the Exchange 2000 server
7) After a period of succesful running, remove Exchange 5.5
9 Switch Exchange 2000 to native mode
10) Upgrade your old PDC now BDC to Windows 2000
11) Switch AD to native mode
If you don't:
1) Build a BDC
2) Promote it to a PDC (which automatically demotes the PDC)
3) Repeat steps 2-11 from above
Just make sure you do periodic backups through the migration process and have a backup plan!
If you have a BDC
1) Promote your BDC to PDC (which automatically demotes the PDC)
2) Upgrade your PDC to Windows 2000
3) Install the AD connector on your BDC/Exchange 5.5 server
4) Build a Windows 2000 Server and join it to the domain as a member server
5) Install Exchange 2000 onto the Windows 2000 member server
6) Move users mailboxes and public folders onto the Exchange 2000 server
7) After a period of succesful running, remove Exchange 5.5
9 Switch Exchange 2000 to native mode
10) Upgrade your old PDC now BDC to Windows 2000
11) Switch AD to native mode
If you don't:
1) Build a BDC
2) Promote it to a PDC (which automatically demotes the PDC)
3) Repeat steps 2-11 from above
Just make sure you do periodic backups through the migration process and have a backup plan!
Simon, that's a great answer. It tells you how to do it, but he really needs to understand how the connector works, that is where most foul ups occur.
ASKER
Question... what needs to be done regarding the hostname on the w2k server? I want to use the same hn as the nt server so that all users do not have configure anything on their side. So lets say my NT server's name is websrv and I name the Bdc websrv1 will I able able to change the Bdc to a Pdc with the original nt hostname which is websrv?
What would users have to configure if you had a different hostname? Things are a lot different in AD domain.
ASKER
for now.. i'm just doing this on a test environment, I'm currently trying to upgrade the WinNT server to W2k server but I get an error saying "Windows 2000 setup does not support upgrading from MS Windows NT server, Enterprise Edition to MS windows 2000 server, what gives?
Is this a Backoffice Server?
ASKER
Yes it is.
You didn't tell us that. I am fairly sure you will need to clean install 2000 on an different box, then install Backoffice Server on it, the upgrade Exchnage.
ASKER
well its WinNT 4.0 but it has a bkoffice server stamp, our main Pdc/exchange5.5 is running on WinNT 4.0 enterprise.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Ypu'll need this as well: http://www.microsoft.com/backofficeserver/downloads/updates/win2000qfe.asp
ASKER
thank god for MSGeek, I will read all your docs and will let you know how this project is going. Thx
That's a little over kill, just hope iit gets you on your way. You have your work cut out for you, not as easy as Simon would have one think.
No comment has been added lately, so it's time to clean up this TA.
I will leave a recommendation in the Cleanup topic area that this question is to:
Accept MSGeek's Comments as answer
Please leave any comments here within the next seven days.
PLEASE DO NOT ACCEPT THIS COMMENT AS AN ANSWER!
Paul
EE Cleanup Volunteer
I will leave a recommendation in the Cleanup topic area that this question is to:
Accept MSGeek's Comments as answer
Please leave any comments here within the next seven days.
PLEASE DO NOT ACCEPT THIS COMMENT AS AN ANSWER!
Paul
EE Cleanup Volunteer
Thanks, glad I could help. MSGeek