I am working on a tiny network (just a handful of users) currently build around a 2003 SBS. The users are spread out over the country and log in through VPN. At the moment the Server functions as Remote access server and file server, as planned. There are no other servers in the "network". One issue that has crept up is maintaining information across computers. Each user has up to 3 computers that they use (desktop, laptop, 2nd desktop), and keeping information on the machines synchronized is difficult. We are using a hosting site for our website and email, and each desktop/laptop has Outlook on it, but they don't really synchronize. Email works so-so with IMAP, but calendars are a mess. Now we will add some mobile phones (iPhones), and then synchronization will become more of headache. So my idea was to install Exchange Server on the SBS server. I do have access to ES2003, so that's where I wanted to start, but I have doubts whether it is really worth the trouble. First, I don't want to host our own email site. I don't think that I have the required bandwidth available, and frankly, I'd rather keep that outsourced, especially it is "free" (well, included with the hosting we have to pay anyway). And I have heard that ES is really not the right tool to collect email from other sites. ES also requires me to install Active Directory, a domain server, etc., and I am not sure what the consequences are. Active Directory is, I think, pretty straight forward, but if I set up a domain structure, does everybody who wants to connect just for the file server functionality also have to be in the domain? Some of the users might not want to join a domain as they don't have the synch issues, and they would rather just use the server as a file server, just like now. So, I am a bit hesitant to jump into this, especially since the setup is working now (albeit with the synch problems), and I don't want to destroy that. What would you suggest? One very concrete question: If I set up a domain, what should I call it? Right now we have a domain, let's call it "MyDomain.com" registered, and html and emails go to the hosting site. Would I set up a domain (on the server), called "MyDomain.com", or would I set it up as, for example, "HQ.MyDomain.com" to avoid conflicts? Thanks for your help. mike

I would name the domain the same as your internet registered domain. I don't understand your fear of conflicts with using the same name. Consider a split-brain DNS, i.e., internal DNS with inside addresses for use inside your network, and an external DNS with names that need to be reached from the Internet. As to your larger question, my answer would be to seek the advice of a consultant. -- Ed Crowley MVP "There are seldom good technological solutions to behavioral problems." . "vistauser111" wrote in message news:8095ce6a-5713-450e-888e-7485ef9518aa... I am working on a tiny network (just a handful of users) currently build around a 2003 SBS. The users are spread out over the country and log in through VPN. At the moment the Server functions as Remote access server and file server, as planned. There are no other servers in the "network". One issue that has crept up is maintaining information across computers. Each user has up to 3 computers that they use (desktop, laptop, 2nd desktop), and keeping information on the machines synchronized is difficult. We are using a hosting site for our website and email, and each desktop/laptop has Outlook on it, but they don't really synchronize. Email works so-so with IMAP, but calendars are a mess. Now we will add some mobile phones (iPhones), and then synchronization will become more of headache. So my idea was to install Exchange Server on the SBS server. I do have access to ES2003, so that's where I wanted to start, but I have doubts whether it is really worth the trouble. First, I don't want to host our own email site. I don't think that I have the required bandwidth available, and frankly, I'd rather keep that outsourced, especially it is "free" (well, included with the hosting we have to pay anyway). And I have heard that ES is really not the right tool to collect email from other sites. ES also requires me to install Active Directory, a domain server, etc., and I am not sure what the consequences are. Active Directory is, I think, pretty straight forward, but if I set up a domain structure, does everybody who wants to connect just for the file server functionality also have to be in the domain? Some of the users might not want to join a domain as they don't have the synch issues, and they would rather just use the server as a file server, just like now. So, I am a bit hesitant to jump into this, especially since the setup is working now (albeit with the synch problems), and I don't want to destroy that. What would you suggest? One very concrete question: If I set up a domain, what should I call it? Right now we have a domain, let's call it "MyDomain.com" registered, and html and emails go to the hosting site. Would I set up a domain (on the server), called "MyDomain.com", or would I set it up as, for example, "HQ.MyDomain.com" to avoid conflicts? Thanks for your help. mike Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."