Windows 2000 domain to SBS 2003
- From: "Rookie" <outbeyond@xxxxxxxxxxxxxxxx>
- Date: Mon, 11 Jun 2007 23:02:26 -0500
I have a client that is looking to upgrade their server. They currently are
using Windows 2000 Server standard as the one and only server and domain
controller and have 12 computers all XP Pro and about 14 users. They are
going to use their existing workstations - no replacements. They need a new
server and it makes sense that they use SBS2003 standard for the operating
system. They are not using Exchange currently. Their primary need is
increased storage space for file shares and redirected folders, centralized
backup, and increased performance. They are considering dual processor Xenon
with RAID5 array and new tape backup.
So I am wondering what is the best way to make the change as I know there
are a few possibilities. I really want to avoid having to join the computers
to a new domain because of managing profile migration from existing domain
accounts to a new domain account and to make it as seamless as possible for
the users. I have a couple possibilities in mind that I would like feedback
on that would seem be easier than using ADMT for the needs of this client.
They have no problem keeping their existing AD domain name.
One would be [after current backup of System State is done on current domain
controller] to join the new SBS 2003 server to the existing domain [after
doing adprep] as a domain controller, then transferring the five FSMO roles
to it, making the new server a global catalog server, making it the
licensing server, verifying that DNS is configured correctly on it and the
DNS zone for the domain shows including _srv records, using it for DHCP with
proper configuration including itself as DNS server, and then after being
sure replication is complete either dcpromoing the old server with Windows
2000 or simply use ntdsutil to remove it from AD. The KB article below
outlines the steps. I could move users to the proper OU and apply
permissions/groups templates to users and create mailboxes if Exchange is
used when done and move computers to the SBS OU when done IF needed though
the client already has Outlook installed on all their computers and has no
need for fax services, etc.
http://support.microsoft.com/kb/884453
The other though that I had would be to temporarily install Windows 2000
Server on the new server, dcpromo it to a domain controller, transfer the
five FSMO roles to it from the original domain controller, make it a global
catalog server, etc as above. Then dcpromo to demote the original domain
controller or clean it from AD after replication and then "upgrade install"
the new server from Windows 2000 Server to SBS 2003 standard.
Any thoughts on which method would be better of the two I am considering,
problems with either, or should I look at doing with ADMT??
Thanks for any advice.
Steve
.
- Follow-Ups:
- Re: Windows 2000 domain to SBS 2003
- From: Charlie Russel - MVP
- Re: Windows 2000 domain to SBS 2003
- Prev by Date: RE: Event ID 4353 - failure to run reports
- Next by Date: Re: SBS 2003 Setup.exe vs. Vista
- Previous by thread: RE: Event ID 4353 - failure to run reports
- Next by thread: Re: Windows 2000 domain to SBS 2003
- Index(es):
Relevant Pages
|
Loading
