• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 208
  • Last Modified:

exchange implemetation between two sites

Hello,

I will try to explain the situation first:

There is a main site A, and a remote site B.
Main site A has a win2003 server and a win2003 TS server.
site B has a sbs 2003 server
The users want to transfer files from site A to site B and vice versa.
The users also want to use exchange.
Right now these are two different forests domainA.local and domainB.local
Their email domains are domainA.com and domainB.com
Right now they are using another mailserver system.

The idea is to add another win2003 server to site An with exchange 2003
The site B only contains a few users, so maybe it's best to format that sever and start with server 2003 + exchange?
That way we will have the same domainname: siteA.local with an additional DC at site B.
The problem is, is this the 'best' solution?
What about the domain names?
users at site a want to use user@domainA.com, users at site b want to use user@siteB.com.
One more thing ... sometimes users from siteA are working at siteB.
Won't this be a problem? when A users logon to site B (same AD), will they use exchangeA instead of the exchangeB server???
Won't this be a problmen over vpn?
What about trust relationship, will this be needed?

alot of questions :)
I hope somebody can help me a little bit.
0
suppsaws
Asked:
suppsaws
  • 2
  • 2
1 Solution
 
suppsawsAuthor Commented:
one more thing.
since site B is only 5 users, is this adittional exchange needed?
Can't they just work over vpn for their exchange (at site A?)
What about the domain names .... when there is only one exchange at site A ....
can users at site B use a different domain name? (siteB.com)
0
 
SembeeCommented:
You can't trust an SBS domain. Therefore if you wanted to use trusts you would have ditch the SBS machine.

You have two options.

Based on what you have written above you could simply treat these as two different sites.
How frequently are they going to want to transfer files? You could simply find a remote access solution - possibly web based.

Another option considering the size of site b would be to simply centralise everything for Exchange and domain on site a. Exchange can manage multiple SMTP domains quite easily. If the users in Site B have lots of files, then give them a local file server (possibly make it a global catalog domain controller as well) to store local data on, and have email on the single server at site a.

Simon.
0
 
suppsawsAuthor Commented:
Simon,

indeed, trust an sbs is not possible, that is why I will format the sbs server and put windows server 2003 on it.
I think this will be cheaper than a transition pack.
It's not that much file transfer, so I hope the vpn speed will be ok.
I think I will centralise on site A because that site contains most users.
0
 
SembeeCommented:
Whether a transition is cheaper or not depends on what you already own. If you already have the Exchange server and cals, then it is cheaper. If you need to purchase, then it can be cheaper to get a transition pack.

Simon.
0

Featured Post

Get your Conversational Ransomware Defense e‑book

This e-book gives you an insight into the ransomware threat and reviews the fundamentals of top-notch ransomware preparedness and recovery. To help you protect yourself and your organization. The initial infection may be inevitable, so the best protection is to be fully prepared.

  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now