Re: expanding SBS / or wishing it fair well?

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

From: Aviciti #2 (smpclient_at_hotmail.com)
Date: 03/30/04 

Date: Tue, 30 Mar 2004 16:26:51 -0500

We could do with a single Exchange server at the corporate office. the problem is when sending large 50MB attachments we have to wait a considerable time form them to upload to the Exchange server across the WAN.

If there were a way to create an email at a remote site, then attach s a large file and hit send, and have it start uploading in the background it would be great. I don't know if cached mode will facilitate this.

Thanks,
Andrew
  "Cris Hanna (SBS-MVP)" <crisnospamhanna@mindspring.com> wrote in message news:uc0dyypFEHA.1240@TK2MSFTNGP10.phx.gbl...
  If he is insistant that you have an exchange server at each location, then you are going to have to "move up"

  One of the limitations of SBS is one single Exchange Server

  You can have multiple DCs...and do point to point VPNs

  But they would all have to connect to the SBS Exchange Server

  You are correct, you cannot have subdomains, but as I said you can have as many DCs at you wish

  --
  Cris Hanna, SBS-MVP
  ----------------------------------------------
  Please DO NOT respond to me directly but post all responses here in the newsgroup so that all can share the information
    "Aviciti #2" <smpclient@hotmail.com> wrote in message news:Oq%23QmjpFEHA.4012@TK2MSFTNGP09.phx.gbl...
    We have SBS at all three of our branch office locations. Our CFO has decided
    we need to connect all of our offices and make it one system... goodbye SBS
    (i think).

    He wantsa single directory service, with exchange servers at all three
    locations and the ability for each site to operate if the VPN is down.

    I just want to make sure there is no way to add subdomains, or secondary
    domain controllers to SBS, and exchange servers as well. We only have 48
    users, and we will probably hold strong at that for years, so we fall under
    the 75 user limit. It's just the distance between the employees that seems
    to be dictating the need for a different system.

    I will miss my SBS admin tools and slick http://servername/connectcomputer
    features :(

    Cheers!

Relevant Pages

  • RE: SBS 2000 & Excahnge 2003
    ... Thank you for posting in the SBS newsgroup. ... You need to purchase separate Windows server 2003 and Exchange server ... Worldwide Microsoft Licensing Sites ...
    (microsoft.public.windows.server.sbs)
  • Re: Adding Dedicated Exchange 2003 Server to SBS 2003 Network
    ... "To be honest, the SBS team doesn't test this scenario a heck of a lot, since it's unusual for a small busines to want to fork out the cash for an additional Windows Server, and a full blown Exchange 2003 server, plus all the CALs. ... The partners at the client want a dedicted Exchange server. ... SBS 2003 Premium Transition Pack and upgrade CALs, ...
    (microsoft.public.windows.server.sbs)
  • Re: expanding SBS / or wishing it fair well?
    ... We could do with a single Exchange server at the corporate office. ... the problem is when sending large 50MB attachments we have to wait a considerable time form them to upload to the Exchange server across the WAN. ... But they would all have to connect to the SBS Exchange Server ...
    (microsoft.public.windows.server.sbs)
  • Re: Allow exchange (that used to use domain) to send to outside em
    ... I have no need for the exchange server to have a public domain ... mprealestate1.com's mx record doesn't point to the sbs, ... that is a valid FQDN with public DNS settings and that users ... 1)The SMTP of the email name that is now on a remote server. ...
    (microsoft.public.windows.server.sbs)
  • Re: Exchange PLUS POP3
    ... I've had to modify this for all my clients...including my own SBS which is at R2 ... We even use RPC over http so our users can use Outlook from home. ... configuring the POP3 Locally. ... >> We originally were a POP3 users with our own Exchange Server setup>> on our ...
    (microsoft.public.windows.server.sbs)