General discussion

Locked

Plan for upgrading NT to w2k3 AD

By ct98 ·
I am in the planning stages of my network upgrade from NT to AD (w2k3). First I am going to upgrade the domain to AD then work on my Exch migration. I want to run my method by the group an make sure I have my steps straight. We are a small network with about 6 servers, (nt/2000).

I am going to be retiring the current PDC. I am going to bring up the new server with NT4 (as a BDC). Take down the old PDC and promote the BDC to the PDC and upgrade it to w2k3. Install AD and run it that way until I am ready to run the Exchange migration. It sounds pretty straightforward to me, but those plans are the ones that go most wrong.

Does anyone see any problems with this migration? Would another plan be even simpler? Thanks for the feedback in advance.

This conversation is currently closed to new comments.

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

All Comments

Collapse -

The other option - ADMT

by Chris.. In reply to Plan for upgrading NT to ...

OK, you should right about now sacrafice a small fury woodland animal of your choice to the folks that developed ADMT at Microsoft.

Personally unless you have a solid reason for inplace upgrading, I would start out with a new Domain and Win2003 install. While there is a fairly even split of those of us who like either in place or parallel turn ups, I would challenge you to ask yourself why either option is the one you should choose.

I'd also recommend that unless you've done the 2003 training that you engage a VAR for professional services. Also beware the Exchange upgrade and make sure you're ready for it.

Just remember 2003 is locked down from the get go, you'll spend a week or two just loosening the securities depening on your users access and experience.

Also lean about GPO's ... you can migrate 90-100% or your logon scripts into GPO's.

Think about and document your idea's on the OU Structure as well. Have that in place prior to starting. Matter of fact, creating and managing OU's is a perfect Jr. Admin or Help Desk task!! So think about that as well.

Evaluate you're current security groups, then review the new options available to you in AD (domain and global groups) and associate that to the OU Structure.

I'm finding most customers are designing OU/AD Structure based on a few things. Usually it is Geographic dispersal or by Business unit organization. I've got one customer who's doing both. This just demonstrates the flexiblity of AD.

Remember with AD's ability to present more than 3 million objects you can easily overwhelm yourself and our peers if you don't apply the KISS rule!!!!

Here is one basic OU structure layout

joesnuff.com
_____________
joesnuffy.corp
Users
Computers
Servers
All the other default OU's

Atlanta
Support
Computers
Users
Groups
Sales
Inside
Computers
Users
Groups
Outside
Computers
Users
Groups
Portland
Executive
Computers
Users
Groups
HR
Computers
Users
Groups

You will notice a reoccuring theme with the base sub OU structure of Computers, Users and Groups. The first two are obvious, and the groups OU can be used for Security groups, Distribution list groups etc. You can also use this basic type of structure to delegate control easier. Say you want you're e-mail admin to manage all of the security groups (because with AD intergration, Exchange 2k and 03 both reference the security groups if you've given the group an addy) so the Mail Admin would only have rights to the Groups OU's in each of the OU's. Also this lets you be more specific with your GPO's. You can use the Computer portion just on the Computers OU and the User portion on just the Users sub OU's ..

Hope that helps and look around this site. There are some really good documents you can use for post and pre migration documentation and planning.

Don't skimp on this effort, once you impliment an inplace migration you'd play **** going back!!! Yet another reason for a parallel upgrade.

Collapse -

Plan for upgrading NT to w2k AD

by techrepublic In reply to Plan for upgrading NT to ...

Same situation here, except going to win2k. Problem is I can't find any good documentation or planning advice for an "In Place Upgrade". Seems everything is for migration and very large enterprise's. Do you have an actual "design" plan? Tony

Collapse -

Well

by Chris.. In reply to Plan for upgrading NT to ...

This is what I do for a living actually. I design and deploy enterprise solutions.. Win2K Win 2003 .. All exchange flavors and Citrix.

If you're taking the leap to AD you might as well go for 2003. You should be able to snag a great deal on the licensing right now.

So short of giving away professional trade secrets :) All I can suggest is that you take a look at one of the Win2k design and deployment books. There are so many out there that I can't really recommend one over the others. Well other than to say that you most likely can't go wrong with the MS Press books on the subject.

Again, if you don't have AD experience you'll want to get some help on the finer points of FISMO placement, OU design and all of the other wiz bang options and functionality.

Collapse -

Technet

by joe_beasley In reply to Plan for upgrading NT to ...

Plenty of info is available on technet. I found http://www.microsoft.com/downloads/details.aspx?familyid=6cde6ee7-5df1-4394-92ed-2147c3a9ebbe&displaylang=en

Back to IT Employment Forum
4 total posts (Page 1 of 1)  

Related Discussions

Related Forums