Partager via

Second server scenarios

  • Article

Updated: February 17, 2009

Applies To: Windows SBS 2008

This section discusses scenarios for implementing a second server using Windows SBS 2008 Premium.

Second server scenarios

Windows SBS 2008 Standard supports e-mail, remote users, file and print services, common administration tasks, network security, and Web-based collaboration tools.

By using Windows SBS 2008 Premium with a second server, you can extend the functionality on a separate operating system in the Windows SBS 2008 network without impacting the original server. For example, you could set up a second server at a remote office to improve the connection speed between sites. How you use the second server that is included in Windows SBS 2008 Premium depends on the requirements for your environment.

Note

It is recommended that you avoid running the multiple functions mentioned earlier on the second server at the same time. For more information, see Guidelines for Windows SBS 2008 Premium deployment.

The following are typical usages for the second server:

  • To provide file and print services or serve as a second domain controller for the Windows SBS 2008 domain in a remote office. This scenario can help you improve authentication and security management in the remote office.

  • To host non-Microsoft® or line-of-business applications.

  • To host SQL Server 2008 Standard for Small Business Server for line-of-business applications. (SQL Server 2008 Standard for Small Business is included in Windows SBS 2008 Premium.)

  • To host shared applications that use the latest Terminal Services technologies in Windows Server 2008.

  • To host Active Directory Lightweight Directory Services for directory service-based applications.

Deploying a second server

There are two primary scenarios for deploying Windows SBS 2008 Premium. In the first scenario, both servers are located at the main office and remote users connect to the main office. In the second scenario, the second server is located at a remote site.

Both servers at the main office

The simplest and least-expensive configuration is one where the server that is running Windows SBS 2008 and the second server are located at the main office. This is the easiest scenario for managing administrative duties, backups, and security. This scenario is best used where overall business administration is highly centralized.

In this scenario, most applications and data reside on servers in the main office, and users infrequently need remote access to line-of-business applications. If there are remote offices, the business tasks performed at each office are functionally independent. All interoffice traffic is routed over the Internet. All remote users connect to the main office by using Remote Web Workplace, Microsoft Office Outlook® Web Access (OWA), ActiveSync®, or a VPN connection. Remote Web Workplace is useful if users need to access their desktop applications and resources, and OWA and the ActiveSync technology are best suited for light e-mail usage. If you use Outlook to connect to Exchange Server by using remote procedure call (RPC) over HTTP, remote users can access Outlook without requiring a VPN connection.

The use of folder redirection or Volume Shadow Copy Service (VSS) is not recommended. For remote users who are connecting to the main office, most connection types are too slow to allow for folder redirection to a server at the main office. This means that enabling these features in Windows SBS 2008 for remote users is counterproductive.

All of the important servers and services in this scenario are at one location where you can maintain and troubleshoot them. You can enable Remote Desktop and work through most issues without visiting a remote site. Note that remote client computers are not backed up automatically. Therefore, unless remote users are diligent about backing up their data, any data loss is most likely not recoverable.

Second server at a remote site

This scenario describes larger businesses or those with more complex business operations. They most likely have server deployments at multiple sites and greater remote office independence. They often have developed line-of-business applications, and they have data to manage and control. Interoffice communication ranges from ongoing and frequent (such as regular updating of price lists, inventory, or financial data) to intermittent (occasional e-mail messages between users or departments). The second server at a remote office might provide file and print services, or it might be another domain controller that helps reduce authentication time.