General discussion

Locked

Upgd nt4 pdc to w2kad

By cdietz ·
I need to upgrade a nt4 pdc to w2k with AD. My plan is to build a new nt4 box, make it a BDC, promote it to a pdc. Take the old nt4 pdc off of the network, then upgrade the new pdc to a w2k AD/DController. So far does this plan sound correct. Weare running a Linux box as DNS. Are there any pitfalls I should watch for. Or am I opening a can of worms. The PDC is having major hardware problems so it HAS to be done. Would it be best to just leave the new machine as an NT4 PDC considering the Linux DNS?

This conversation is currently closed to new comments.

9 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Comments

Collapse -

Upgd nt4 pdc to w2kad

by Joseph Moore In reply to Upgd nt4 pdc to w2kad

It is possible to get DNS running on a non-Windows machine to service your AD structure. You will just not be able to do everything you could with a fully realized AD rollout (which includes DNS on the Domain Controllers). No Dynamic DHCP entries inDNS. No AD-intergrated DNS stuff.
Personally, I am not that brave to run it like this.
I have a similar situation in that I am rolling out AD on Saturday (wish me luck!), but my company currently has a global DNS solution built on Solaris machines. Now, I have decided to not try and fight with DNS on Solaris and AD.
Instead, I am setting up a new Win2K server (\\NEWDC) as a member server. After that, I will promote my current NT4 PDC (\\PDC) to Win2k, which will auto-run DCPROMO and set upAD AND install DNS. AFter that, I am taking my new Win2K server \\NEWDC and promoting it to be another Domain Controller in my now-existing AD forest (and installing DNS at that time).
After that, I am transferring all FSMO roles from \\PDC to \\NEWDC.
Once that is done, I am demoting \\PDC so I will only have 1 Domain Controller, \\NEWDC

Ok? Good.
Now, once \\NEWDC is the only AD server, I am going to go into its DNS Management MMC Snap-in, and I am going to enable DNS Forwarders for itsDNS server. I am going to point the Forwarders to the primary Solaris DNS servers we already have.
I am doing that because the DNS setup for AD will be DIFFERENT from my company's current DNS domain namespace running on the Solaris boxes.
And thatway, my office clients (who will be part of the AD domain OFFICE.DOMAIN) will be able to resolve DOMAIN.COM (which is hosted by the Solaris DNS servers) by the DNS on \\NEWDC. Sure, \\NEWDC is just gonna forward name resolution requests for DOMAIN.COM to the Solaris DNS machines, but to the clients it will be transparent.

Hope this all makes sense. It took a couple of weeks planning to get this to work.

Collapse -

Upgd nt4 pdc to w2kad

by Joseph Moore In reply to Upgd nt4 pdc to w2kad

Ok, if you are just not comfortable rolling out AD with its DNS requirements, then yeah, set up a new NT4 box. Make it a BDC in your existing NT domain. Let it synchronize up with your PDC.
Then promote this new BDC to be the PDC.
You can then take the old PDC offline and scrap it.
Doing it this way will keep all of your Windows accounts, and the new machine is the PDC. This is, admitedly, a lot easier than the AD rollout.
Yes, Win2K with AD is better than NT4 flat domain, but if you don't have a need to go to AD, then don't. And if you really don't want to interface with DNS on Linux at all, then go the NT4 route.

Good luck!

Collapse -

Upgd nt4 pdc to w2kad

by cdietz In reply to Upgd nt4 pdc to w2kad

Poster rated this answer

Collapse -

Upgd nt4 pdc to w2kad

by Trackhappy In reply to Upgd nt4 pdc to w2kad

Sounds spot-on. Check out the DNS requirements for 2000 AD though. Microsoft recommends their 2000 DNS server naturally, but yours may be ok if it supports dynamic updates and SRV resource records.
As far as whether to, or not. 2000 is much better for lots of reasons, more efficient, more stable, and nicer to manage. AD adds more complexity and with it more granular control. It is a steep learning curve if you really want to use it to it's full potential, and if you have a small relatively simple network then you won't gain much.
Your decision.

Collapse -

Upgd nt4 pdc to w2kad

by cdietz In reply to Upgd nt4 pdc to w2kad

Poster rated this answer

Collapse -

Upgd nt4 pdc to w2kad

by cdietz In reply to Upgd nt4 pdc to w2kad

Answer #1 looks kinda like the line of thought I was looking at. Very Detailed, very complex, Many points of failure (Things I could do wrong) The server is at a hosting center and only needs to authenticate a few VPN logins from developers, The IWAM and IUSER accounts for a couple of IIS servers, DB and a few file servers. My main concern is prior to me coming to this company, they installed all the customers dynamically updating (Customer.mycompany.com) DNS on a Linux DNS box. If I tank this, thousands of customers will be in screwed (I will be screwed). I will not be using any groups, OU's or policys with AD. From both of your answers so far it is looking like i should just replace the Pile Of PDC (needs reboot 3-4 times a day now)with a new fresh server with nt4 pdc on it. What do you think, either of you guys?

Collapse -

Upgd nt4 pdc to w2kad

by bchesmer In reply to Upgd nt4 pdc to w2kad

If you have no valid requirement to move to W2K, then I would stick with the NT 4.0. Just my 2 cents.

Collapse -

Upgd nt4 pdc to w2kad

by cdietz In reply to Upgd nt4 pdc to w2kad

Poster rated this answer

Collapse -

Upgd nt4 pdc to w2kad

by cdietz In reply to Upgd nt4 pdc to w2kad

This question was closed by the author

Back to Windows Forum
9 total posts (Page 1 of 1)  

Related Discussions

Related Forums