Cris
Fri Apr 28 15:01:48 CDT 2006
This is a multi-part message in MIME format.
------=_NextPart_000_000B_01C66AD4.AC454670
Content-Type: text/plain;
charset="Utf-8"
Content-Transfer-Encoding: quoted-printable
You've pretty much got it...introduce a second server into the SBS =
domain...win2k or win2k3, make it a DC, then you could take it off the =
network, seize the FSMO roles, take the SBS server down and bring the =
new server online and now you have a NON-SBS domain which could support =
trusts.
Of course there are issues such as data, mail boxes, etc.
--=20
Cris Hanna [SBS-MVP]
--------------------------------------
Please do not respond directly to me, but only post in the newsgroup so =
all can take advantage
"Don" <Don@discussions.microsoft.com> wrote in message =
news:6887AFB5-DFDA-490F-9852-7AACEC931D13@microsoft.com...
My company purchased another company about a year ago. The decision =
at the=20
time was to leave their infrastructure in place. My company is on a =
2000-AD=20
domain, the subsidiary is on SBS 2000. There wouldn't be any problems =
except=20
that SBS does not allow any trust relationships. This is going to =
come into=20
play when an ERP software package is rolled out, they are going to be=20
sending/receiving data to/from my company via VPN. At the moment I =
don't see=20
any way out of this except getting rid of SBS which will be a pain =
since=20
there wasn't really a new server that was budgeted for. Guess I'm in =
for a=20
fun month unless there is some better way to do this that I'm not =
seeing.
Thank you,
Don
------=_NextPart_000_000B_01C66AD4.AC454670
Content-Type: text/html;
charset="Utf-8"
Content-Transfer-Encoding: quoted-printable
=EF=BB=BF<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Dutf-8">
<META content=3D"MSHTML 6.00.2900.2873" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>You've pretty much got it...introduce a =
second=20
server into the SBS domain...win2k or win2k3, make it a DC, then you =
could take=20
it off the network, seize the FSMO roles, take the SBS server down and =
bring the=20
new server online and now you have a NON-SBS domain which could support=20
trusts.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Of course there are issues such as =
data, mail=20
boxes, etc.</FONT></DIV>
<DIV><BR>-- <BR>Cris Hanna=20
[SBS-MVP]<BR>--------------------------------------<BR>Please do not =
respond=20
directly to me, but only post in the newsgroup so all can take =
advantage</DIV>
<BLOCKQUOTE=20
style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
<DIV>"Don" <<A=20
=
href=3D"mailto:Don@discussions.microsoft.com">Don@discussions.microsoft.c=
om</A>>=20
wrote in message <A=20
=
href=3D"news:6887AFB5-DFDA-490F-9852-7AACEC931D13@microsoft.com">news:688=
7AFB5-DFDA-490F-9852-7AACEC931D13@microsoft.com</A>...</DIV>My=20
company purchased another company about a year ago. The decision =
at the=20
<BR>time was to leave their infrastructure in place. My company =
is on a=20
2000-AD <BR>domain, the subsidiary is on SBS 2000. There =
wouldn't be any=20
problems except <BR>that SBS does not allow any trust =
relationships. =20
This is going to come into <BR>play when an ERP software package is =
rolled=20
out, they are going to be <BR>sending/receiving data to/from my =
company via=20
VPN. At the moment I don't see <BR>any way out of this except =
getting=20
rid of SBS which will be a pain since <BR>there wasn't really a new =
server=20
that was budgeted for. Guess I'm in for a <BR>fun month unless =
there is=20
some better way to do this that I'm not seeing.<BR><BR>Thank=20
you,<BR><BR>Don</BLOCKQUOTE></BODY></HTML>
------=_NextPart_000_000B_01C66AD4.AC454670--