Migratign to Windows Server 2003 AD

I have a client with a single Small Business Server 2000. We need to upgrade
to upgrade to Windows Server 2003.

I am aware of the ADMT which can transfer user and computer accounts to a
new domain, but this involves quite a bit of work on each workstation and
would like to maintain the existing active directory domain to avoid that.

Is it possible to do the upgrade in the following way? (I know it may be a
long shot, but my creative brain has been working over-time)
1) Install new Windows 2000 Server, promote to DC in SBS domain.
2) Disconnect SBS server from network.
3) Seize FSMO Roles on Windows 2000 DC.
4) Install new Windows 2003 server, do forest prep, domain prep, etc on 2000
DC, then promote to DC in 2000 domain.
5) Transfer FSMO roles to 2003
6) Demote Windows 2000 DC to member server.
7) Restore SQL and file data from backup.

If we manage to successfully do the upgrade in this way, will we be left
with an Active Directory with the same limitations as SBS 2000 e.g. only 50
workstations, no domain trusts, etc.?

Larry
Thu Aug 16 20:12:59 CDT 2007

Hi Derek:

You are describing the process perfected here:

www.sbsmigration.com

by a long time SBS_MVP, Jeff Middleton.

There are several more steps required in the process becuase of the nature
of SBS, and for the $200 cost of the kit, plus the VB scripts that you get,
plus the support provided, it is well worth it.

Larry

"Derek Bayer" <DerekBayer@discussions.microsoft.com> wrote in message
news:9F38748C-CDAE-4FDF-AD28-81D1BD95ED30@microsoft.com...
>I have a client with a single Small Business Server 2000. We need to
>upgrade
> to upgrade to Windows Server 2003.
>
> I am aware of the ADMT which can transfer user and computer accounts to a
> new domain, but this involves quite a bit of work on each workstation and
> would like to maintain the existing active directory domain to avoid that.
>
> Is it possible to do the upgrade in the following way? (I know it may be a
> long shot, but my creative brain has been working over-time)
> 1) Install new Windows 2000 Server, promote to DC in SBS domain.
> 2) Disconnect SBS server from network.
> 3) Seize FSMO Roles on Windows 2000 DC.
> 4) Install new Windows 2003 server, do forest prep, domain prep, etc on
> 2000
> DC, then promote to DC in 2000 domain.
> 5) Transfer FSMO roles to 2003
> 6) Demote Windows 2000 DC to member server.
> 7) Restore SQL and file data from backup.
>
> If we manage to successfully do the upgrade in this way, will we be left
> with an Active Directory with the same limitations as SBS 2000 e.g. only
> 50
> workstations, no domain trusts, etc.?

SuperGumby
Fri Aug 17 04:36:37 CDT 2007

I'll 2nd that.

Even though Derek has worked out most of the process himself I assure him:
having the defined procedure is well worth the cost.

I've done it. Developed my own migration strategy independently of Jeff
(well, not completely independently, I think I asked him for advice on more
than one occassion). Not because I wanted to but because I migrated systems
previous to Jeff's 'product' being available. Having been there and done it
I know how much time it takes, much more of my time than the value of the
migration kit, IMHO.

But hey, Derek, you're a good way along the path, don't wish to pay for a
kit? keep developing, you'll get there and there is no reason why anyone
should not assist you in doing so should you hit a problem. Though many of
us will point to Jeff's site there are no Jeff-droids (well, not many :-).

Though you are at 2000 I'd move the discussion to the 2003 group,
microsoft.public.windows.server.sbs, where a great many more responses could
be expected.

"Larry Struckmeyer" <lstruckmeyer(at)mis-wizards(dot)com> wrote in message
news:eyWu1tG4HHA.3900@TK2MSFTNGP02.phx.gbl...
> Hi Derek:
>
> You are describing the process perfected here:
>
> www.sbsmigration.com
>
> by a long time SBS_MVP, Jeff Middleton.
>
> There are several more steps required in the process becuase of the nature
> of SBS, and for the $200 cost of the kit, plus the VB scripts that you
> get, plus the support provided, it is well worth it.
>
> Larry
>
> "Derek Bayer" <DerekBayer@discussions.microsoft.com> wrote in message
> news:9F38748C-CDAE-4FDF-AD28-81D1BD95ED30@microsoft.com...
>>I have a client with a single Small Business Server 2000. We need to
>>upgrade
>> to upgrade to Windows Server 2003.
>>
>> I am aware of the ADMT which can transfer user and computer accounts to a
>> new domain, but this involves quite a bit of work on each workstation and
>> would like to maintain the existing active directory domain to avoid
>> that.
>>
>> Is it possible to do the upgrade in the following way? (I know it may be
>> a
>> long shot, but my creative brain has been working over-time)
>> 1) Install new Windows 2000 Server, promote to DC in SBS domain.
>> 2) Disconnect SBS server from network.
>> 3) Seize FSMO Roles on Windows 2000 DC.
>> 4) Install new Windows 2003 server, do forest prep, domain prep, etc on
>> 2000
>> DC, then promote to DC in 2000 domain.
>> 5) Transfer FSMO roles to 2003
>> 6) Demote Windows 2000 DC to member server.
>> 7) Restore SQL and file data from backup.
>>
>> If we manage to successfully do the upgrade in this way, will we be left
>> with an Active Directory with the same limitations as SBS 2000 e.g. only
>> 50
>> workstations, no domain trusts, etc.?
>
>