Cris
Mon Aug 11 20:23:15 CDT 2003
This is a multi-part message in MIME format.
------=_NextPart_000_011A_01C36046.65269370
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
No you cannot get the shared fax without a third party program
Why not just get SBS 2000 with SQL and a strong enough server to handle =
it all
Cheaper than adding a second server
--=20
Cris Hanna [SBS - MVP]
Please DO NOT email me directly but respond only in the newsgroup so =
that all can benefit.
"Robin" <gambhir@swiftnet.org> wrote in message =
news:14WZa.4932$ji.35746923@news.nnrp.ca...
I have to migrate a single server SBS 4.5 installation to a 2 server
installation. The second server will be running SQL Server 2000
exclusively. The first server will be running exchange and providing =
fax
services for the network. Essentially I am splitting the SBS =
functions over
two servers to maximize the performance of SQL server. SQL Server =
2000
seems to require a server Windows Server so I guess I'll have to run =
that on
the second machine. The first machine will either run SBS 2000 or =
Windows
Server 2000, depending upon whether I can get the shared fax =
facilities in
Windows Server 2000. If that 's the case, then I'll just run that and
Exchange without any SBS overhead.
Any comments on the above would be helpful. Especially those that =
might
recommend a direction to go in and a means of migrating from SBS 4.5 =
with a
minimum of pain. I know MS has some knowledge base materials on SBS
4.5-2000 migration but I haven't found any that refers to SBS to =
Windows
Server + Exchange migration.
Thanks for your help.
Robin.
------=_NextPart_000_011A_01C36046.65269370
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2800.1170" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>No you cannot get the shared fax =
without a third=20
party program</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Why not just get SBS 2000 with SQL and =
a strong=20
enough server to handle it all</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Cheaper than adding a second=20
server</FONT></DIV>
<DIV><BR>-- <BR>Cris Hanna [SBS - MVP]<BR>Please DO NOT email me =
directly but=20
respond only in the newsgroup so that all can benefit.</DIV>
<BLOCKQUOTE=20
style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
<DIV>"Robin" <<A=20
href=3D"mailto:gambhir@swiftnet.org">gambhir@swiftnet.org</A>> =
wrote in=20
message <A=20
=
href=3D"news:14WZa.4932$ji.35746923@news.nnrp.ca">news:14WZa.4932$ji.3574=
6923@news.nnrp.ca</A>...</DIV>I=20
have to migrate a single server SBS 4.5 installation to a 2=20
server<BR>installation. The second server will be running SQL =
Server=20
2000<BR>exclusively. The first server will be running exchange =
and=20
providing fax<BR>services for the network. Essentially I am =
splitting=20
the SBS functions over<BR>two servers to maximize the performance of =
SQL=20
server. SQL Server 2000<BR>seems to require a server Windows =
Server so I=20
guess I'll have to run that on<BR>the second machine. The first =
machine=20
will either run SBS 2000 or Windows<BR>Server 2000, depending upon =
whether I=20
can get the shared fax facilities in<BR>Windows Server 2000. If =
that 's=20
the case, then I'll just run that and<BR>Exchange without any SBS=20
overhead.<BR><BR><BR><BR>Any comments on the above would be helpful.=20
Especially those that might<BR>recommend a direction to go in and a =
means of=20
migrating from SBS 4.5 with a<BR>minimum of pain. I know MS has =
some=20
knowledge base materials on SBS<BR>4.5-2000 migration but I haven't =
found any=20
that refers to SBS to Windows<BR>Server + Exchange=20
migration.<BR><BR><BR><BR>Thanks for your=20
help.<BR><BR><BR><BR>Robin.<BR><BR><BR><BR></BLOCKQUOTE></BODY></HTML>
------=_NextPart_000_011A_01C36046.65269370--