How difficult is it to "upgrade the domain schema" from Windows 2000 to 2003?

[Epsil0n00]

We have a consultant that is trying to tell us that upgrading our Windows 2000 domain to Windows Server 2003 schema is really difficult. Hence, my supervisor is convinced that we shouldn't upgrade any of our 15+ servers to Windows 2003, but leave them all on 2000 instead (to avoid needing to upgrade the schema).

How complex is this domain schema upgrade and what is involved in it? Is it worth upgrading the schema to 2003 so that we can run 2003 servers... or is best to continue to run Windows Server 2000 machines. By the way, we are about to install 4-5 new servers (new hardware) and we're trying to decide whether to upgrade the schema and use 2003 on these new machines, or just stick with 2000.

What do you guys think!?
Thanks!
Epsil0n

 

[Rogue]

I don't think you have much of a choice. Microsoft is looking to kill off Win2k support soon I believe. Users will fight this for some time and Microsoft will keep them happy for a bit, but you should suck it up and migrate to Win2k3 sooner rather than later.

I can't see the schema upgrade being that difficult. Microsoft certainly isn't perfect at these things, but it should be pretty straight forward. Might look at some of the Quest migrator tools and see if they offer anything for this to make it easier.

 

[Epsil0n00]

The other thing our consultant claimed is that "there are some compatibility issues between Windows Server 2003 (and schema 2003) and Macintosh clients."

Now, all our Mac clients do on our network is get DHCP addresses, access Windows file shares, and print to Windows print queues. I can't imagine that there would be any problems...

Has anyone heard of any "compatibility issues" between Win Server 2003 and Mac clients?

Thanks

 

[Rogue]

Here's where I pretty much stopped reading, tell me if my hunch is correct:

"We have a consultant," and "really difficult" and "consultant claimed."

Sounds to me like they're trying to make money by way of FUD. If I weren't so tired, I'd help you research the topics at hand, but I've gotta get up at 6am tomorrow. I'll check back if I have some free time in the morning and see if I can help more. I the meantime, Google Groups are quite handy for things like this.

http://groups-beta.google.com/group...o+win2k3+schema&rnum=2&hl=en#8b520a5447990ae8

 

[Vegito]

What servers do you have now ?

Do you have exchange mail server ?
If yes, do you plan to use exchange 2003 ? if yes, you will need Windows 2003

Its easiler to build a W2K3 DC, transfer the FMSO roles and kill off your old W2K DC servers

Windows 2003 has stricter encryption, ie old ms lan client can't authenticate with 2003 DC but there are things you can turn off..

I dont use macs, so I can't help you but i'm assuming MAC will have the same authentication problem as an old win9x ms lan client..

 

[mobilecommand]

Howdy,

Basically your contractor is mostly blowing smoke in some areas or he is not very good.. Now mind you if your schema upgrade does go bad it can cause issues domain wide but there are a few items you can do to help minimize issues.. First of all you want to migrate to 2003 AD.. There are some really nice features you get.. I cannot tell you on the MAC side but in the links i put in the message will give you an idea..

Basically in a nutshell this is how you want to do your schema update.. Locate your domain controllers that host the schema and infrastructure operations masters. If there on the two diffrent servers i would have you transfers roles to 1 server.. On that 1 server preform a system state backup and if you have a disk cloneing software ghost the server as well.. Once you are done DISCONNECT THE SERVER FROM THE NETWORK.. You want to do this incase you get a bad schema update it will not replicate it though out the domain.. Once the server is off the network do all schema upgrades 2003 ad, exchange 2005 etc.. Check event viewer and make sure everything looks good. If there are no issues plug the server back into the network open up replmon and force replication and you are done.. If the upgrades go bad while you are disconnect from the network you can always restore from ghost or system state backup.. I have done schema ugrades and it aint no thing..


http://support.microsoft.com/default.aspx?scid=kb;en-us;325379

http://support.microsoft.com/default.aspx?scid=kb;en-us;555040

 

[Rapidskies]

Is there any reason you can't just add the 2003 servers as member servers?

Unless they "have" to be DC's or you need to run an app like Exchange 2003, you don't have to migrate your schema to use 2003 servers in your 2000 domain.

 

[mobilecommand]

you can have as many 2003 member server as you want but if you plan on running a 2003 DC and other servers that need it you need to update the schema..

 

[stash]

There is the potential for issues if you have already extended the schema for Mac OS X: http://support.microsoft.com/default.aspx?scid=kb;en-us;887426

mobilecommand's advice is good, except there is no Exchange 2005 yet Also, make sure you take his advice literally to disconnect the machine from the network. This does NOT mean shut down the box, then remove it from the network and reboot. This will cause problems due to the initial sync requirements put in with either SP3 or SP4 on 2000 (I can't remember off hand).

Also, Rogue, you are correct that this 'consultant' is spreading FUD. However, you are similarly spreading FUD by saying that Microsoft is trying kill of Windows 2000 support soon. Mainstream support just ended June 30th, but there are still five more years of support left for 2000. This was all communicated many months ago in a clear plan for support. Given the extraordinary costs involved with support for Microsoft, 10+ years of support for a single OS is very good. There are very few software vendors that support their products for that long.

Read all about it at http://support.microsoft.com/default.aspx?scid=fh;[ln];lifecycle

 

[GeekDrew]

Originally posted by: Epsil0n00
The other thing our consultant claimed is that "there are some compatibility issues between Windows Server 2003 (and schema 2003) and Macintosh clients."

Now, all our Mac clients do on our network is get DHCP addresses, access Windows file shares, and print to Windows print queues. I can't imagine that there would be any problems...

Has anyone heard of any "compatibility issues" between Win Server 2003 and Mac clients?

Thanks

Bringing Mac into the mix is like firing a canon at oneself and then declaring it to be merely a flesh wound.

We did not have an AD active at my last office prior to 2003 - I used 2003 when I built it about a year or so ago. I do know that it took several Apple engineers several days to get a lab of 25 computers to talk to our Active Directory + eDirectory - but I'm not sure what the problem was... I don't know if it was with AD or eD.