In the first article of the series "How to add an additional Domain Controller from a remote office to the SBS domain" we have configured the SBS server and prepared it for a new additional domain controller. In this second article we will configure the Windows 2003 server that is located at the remote office so it can be joined to the SBS domain and promoted.

 

We will want the new server to be running DHCP, WINS and DNS, so these services are going to be added. We will configure RRAS so it will have a persistent VPN connection to the SBS network. DCPROMO will be run so the server is becoming an additional Domain Controller in the SBS network. We will correct the network adapters configuration, configure DHCP server and correct DNS server. Then we will check if the replication has completed and enable remote desktop so we can RDP to this new Domain Controller from within the SBS network.

 

The third article will have the finishing steps that will need to be done to complete the remote office setup. These steps are different for the SBS server and the additional Domain Controller.

 

I would like to thank Brian Desmond, Directory Services MVP, for his valuable additions, in particular about the DHCP event 1056 and the add new subnet in Active Directory Sites and Services (part 1).

 

The following chapters are included in this article:

Now that Mac OS 10.5 has hit the streets, there are folks who are wanting to know how to connect a Mac running the new operating system to an SBS network. This document covers steps for connecting a Macintosh running Mac OS 10.5 to an SBS 2003 network. This document assumes a healthy SBS network set up according to best practices.

This document provides instructions for connecting a Macintosh running Mac OS X 10.4 to an SBS 2003 server. This document was prepared using Mac OS X 10.4.10, but should apply to any later updates to 10.4. The server used to develop these screen shots has an internal domain with a .lan suffix. These steps should work with any internal domain suffix, including .local.  This document makes several assumptions:

Because of the release of the iPhone, there has been an increase in interest in configuring IMAP and POP3 services on SBS servers. In this author's opinion, providing access to e-mail via IMAP is better than POP3. The approach of IMAP more closely emulates how Exchange provides e-mail services in that messages are maintained on the server, and the IMAP client only pulls down what is needed. There are still security issues with IMAP, however, in that the default protocol still transmits the username and password information across the internet in clear text, and even though fewer sniffers are trained on IMAP ports to try and discover account credentials, the risk is still there.

 

To help protect account credentials, as well as e-mail contents, IMAP can be set up over SSL, which encrypts the entire transaction process, not just username and password. The iPhone and other devices can be easily set up to use IMAP over SSL, but you have to first set up the Exchange server on SBS to provide the secure mail transport. This document covers this implementation with SBS 2003 and ISA 2004. A separate document has been created for the process to follow with SBS 2003 Standard.