Re: Second SBS2003 Server with Exchange Public Folder Replication

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

By default, public folders aren't cached. So if you lose connectivity, you can't see the public folders. But if you add them to your favourites and enable caching on them, then they're stored as part of your offline folders. And if your connectivity goes out, they're still available.

--
Charlie.
http://msmvps.com/xperts64


"JohnB" <JohnB@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:5D2FC757-1CC7-43CE-A643-82E8F550FC9F@xxxxxxxxxxxxxxxx
Great advise and thank you for the support. Were already using RPC over HTTP
cached mode and will create a reduntand connection with a second provider.

How does adding PFs to users Outlook Favorites & configuring that for cached
mode as well help? Does this allow for the posts to be referenced without
server connectivity?

--
Thank you,
John


"Charlie Russel - MVP" wrote:

Good advice. I agree on all counts. If they need access to some specific
main office content outside of exchange, and connectivity is a problem, then
possibly a main off Terminal Server would be a useful addition, but it
doesn't sound like that is a need, at least at this point. Taking advantage
of RPC over HTTP is the key to this.

--
Charlie.
http://msmvps.com/xperts64


"Lanwench [MVP - Exchange]"
<lanwench@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:OQJJY3j5GHA.1252@xxxxxxxxxxxxxxxxxxxxxxx
> 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.
>
>
>
>


.

Relevant Pages

  • Re: So why SBS?
    ... Public folders will be in the next version.. ... If SBS isn't for you...that's fine. ... Mailenable is an example of a freeware or pay for extra's, mail server. ... It is infinitly simpler to configure than Exchange once installed. ...
    (microsoft.public.windows.server.sbs)
  • Re: SBS2K, Exch. 2K, Public Folder error 80040e19
    ... Exchange site directory name contains characters that Exchange 2000 Server ... temporarily uninstall IIS lockdown and URLScan tools, ... >named "Public Folders" as created by the SBS2000 server wizard. ...
    (microsoft.public.windows.server.sbs)
  • Re: So why SBS?
    ... Public folders will be in the next version.. ... The sad part of most of us is that we haven't even tried or practiced a backup/restore and we freak out over a 'single" SBS box when we haven't even tried to restore it from a harddrive. ... Exchange seems to mix its words and titles, the global/generic use of POP and SMTP for just about every Exchange function is dumb, MailEnable understands post office protocol and simple mail transfer protocol in a "meaningfull" way. ... The standard profiles in Server are quite effective assuming you add new users to the correct account in the first place and your note running more than 1 file server. ...
    (microsoft.public.windows.server.sbs)
  • Re: Public Folder Nightmare
    ... There are more on the Exchange 2003 web site. ... In this instance the Exchange machine was the first server in the ... Directory after an unsuccessful domain controller demotion) in an attempt ... Restore and mount the public folders, ...
    (microsoft.public.exchange.admin)
  • Re: Entourage 2004 crippling Exchange 2003
    ... The previous-to-SP2 mechanism Entourage used (at the instruction of the ... Exchange team) ended up causing significant performance issues on the public ... Very few Entourage clients accessing public folders would use ... all of the processing power of the server. ...
    (microsoft.public.mac.office.entourage)