adding sbs 2003 R2 to an existing W 2003 domain

I am adding an sbs 2003 R2 to and exisiting Windows 2003 Server (non R2)
domain. I need to keep the exisitng server.

1. Should I join the new domain then demote the current server..need some
tips to look out for on this.
OR
2. It is only 15 users, thus I am considering starting from scratch and
copying the data across. I will import the existing PST files into exchange.
BUT to keep the exisitng server what should be done to demote it and to join
the new domain..then move data across?

thanks in advance, this is not my first sbs deploy, but first integration.
James

KMA James <KMA James@discussions.microsoft.com> wrote:
> I am adding an sbs 2003 R2 to and exisiting Windows 2003 Server (non
> R2) domain. I need to keep the exisitng server.
>
> 1. Should I join the new domain then demote the current server..need
> some tips to look out for on this.
> OR
> 2. It is only 15 users, thus I am considering starting from scratch
> and copying the data across. I will import the existing PST files
> into exchange. BUT to keep the exisitng server what should be done to
> demote it and to join the new domain..then move data across?
>
> thanks in advance, this is not my first sbs deploy, but first
> integration. James

I suggest you either go with option 2, or better still, www.sbsmigration.com

Any help here?

How to install Small Business Server 2003 in an existing Active Directory
domain
http://support.microsoft.com/kb/884453


"KMA James" <KMA James@discussions.microsoft.com> wrote in message
news:87EA0707-D762-4811-84C8-157A3749D7E1@microsoft.com...
>I am adding an sbs 2003 R2 to and exisiting Windows 2003 Server (non R2)
> domain. I need to keep the exisitng server.
>
> 1. Should I join the new domain then demote the current server..need some
> tips to look out for on this.
> OR
> 2. It is only 15 users, thus I am considering starting from scratch and
> copying the data across. I will import the existing PST files into
> exchange.
> BUT to keep the exisitng server what should be done to demote it and to
> join
> the new domain..then move data across?
>
> thanks in advance, this is not my first sbs deploy, but first integration.
> James

Hi James

In my opinion with 15 Users you would find that the time saved by using a
Swing Migration sbsmigration.com will more than pay for the small fee Jeff
charges for his kit which includes his support as well. A big advantage is
that the old server stays on line until you are ready to put the new server
on line and the WS's do not need to be touched. Then simply take the old
server to Workgroup status and join it to the Domain as a member server.

--
Frank McCallister SBS MVP
MCP Microsoft Small Business Specialist
COMPUMAC

"KMA James" <KMA James@discussions.microsoft.com> wrote in message
news:87EA0707-D762-4811-84C8-157A3749D7E1@microsoft.com...
> I am adding an sbs 2003 R2 to and exisiting Windows 2003 Server (non R2)
> domain. I need to keep the exisitng server.
>
> 1. Should I join the new domain then demote the current server..need some
> tips to look out for on this.
> OR
> 2. It is only 15 users, thus I am considering starting from scratch and
> copying the data across. I will import the existing PST files into
> exchange.
> BUT to keep the exisitng server what should be done to demote it and to
> join
> the new domain..then move data across?
>
> thanks in advance, this is not my first sbs deploy, but first integration.
> James

thanks , a very good option, i did go through the KB mentionned previously,
any good articles on how to bring down the 2003 server then re join without
reinstalling?
I need it for file/print and maybe keep the VPN services on it?
J



"Frank McCallister SBS MVP" wrote:

> Hi James
>
> In my opinion with 15 Users you would find that the time saved by using a
> Swing Migration sbsmigration.com will more than pay for the small fee Jeff
> charges for his kit which includes his support as well. A big advantage is
> that the old server stays on line until you are ready to put the new server
> on line and the WS's do not need to be touched. Then simply take the old
> server to Workgroup status and join it to the Domain as a member server.
>
> --
> Frank McCallister SBS MVP
> MCP Microsoft Small Business Specialist
> COMPUMAC
>
> "KMA James" <KMA James@discussions.microsoft.com> wrote in message
> news:87EA0707-D762-4811-84C8-157A3749D7E1@microsoft.com...
> > I am adding an sbs 2003 R2 to and exisiting Windows 2003 Server (non R2)
> > domain. I need to keep the exisitng server.
> >
> > 1. Should I join the new domain then demote the current server..need some
> > tips to look out for on this.
> > OR
> > 2. It is only 15 users, thus I am considering starting from scratch and
> > copying the data across. I will import the existing PST files into
> > exchange.
> > BUT to keep the exisitng server what should be done to demote it and to
> > join
> > the new domain..then move data across?
> >
> > thanks in advance, this is not my first sbs deploy, but first integration.
> > James
>

Jeff's kit will have some info on this but simply DCPROMO the 2003 server to
Workgroup status and the join to SBS as member server with
Http://servername/connectcomputer wizard giving it a different name.

--
Frank McCallister SBS MVP
MCP Microsoft Small Business Specialist
COMPUMAC

"KMA James" <KMAJames@discussions.microsoft.com> wrote in message
news:86746419-3CFC-45FF-A599-6232AF582725@microsoft.com...
> thanks , a very good option, i did go through the KB mentionned
> previously,
> any good articles on how to bring down the 2003 server then re join
> without
> reinstalling?
> I need it for file/print and maybe keep the VPN services on it?
> J
>
>
>
> "Frank McCallister SBS MVP" wrote:
>
>> Hi James
>>
>> In my opinion with 15 Users you would find that the time saved by using a
>> Swing Migration sbsmigration.com will more than pay for the small fee
>> Jeff
>> charges for his kit which includes his support as well. A big advantage
>> is
>> that the old server stays on line until you are ready to put the new
>> server
>> on line and the WS's do not need to be touched. Then simply take the old
>> server to Workgroup status and join it to the Domain as a member server.
>>
>> --
>> Frank McCallister SBS MVP
>> MCP Microsoft Small Business Specialist
>> COMPUMAC
>>
>> "KMA James" <KMA James@discussions.microsoft.com> wrote in message
>> news:87EA0707-D762-4811-84C8-157A3749D7E1@microsoft.com...
>> > I am adding an sbs 2003 R2 to and exisiting Windows 2003 Server (non
>> > R2)
>> > domain. I need to keep the exisitng server.
>> >
>> > 1. Should I join the new domain then demote the current server..need
>> > some
>> > tips to look out for on this.
>> > OR
>> > 2. It is only 15 users, thus I am considering starting from scratch and
>> > copying the data across. I will import the existing PST files into
>> > exchange.
>> > BUT to keep the exisitng server what should be done to demote it and to
>> > join
>> > the new domain..then move data across?
>> >
>> > thanks in advance, this is not my first sbs deploy, but first
>> > integration.
>> > James
>>