need to add second server to pdc

[jman9322]

I have installed windows 2000 server on both odc and second server. How do I go about seting up the second server on the PDC? I have never done this before so I do need a little help. after I setup the second server I am going to install windows 2003 on both servers and upgrade exchange 2000 to exchange 2003 on the PDC. any advice anything will be apriciated.



Thank you,
Jason

 

[alpha88]

So basically you want to set up 2 windows 2000 servers. Well basically run dcpromo from the start run that will install active directory. You can than run dcpromo on the second server in order to make it a dc also. I run active directory integrated dns but you can run it in different ways. Ok I'm confused why don't you just install windows server 2003 instaed of windows 2000 server. Either way what I listed above will work on both.

 

[Davetoo]

Well, let's start with the basics. Beginning with W2K, there are no longer PDC's and BDC's, there are only DC's and DC's that handle certain FSMO roles.

To make a server a DC, you simply dcpromo it. So where you had one DC before, now you'll have two DC's, and they will automatically replicate AD information.

What doesn't make any sense is why would you install a W2K domain, only to upgrade it to W2K3? Just install W2K3 and be done with it.

Also, I know for E2K MS recommends you not put it on a DC. You might want to check their recommendations for E2K3, it may be the same.

I'm Certifiable, not certified.
It just means my answers are from experience, not a book.

 

[alpha88]

lander215 I don't think ms recommends putting exchange of any kind on a domain controller. We've always kept our dc separate from our exchange 2000 now exchange 2003 servers. Exchange needs access to global catalog servers in order to operate. Also why put it on a dc when you extend the ad scheme anyway so you can control everything you what from the exchange box. Now we have to global catalog servers for exchange redundacy.

 

[jman9322]

Ok then I ask you. This second server is basically only going to be used for files. Should I not setup AD on it? And should I make it it's own domain? We were thinking that since the other server is running windows server 2000 upgrade them at the same time? I guess I could just put the new file server on windows 2003 right away, and then upgrade our other server to 2003. I just wanted to be able to use the same AD to manage permissions on the new file server. So I guess the new file server has to be its own domain with AD installed with windows 2003. then upgrade our other server to 2003 and exchange 2003. Sorry If I sound broken in what im trying to say im just not sure how to get it across. Thank you for all your help.

Thank you,
Jason

 

[Davetoo]

No, bring the W2K3 server into the same domain as the W2K, no need for separate domains, and in fact just complicates matters as you'd have to keep separate credentials for each domain or setup a trust between the two, which is unnecessary.

I'm Certifiable, not certified.
It just means my answers are from experience, not a book.

 

[alpha88]

lander215 is right theres no need for separate domains. Normally you use a separate domain when you want to separate security boundaries. Now as far as running windows 2000 server and windows server 2003. I don't see any problems with having a 2000 server dc and a 2003 dc. If you have a 2000 domain controller and want to add a 2003 domain controller. You will have to run domain prep and forest prep in order to extend the scheme. Now if you have a 2003 domain controller installed first you can easily add a 2000 server domain controller without extending the scheme. Now back to management lets say you want to manage a windows 2003 dc you can just install the 2003 admin pack on your xp workstaion. You can manage both 2000 and 2003 servers with these tools.BTW you should always have 2 dc's and 2 dns servers.