utilize
asked on
Migrating Windows 2000 Server domain to Windows SBS 2003
Hi All,
I plan to do the above on the system explained.
Current system:
2 x Windows 2000 DCs and 1 x Windows 2000 Exchange Server (AD Connector) and 1 Windows 200 Member Server.
Going to migrate to 2 x new boxes - 1 x Windows 2003 SBS and 1 x Windows 2003 Enterprise DC.
I plan to do the following to migrate the domain.
- Service pack 4 all 2k servers (DCs)
- Extend AD Schema to accomodate Win2k3
- Build Win2k3 SBS but not run sbs wizard (effectively std edition).
- Join Win2k3 SBS server to win2k domain
- Transfer FSMO roles and make PDC (effectively)
- Run SBS Wizard and finish SBS'ing the server - including installing Exchange 2003
- Migrate/Move Exchange mailboxes accross to new SBS Server
- DCPROMO redundant 2k boxes out of the domain
- DCPROMO new 2k3 Enterprise server into domain
Now does the above sound like a) a good plan and b) is there anything major in particular i should be wary of.
Is there a better way of migrating the domain? Is this a good / efficient way of doing this?
Any thoughts, tips and recommendations much appreciated.
I plan to do the above on the system explained.
Current system:
2 x Windows 2000 DCs and 1 x Windows 2000 Exchange Server (AD Connector) and 1 Windows 200 Member Server.
Going to migrate to 2 x new boxes - 1 x Windows 2003 SBS and 1 x Windows 2003 Enterprise DC.
I plan to do the following to migrate the domain.
- Service pack 4 all 2k servers (DCs)
- Extend AD Schema to accomodate Win2k3
- Build Win2k3 SBS but not run sbs wizard (effectively std edition).
- Join Win2k3 SBS server to win2k domain
- Transfer FSMO roles and make PDC (effectively)
- Run SBS Wizard and finish SBS'ing the server - including installing Exchange 2003
- Migrate/Move Exchange mailboxes accross to new SBS Server
- DCPROMO redundant 2k boxes out of the domain
- DCPROMO new 2k3 Enterprise server into domain
Now does the above sound like a) a good plan and b) is there anything major in particular i should be wary of.
Is there a better way of migrating the domain? Is this a good / efficient way of doing this?
Any thoughts, tips and recommendations much appreciated.
I have some doubts about this working - but I'm curious - so I'm hoping EE's resident expert on SBS will speak up.
In general, I have never heard of this kind of plan working - I don't think it will - but he'll know. Typically, most people when migrating to SBS will use ADMT
In general, I have never heard of this kind of plan working - I don't think it will - but he'll know. Typically, most people when migrating to SBS will use ADMT
SBS acts exactly as regular server 2003 as long as you leave the wizards out of it. Of course, you're going to be nagged to death if you don't make it "king 'o the hill" in short order, but for the pruposes of his swing it'll be fine.
Once joined to the domain and the roles are transferred, you can finalize the SBS component with the remaining steps in the wizard.
This will work.
Once joined to the domain and the roles are transferred, you can finalize the SBS component with the remaining steps in the wizard.
This will work.
I would be concerned because SBS, in my experience requires AD to be setup a specific way - if you don't have that setup, you can have problems - and not just problems using the wizard. When I setup my first SBS server I renamed some of the default OUs and I had major issues logging in from my XP workstations until I renamed them back. SBS WANTS to be setup a certain way, bypassing that way COULD cause SERIOUS problems.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
lee,
Please email me - EE alias at gmail. Unrelated to this post. Kind of urgent.
NM
Please email me - EE alias at gmail. Unrelated to this post. Kind of urgent.
NM
ASKER
Well, the above solution is good and works.
However, if there is any question of your AD integrety and or there are known issues with the domain being unstable i would not recommend this.
We had awful GC replication issues and spent along time fixing them.
Thanks for all the help! Techsoeasy gets the points as i used this Whitepaper to complete this!
However, if there is any question of your AD integrety and or there are known issues with the domain being unstable i would not recommend this.
We had awful GC replication issues and spent along time fixing them.
Thanks for all the help! Techsoeasy gets the points as i used this Whitepaper to complete this!
I think if I were to do it this way, I'd use an evaluation copy of Server 2003 Standard and upgrade the non-Exchange Win2K server... even though i'm not a fan of in-place upgrades, since you had the extra DC anyhow this would have been a chance to deal with your AD before adding the SBS to the mix.
Don't know if that would have made the GC errors easier to deal with, but just a hunch that it would have.
Glad you got it all sorted out though.
Jeff
TechSoEasy
Don't know if that would have made the GC errors easier to deal with, but just a hunch that it would have.
Glad you got it all sorted out though.
Jeff
TechSoEasy
Make sure the new SBS DC is also a Global Catalog.
You should be in good shape if you move slowly and watch for & correct and errors as they come up.