Re: Second SBS2003 Server with Exchange Public Folder Replication
- From: "Lanwench [MVP - Exchange]" <lanwench@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Mon, 2 Oct 2006 12:14:16 -0400
In news:22FEE608-AFE7-47FB-BA8F-C9F86B3CFE62@xxxxxxxxxxxxx,
JohnB <JohnB@xxxxxxxxxxxxxxxxxxxxxxxxx> typed:
Good day,
Were looking to install a second SBS2003 STD Domain Controller in a
remote site. We have 25 users total with 15 in our main office and 10
connecting remotely from our offsite office all working with a few
public folders. (30 user licenses installed) Our offsite staff has
grown from 5 to 10 and due to some infrequent connectivity problems
and the increase in users we would like to install a second domain
controller in our remote office replicating the public folders
between the two servers and build some redundancy should one of the
servers fail if possible.
Can we use SBS2003 as a second domain controller in our off site
office?
Nope. It would be a completely different AD domain, and you couldn't have
Exchange replicate between them.
If so then how if http://support.microsoft.com/kb/884453
states that only one SBS server can exist on the domain?
That is entirely correct.
Is there a support article that would indicate how to configure the
Exchange public folder replication for these two servers?
They can't.....
Would 25 additional licenses be required for the additional SBS
Server?
I'd forget this idea - it's overly complicated, and you likely won't get
what you wish or expect out of it. You can use only one SBS server in your
domain.
If this remote site is part of your company, another domain is unwise
anyway, even without SBS. I'd just stick a W2003 DC in that location (and
configure it for AD-integrated DNS). Set it up in its own AD Site/Subnet
(AD Sites & Services). The users will authenticate locally.
You could of course buy Exchange 2003 on that W2k3 server, and install it
into the existing Exchange org/admin group, but why? I think you'd need
Exchange CALs for it, and frankly, for 10 users in a remote location I don't
see why they'd really need their own Exchange server.
I'd just configure those users with Outlook 2003 using RPC over HTTP to the
main office's Exchange (SBS) box, using cached mode, and add the PFs to
their Outlook Favorites & configure that for cached mode as well.
.
- Follow-Ups:
- Re: Second SBS2003 Server with Exchange Public Folder Replication
- From: Charlie Russel - MVP
- Re: Second SBS2003 Server with Exchange Public Folder Replication
- Prev by Date: Re: 2 Outlook clients in the same profile
- Next by Date: Re: changing location of outlook files (.pst)
- Previous by thread: Re: Second SBS2003 Server with Exchange Public Folder Replication
- Next by thread: Re: Second SBS2003 Server with Exchange Public Folder Replication
- Index(es):
Relevant Pages
|
