How To Plan, Install, Manage, Maintain, Secure, Backup and Restore Small Business Server 2003 R2
Part Three - Pre-Installation
Please see what the Legal Eagles Make us say Here.
The description of pre installation suggestions is probably more complex than actually doing them. Here is a short list. You can also do some of these after the installation, but you should at least consider the steps involved and how you will proceed.
1. Internet Access
When I first started setting up SBS, we very often had 4 $250 (USD) modems for internet, modem sharing (since dropped from SBS), and Fax. Add to this the cost of 4 full service phone lines and the total expense was significant. While you can still use dial up internet access with SBS, most locations would choose some form of Broadband access, such as cable, DSL, Managed Circuit (T1 or variations), or even satellite. I suggest that you have this worked out for your business location before you make the plunge so at least you know what to expect.
Include in your research to determine that the provider does not preclude or block any of the services or data transmission that you will be using. For example, some ISPs specifically prohibit mail servers or data transfers from a unit attached to their system.
2. Email
SBS is designed for and intended to act as your corporate mail server. The Exchange Server component becomes to you what your ISP's mail server has been up to now. You can view it remotely, similar to Web Mail, and you can use pop3 protocol to pull the mail off to a remote mail program such as Outlook or Outlook Express. However, read on, and you will find that it is much more.
The SBS component Exchange Server is the best and biggest reason to purchase and use SBS. But to do it properly you need a method of receiving the mail into your SBS/Exchange mail server. By far the best method of doing so is Simple Mail Transfer Protocol, or SMTP. While MS furnishes a POP3 connector for pulling mail from your ISP into your local exchange server, it is neither reliable not elegant. SMTP is far better and more reliable. For a more or less complete explanation of SMTP mail look here.
SMTP mail will work best if your ISP assigns you a static IP address and sets up the appropriate DNS records. The records you need are MX (mail exchange) and PTR (reverse lookup). It is also beneficial to have a SPF record, to ensure that your mail address is not spoofed.
If your ISP will not, or cannot assign a static ip address for your internet connection, you can "rent" a service that tracks any changes to your dynamic ip and adjusts accordingly. In this case your ISP will point your mail exchange record and your reverse lookup record to the "rented" ip address, which will translate incoming mail and send it to your server.
The next best thing about SBS and Exchange Server is the ability to connect your Outlook Client directly to your Server over the web as though you are in the office connected to the network. Yes, that's right. The internet serves as a very long network cable so long as you can get a internet connection.
3. Public Web Site
Your public web site, www.your_internet_name.com - .net - .bus, whatever, can be hosted on your SBS server, but this is not a good idea.
Among other reasons, 1. Opening your SBS to html (port 80) traffic is very insecure. 2. Your server is not likely to be up as consistently or as securely as your ISP's Data Farm and you have to pay an ISP anyway, so why not take advantage of all the protections they offer?
In summary, internet access, email, and your public web site are matters for you to discuss with your ISP. It is usually their responsibility to setup the appropriate records in their DNS servers to allow your SBS system to work properly. You will need an A record, a C record, a MX record and a PTR record for each domain you use with Exchange Server. SPF records are a good idea as well.
Existing Windows Servers
There is good news here as well. Migration from existing Windows Server to SBS Server 2003, while not a snap, has been tested and documented to make the transition easier than you would expect.
For a discussion and documentation for migrating from existing Windows servers, look here for a Microsoft Document, and here, for a third party solution created by one of the most prolific SBS'rs on the planet.
Top.