Decommission SBS 2003 - transfer FSMO - set up trust

Hello,

We are in the beginning stages of making some major changes/upgrades.

Current:
- SBS 2003 (DC/FSMO)
- Windows 2003 Server (BDC)
- Member servers on domain
Both to be retired
Let's call this domain A

New:
- Hyper-V Core to host
- Window 2008 R2 (DC for new domain, required for ownership/name
change)
And let's call this domain B

Our goal is to establish a trust between the two domains to ease the
transition process workload and ensure access to resources between
domains.

When completing the New Trust the message states that it cannot be
completed because of the SBS 2003.

If I were to transfer the FSMO roles to the Windows 2003 server (and,
if needed, decommission the SBS 2003 - NOTE: we do not use Exchange or
any other features other than AD), would I be able to complete the New
Trust?

What do you recommend?

Also, would it just be easiest (or even possible) to perform an in-
place upgrade to Windows 2003 Standard on the SBS 2003 server?
Like I said, we only use the SBS 2003 server for AD (and BackupExec,
but we will handle reconfig of that).

John wrote:

> Hello,
>
> We are in the beginning stages of making some major changes/upgrades.
>
> Current:
> - SBS 2003 (DC/FSMO)
> - Windows 2003 Server (BDC)
> - Member servers on domain
> Both to be retired
> Let's call this domain A
>
> New:
> - Hyper-V Core to host
> - Window 2008 R2 (DC for new domain, required for ownership/name
> change)
> And let's call this domain B
>
> Our goal is to establish a trust between the two domains to ease the
> transition process workload and ensure access to resources between
> domains.
>
> When completing the New Trust the message states that it cannot be
> completed because of the SBS 2003.
>
> If I were to transfer the FSMO roles to the Windows 2003 server (and,
> if needed, decommission the SBS 2003 - NOTE: we do not use Exchange or
> any other features other than AD), would I be able to complete the New
> Trust?
>
> What do you recommend?

If you're taking out Exchange, you will be able to rename the domain
with RENDOM (the presence of Exchange 2003+ in an AD environment is not
itself a bar to renaming AD domains - but Exchange on a DC [a la SBS]
*is*). No need to mess about with a new domain or trusts at all.

--
Steve Foster
For SSL Certificates, Domains, etc, visit.:
https://netshop.virtual-isp.net

In article <afbc417b-be10-4a84-bc4f-8c957b2fc3a2
@fo10g2000vbb.googlegroups.com>, says...
>
> Hello,
>
> We are in the beginning stages of making some major changes/upgrades.
>
> Current:
> - SBS 2003 (DC/FSMO)
> - Windows 2003 Server (BDC)
> - Member servers on domain
> Both to be retired
> Let's call this domain A
>
> New:
> - Hyper-V Core to host
> - Window 2008 R2 (DC for new domain, required for ownership/name
> change)
> And let's call this domain B
>
> Our goal is to establish a trust between the two domains to ease the
> transition process workload and ensure access to resources between
> domains.
>
> When completing the New Trust the message states that it cannot be
> completed because of the SBS 2003.
>
> If I were to transfer the FSMO roles to the Windows 2003 server (and,
> if needed, decommission the SBS 2003 - NOTE: we do not use Exchange or
> any other features other than AD), would I be able to complete the New
> Trust?
>
> What do you recommend?

You're going about it wrong because SBS can't do Trusts between domains.

This site has a product (set of tools) that will make it simple,
painless, and you don't have to rename the domain or rejoin the
computers to the domain... The new SBS 2008 box can have the same IP as
the old server. My experience is that you can get all of the work done
and restore a backup of changed files to the new server overnight,
everyone will be back online with little or no downtime.

http://www.sbsmigration.com/

--
You can't trust your best friends, your five senses, only the little
voice inside you that most civilians don't even hear -- Listen to that.
Trust yourself.
(remove 999 for proper email address)