I need some here with a rather complicated issue. I'll try to go
through it as thoroughly as possible.

I currently have 3 NT 4.0 Servers in an NT Domain. One of them acts as
a Fax Server, another as a Print Server. I do not wish to upgrade them,
they work fine as is and I'd like to keep them.

I now have to add an SBS 2003 server to the mix. The SBS 2003 Server
will host the windows version of our "enterprise-wide" software (we're
currently using the DOS version, hosted on one of the NT Servers)
I chose SBS 2003 because it gave me SQL Server at a lower cost than
purchasing both Server 2003 and SQL Server 2005 separately.

The initial plan was to have the SBS machine create it's own domain and
then create a trust relationship between the 2003 Domain and my old NT
4.0 Domain. However, I have been told that this is not possible with
SBS 2003.

So, this leaves me with a dilemma, along with a couple possible solutions...

1) Return SBS 2003, and suck up the extra cost of Server 2003 and SQL
Server 2005. then make 2 Domains with a trust relationship.

2) Allow SBS 2003 to create it's domain, and then place the 3 NT 4.0
Servers within that domain as stand-alone servers (not sure if this is
even possible) This means ditching the NT 4.0 domain, but that's fine
if this will work.

So, what do you think would be the best solution?

Thanks in advance,
Mike

Hi Michael,

You could use SwingIT to migrate your NT domain accounts to SBS, then simply
reinstall the NT domain controllers as member servers after the migration,
saving your users the headache and confusion of new domain, new usernames
and recreating profiles etc. That's what we decided to do and I must say
it's saved a lot of aggravation, as well as saving the company $$ by using
SBS over individual Windows 2003, ISA, SQL and Exchange software and
licenses.

www.sbsmigration.com

--
hth,
SusanV


"Michael J. Zaun" <mikez@canfieldelectronics.com> wrote in message
news:uG1IRrcNHHA.4992@TK2MSFTNGP04.phx.gbl...
>I need some here with a rather complicated issue. I'll try to go
>through it as thoroughly as possible.
>
> I currently have 3 NT 4.0 Servers in an NT Domain. One of them acts as a
> Fax Server, another as a Print Server. I do not wish to upgrade them,
> they work fine as is and I'd like to keep them.
>
> I now have to add an SBS 2003 server to the mix. The SBS 2003 Server will
> host the windows version of our "enterprise-wide" software (we're
> currently using the DOS version, hosted on one of the NT Servers)
> I chose SBS 2003 because it gave me SQL Server at a lower cost than
> purchasing both Server 2003 and SQL Server 2005 separately.
>
> The initial plan was to have the SBS machine create it's own domain and
> then create a trust relationship between the 2003 Domain and my old NT 4.0
> Domain. However, I have been told that this is not possible with SBS
> 2003.
>
> So, this leaves me with a dilemma, along with a couple possible
> solutions...
>
> 1) Return SBS 2003, and suck up the extra cost of Server 2003 and SQL
> Server 2005. then make 2 Domains with a trust relationship.
>
> 2) Allow SBS 2003 to create it's domain, and then place the 3 NT 4.0
> Servers within that domain as stand-alone servers (not sure if this is
> even possible) This means ditching the NT 4.0 domain, but that's fine if
> this will work.
>
> So, what do you think would be the best solution?
>
> Thanks in advance,
> Mike

Another (late) note. You could use UPROMOTE to demote the existing NT4
xDCs from Domain Controller status to member servers and join them to
your SBS domain.

http://utools.com/UPromote.asp

-Lee

Michael J. Zaun wrote:
> I need some here with a rather complicated issue. I'll try to go
> through it as thoroughly as possible.
>
> I currently have 3 NT 4.0 Servers in an NT Domain. One of them acts as
> a Fax Server, another as a Print Server. I do not wish to upgrade them,
> they work fine as is and I'd like to keep them.
>
> I now have to add an SBS 2003 server to the mix. The SBS 2003 Server
> will host the windows version of our "enterprise-wide" software (we're
> currently using the DOS version, hosted on one of the NT Servers)
> I chose SBS 2003 because it gave me SQL Server at a lower cost than
> purchasing both Server 2003 and SQL Server 2005 separately.
>
> The initial plan was to have the SBS machine create it's own domain and
> then create a trust relationship between the 2003 Domain and my old NT
> 4.0 Domain. However, I have been told that this is not possible with
> SBS 2003.
>
> So, this leaves me with a dilemma, along with a couple possible
> solutions...
>
> 1) Return SBS 2003, and suck up the extra cost of Server 2003 and SQL
> Server 2005. then make 2 Domains with a trust relationship.
>
> 2) Allow SBS 2003 to create it's domain, and then place the 3 NT 4.0
> Servers within that domain as stand-alone servers (not sure if this is
> even possible) This means ditching the NT 4.0 domain, but that's fine
> if this will work.
>
> So, what do you think would be the best solution?
>
> Thanks in advance,
> Mike