Microsoft® Windows® Small Business Server 2003 is the flexible network solution designed to help small businesses. The integrated Windows Small Business Server 2003 is the one-computer server solution that supports up to 75 client computers. Integrating state-of-the-art server software, including Microsoft Windows Server™ 2003, Microsoft SQL Server™ 2000, Microsoft Exchange Server 2003, and Microsoft Internet Security and Acceleration (ISA) Server 2000, Windows Small Business Server 2003 helps you take advantage of the rapidly changing Internet, manage and grow customer relationships, and enhance your company's productivity. Adding Microsoft Business Solutions CRM Server provides great communication tools to help you keep in touch with current customers, reach new customers, and track sales and support activities using a shared contact database.

Important   Windows Small Business Server 2003 Premium Edition is the only edition of Windows Small Business Server 2003 that is supported with Microsoft CRM Server.

Windows Small Business Server 2003 installs and configures all application components through a single, integrated setup utility that checks disk space, system compatibility, and dependencies. It also significantly reduces the complexity of installation by automatically setting many common parameters to defaults and consolidating the number of screens encountered during setup.

For more information about Windows Small Business Server 2003, see:

• Windows Small Business Server 2003 home page, located at http://www.microsoft.com/windowsserver2003/sbs/default.mspx.

• Windows Small Business Server 2003 Getting Started Guide, located at http://www.microsoft.com/downloads/details.aspx?displaylang=en&familyid=483b6e22-8ed2-420b-915e-96d469347fb2

• Windows Small Business Server product documentation, located at http://www.microsoft.com/windowsserver2003/sbs/techinfo/productdoc/default.mspx

• Backing Up and Restoring Windows Small Business Server 2003, located at download.microsoft.com/download/b/d/8/bd8e1a40-d202-429a-8eb7-26300d62bcc9/BKU_BkupRstr.doc

• Windows Small Business Server 2003 "Troubleshooting," located at download.microsoft.com/download/5/6/1/561c9fd7-0e27-4525-94ec-4d2d38f61aa3/TSHT_SBS.htm

• "Technical Resources for Windows Small Business Server 2003," located at http://www.microsoft.com/windowsserver2003/sbs/techinfo/default.mspx

On This Page

Computer Requirements
Planning Your Deployment
Installing Windows Small Business Server 2003
Securing the Cache Against Pollution
Configuring External DNS for the SMTP Virtual Server
Installing SQL Server 2000
Installing Microsoft CRM
Installing the Microsoft CRM-Exchange E-Mail Router
Configuring Users and Queues
Backing up Windows Small Business Server 2003
Microsoft CRM Folders
Installing Microsoft CRM Using the Command Line

Computer Requirements

The following table lists the minimum computer equipment requirements and some recommendations for Windows Small Business Server 2003 recommended for up to 25 users. As mentioned, Windows Small Business Server 2003 supports up to 75 users.

Component	Requirement	Recommendation
Processor	Dual Intel Pentium Xeon PIII 700 MHz or comparable single CPU speeds	Dual 1.8 GHz (Xeon P4) or comparable single CPU speeds
Memory	512 MB of RAM	1 GB of RAM or higher, depending on your system configuration
Hard disk	8-gigabyte (GB) available hard disk space	SCSI hard drives partitioned with RAID 5 depending on your system configuration
Modem	No modem	Two modems, one for Shared Fax Service and one for Remote Access Service, Shared Modem Service, and Internet Security and Acceleration Server dial-up service
CD-ROM drive	CD-ROM drive	CD-ROM drive
Network Adapter card	1 Network adapter card (10/100 megabit Ethernet)	2 Network adapter cards (10/100 megabit Ethernet)
Video card	Video graphics adapter capable of 256 colors and 800 X 600 pixels	Video graphics adapter capable of 256 colors and 800 X 600 pixels

Hardware is the most common cause of performance problems in a Small Business Server network. You can optimize the performance of Small Business Server components - especially Exchange Server 2003 and SQL Server 2000 - by considering the following:

• Memory (RAM). Additional physical memory is often the key to improved performance, especially for Exchange Server 2003. To maximize server performance, be sure to increase system RAM.

• Redundant array of independent disks (RAID) hardware. Using multiple, fast small computer system interface (SCSI) drives (7200 RPM or faster) and individual SCSI disk controllers can improve input/output (I/O) processing as well as read/write times. If you are running SQL Server 2000 or expect heavy file sharing and printing on your Small Business Server network, consider using RAID.

Planning Your Deployment

The following are suggestions to consider as part of your deployment planning.

Use More Than One Physical Disk Partition

Important   If you plan to use disk as a backup destination rather than tape, have one additional disk in addition to the disks recommended for the solutions that follow. A backup disk should contain only backups; it should not contain any application or operating system files.

For disk fault tolerance and performance, use multiple physically separate partitions to deploy Microsoft CRM on Windows Small Business Server 2003. This is especially important because separate partitions are required to use the Full Recovery model in your Microsoft CRM databases for SQL Server 2000. Separate partitions are also required to use the Windows Small Business Server 2003 scheduled backup feature. The Backup cannot be used with SQL Server database files when SQL Server is running.

The Full Recovery model for a SQL Server database allows both full database backups and transaction log backups. A full database backup is always the first backup in a backup set and is the first one to be restored. Transaction log backups are incremental backups of the work done in a database since the last transaction log backup. When a SQL Server database is restored, the full database is restored followed by all transaction log backups that occurred after the database backup until the moment of the failure. For more information about backing up SQL Server databases, see Chapter 10 "Backing Up and Restoring Your Microsoft CRM System."

For the highest degree of disk fault tolerance, create a minimum of three physically separate partitions: one to act as the principal Small Business Server partition, a second that contains the data files for the Microsoft CRM Server databases, and a third that contains the transaction log files for the Microsoft CRM Server databases.

Note   If you use a three or four partition solution, you will not be able to specify separate locations for SQL Server data files and log files when you run SQL Server Setup. There can be only a single location for both data and log files by default. To implement a three or four partition solution, you must create the databases before installing Microsoft CRM Server and specify that the databases already exist when you run Microsoft CRM Server Setup. The databases you need to create are the Organization_name _MSCRM, Organization_name _METABASE, and  Organization_name _CRMCRYSTAL.

If you have only enough disks to create two RAID partitions or want to minimize the complexity of the three partition solution, use one partition as the principal Small Business Server partition and the second partition for all the SQL Server database files. In this configuration, data files and log files exist on the same drive, reducing the level of fault tolerance, and the Full Recovery model can still be used with the Small Business Server backup.

The recommended configuration uses SCSI disks along with a RAID controller. Use RAID 5 or RAID 0+1 for fault tolerance and as a balance between the best write performance and read performance. RAID 0+1 is more expensive in terms of hard disk cost, but provides the highest level of performance and redundancy.

Using a Pilot Implementation

Implementing Microsoft CRM on Windows Small Business Server 2003 can have a big impact on how you do business and how your employees work. For example, if your business currently does not have e-mail, Internet connectivity, server-based faxing, or a customer relationship management (CRM) package, you might assign three or four employees (or just a selected department) to try out these new features on a server configured the way that you expect the system to be deployed in the entire business. As these few employees learn the system, you will learn how this change might affect the rest of your employees.

If your business is not computerized and you plan to go to a full client/server networked business environment, you should consider a small pilot project with a few employees to make sure that you will attain the efficiency gains that you expect and that your employees will be able to handle the change in business practices.

If you plan to migrate from an older client/server or peer-to-peer network, you will want to make sure all your key line-of-business applications work on Windows Small Business Server 2003. Again, it is suggested that you set up a pilot project in which you install your business application on Windows Small Business Server 2003 and then test the application to ensure that it operates as you expect. Run this application on both the old and new platforms for a period of time or until you are comfortable with making the final switch to the new network.

Connecting Your Windows Small Business Server 2003 to the Internet

A small business can allow users to access Microsoft CRM resources over the Internet using the Internet Information Services (IIS) included in Windows Small Business Server 2003. When IIS is used to host the Microsoft CRM Web site, security for the Web site and speed for Internet users accessing Microsoft CRM are both important considerations. This section discusses the minimum security requirements and methods for estimating the data transfer capability (this is called "bandwidth") needed for quick access to the small business Web site.

The estimate of data transfer capability will have an impact on the modem configuration required to support the amount of data to be transferred. Generally, a higher-volume site requires more bandwidth and, as a result, needs more modems (or a faster connection type, such as XDSL, cable modem, ISDN, or T1) to handle the volume of data being transferred.

Securing the Network Connection to the Internet

Before adding your Small Business Server computer to the network, make sure that you have an Internet firewall. This firewall can be part of the physical device that connects the networked computers to the Internet, such as a router, or a software firewall like the one included in Windows Small Business Server 2003.

A Windows Small Business Server 2003 computer connected to a network where a hardware device is providing the firewall service uses only a single network adapter connected to the local area network and the Internet. The hardware firewall is a network device such as a DSL router. The hardware firewall has an IP address that is the default gateway for the Windows Small Business Server 2003 computer.

For the computer  to act as a software firewall, you should install two network adapters into your server. One provides a connection from the Windows Small Business Server 2003 computer to the client computers on the network. The other network adapter is connected to the hardware device providing the Internet connection, such as a DSL modem or a cable modem. In this configuration, the Windows Small Business Server 2003 computer is the default gateway to the Internet.

For more information about configuring the network connections and connecting Windows Small Business Server 2003 to the Internet, see the Windows Small Business Server 2003 Getting Started Guide on the first Windows Small Business Server 2003 CD. It is in the directory \Setup\I386 when you open the file Sbsgs.chm. See Chapter 2 "Before You Begin," Appendix B "Understanding your Network," and Appendix C "Network Configuration Settings."

Optimizing Bandwidth

When planning Internet connectivity, you must make a careful analysis of the planned services. For example, if only Microsoft CRM access from the Internet using HTTP is offered, you should not install File Transfer Protocol (FTP) services on Windows Small Business Server 2003.

When determining the type of connection for your hosted Microsoft CRM Web site, you must estimate the current and future bandwidth of the site correctly. Bandwidth is determined by the number of bits transferred per second (bps). Bandwidth is commonly noted in kilobytes per second (Kbps) or megabytes per second (Mbps). Sufficient bandwidth is required for quick access to resources on the small business Web site.

One of the best sources for determining current and future bandwidth needs is your Internet Service Provider (ISP). Your ISP's experience is invaluable to estimate initial and future needs. You can also use historical data from other Web sites to estimate bandwidth. The number of bytes transferred is a commonly recorded statistic on Web sites. Once the site is up and running, the system administrator can gather statistics on bytes transferred by using the performance counters of the ISA server.

Other Planning Considerations

In addition to the impact Microsoft CRM and Windows Small Business Server 2003 will have on your business and your business practices, you should also consider the following:

• It is highly recommended that your Small Business Server computer be used as a dedicated server and not also as a client computer (such as installing and using the Microsoft Office System). In addition, do not install Microsoft CRM Sales for Outlook on your Small Business Server computer.

• Make sure all the applications that you will install are compatible with Windows Server 2003. For more information, see "Supported Applications," located at http://www.microsoft.com/windowsserver2003/evaluation/suppapps/default.mspx.

• You have updated device drivers that are compatible with Windows Server 2003. (Contact the hardware manufacturers for updated device drivers for their products.)

• You have collected and recorded the information required for installation. See the "Before You Begin" section of the Microsoft Windows Small Business Server 2003 Getting Started Guide located on first CD for Windows Small Business Server 2003, in the \Setup\I386 directory. Double-click Sbsgs.chm and go to Chapter 2, "Before You Begin."

• If you are upgrading to Windows Small Business Server 2003, you have backed up all critical data on your system and tested your backup to ensure data integrity.

• You have secured an uninterruptible power supply (UPS) for your server. In the event of a power outage, a UPS will provide the server with enough backup power to save your data and safely shut down.

• You have planned your Small Business Server installation for growth. You may have only a few employees now, but in a year or two you may have 40. Plan your installation for 40; doing so will save you time and money in the future.

Windows Small Business Server 2003 Limitations

Managing expectations is important when you plan and deploy Small Business Server as the infrastructure of a small business network. Understanding the limitations of Windows Small Business Server 2003 is part of managing expectations. The known limitations are as follows:

• One domain. You can have only one domain on a Small Business Server network. In addition, this domain must be the root of the forest.

• No trust relationships. Because only one domain is supported on a Small Business Server network, there can be no trust relationships with other domains. This restriction on trust relationships includes parent-child trust relationships. There can, however, be other domain controllers on the network.

• A maximum of 75 client computers. Only 75 client computers can be connected to the small business server, assuming that the appropriate client access licenses are in place. Client access licenses are enforced in Windows Small Business Server 2003.

• Small Business Server computer as a dedicated server. It is highly recommended that your Windows Small Business Server 2003 computer be used as a dedicated server and not as a client computer (such as installing and using the Microsoft Office System). In addition, do not install Microsoft CRM Sales for Outlook on your Windows Small Business Server 2003 computer.

Installing Windows Small Business Server 2003

To install Windows Small Business Server 2003, you can start from a freshly formatted computer that does not have an operating system installed, or you can upgrade an existing Windows 2000 Server or Windows Server 2003 installation. (Upgrading to Windows Small Business Server 2003 from Small Business Server 2000 is discussed in Chapter 20 "Upgrade Microsoft CRM to Version 1.2.")

These steps assume a clean installation of Windows Small Business Server 2003 on a computer without an existing operating system.

This process may take several hours to complete.

Install Windows Server 2003

The first step for installing Windows Small Business Server 2003 is to install the operating system (OS). For a clean installation, you can start from the Windows Small Business Server 2003 distribution media. You will see the initial Windows setup steps and a screen where you can choose to install Windows or repair a damaged installation.

1. On the Welcome to Setup page, press ENTER to set up Windows.

2. Read the license agreement and press F8 to agree with its terms and continue the installation.

3. Next, a list of partitioned and unpartitioned space appears. Those areas that have been formatted with a file system and assigned a drive letter appear as partitions. Disks that have not been formatted and assigned a drive letter appear as unpartitioned space. Choose the partition where you want to install the Windows Server 2003.

4. Choose whether to format the partition or the unpartitioned space selected in the previous step. You can keep the existing partition, if one exists, or format it. If you format an existing partition, you will lose any data that exists on that drive.

5. After formatting occurs, Setup takes several minutes to copy files from the distribution media to the installation partition and prepare to start Windows for the first time.

6. After Windows starts, you will see the Regional and Language Options page where you can change the default regional and language settings. Click Next.

7. Enter your name and organization. Click Next.

8. Enter the product key that appears on the Windows Small Business Server 2003 distribution media. Click Next.

9. Type a name that is unique on the network where the Small Business Server computer will be identified. Type and confirm a password for the local administrator. Click Next.

   Note   Microsoft recommends that you create a password complex enough to meet the criteria for strong passwords. If the password you choose does not meet the criteria for a strong password, you will be prompted to change it or confirm that you want to continue with the current password.

10. Make any changes that you want to the date and time settings. Click Next.

11. Once Setup completes, the computer will restart. Log on using the Administrator logon and password. You can make adjustments to the screen resolution and color depth settings before continuing. The Setup Wizard begins automatically. On the Continuing Microsoft Windows Small Business Server Setup page, click Next.

Continue Windows Small Business Server 2003 installation

1. If there are conditions you should be aware of before continuing Setup, you will receive the Setup Requirements page. For example, if your server does not meet hardware requirements of Windows Small Business Server 2003, the requirements that have not been met are listed. You can review the missing requirements and get more information about them. If the unmet requirements prevent you from proceeding, you will not be able to continue with the setup. If a missing requirement is a warning or is informational, you can stop Setup at this point and change the hardware to meet the requirements, or you can continue with the setup. If the missed requirement is a warning, this condition may cause problems with your installation of Windows Small Business Server 2003. When you are finished reviewing the Setup Requirements page, click Next.

2. On the Company Information page, enter common information about your company once. It will be used multiple times without reentering the information. Completing the information on this page is optional. Click Next to continue.

Configure network settings

1. Make sure that the network adapter that you want to connect to the local network is connected to a hub or switch and has power.

2. On the Internal Domain Information page, specify the full DNS name, the NetBIOS domain name, and the computer name of the Small Business Server. Microsoft recommends using the extension .local as a DNS extension, so the full DNS name could be CRM.local with the domain named CRM. The computer name defaults to the name you entered during Windows setup. You can change it at this time. Click Next to continue.

   Note   After you install Windows Small Business Server 2003, you will not be able to change the full DNS name for the internal domain, the domain name, or the computer name. To change any of these settings requires that you reinstall it.  

3. If you have more than one network adapter installed, choose the adapter for the local facing network on the Local Network Adapter Information page. This is the adapter that connects to the hub or switch from which all the other client computers on the network can be accessed. Click Next to continue.

   Note   Network adapters other than the one you choose to connect to the local network will be disabled by Small Business Server. You can enable them after Setup completes.

4. On the Local Network Adapter Configuration page, you can change the IP address and subnet mask of the network adapter that connects to the local network from the default values. In a single network adapter configuration, specify an IP address on the same subnet as the default gateway; this can be a DSL model, cable modem, or other hardware device. Click Next.

5. On the Login Information page, you can choose to log on automatically after the server reboots. Setup then completes the component installation. Alternatively, you can choose to log on again manually after the server reboot.

6. Before continuing with the Windows configuration steps, close all other programs. Click Next.

7. The setup automatically continues again with the next stage of the Windows configuration. You can track the progress of each step during the configuration. When the first stage of the Windows configuration is finished, the Small Business Server computer will automatically restart.

Select components

1. On the Component Selection page, accept the default selection to include all components in the installation. You can change the partitions where they will be installed, if necessary. Click Next.

2. On the Data Folders page, choose the location where data will be stored for each application. Click Next.

3. Review the choices on the Component Summary page. Click Next to continue.

   Note   As the components are installed, you can track the progress on the Component Progress page.

4. If you are using CDs as the installation media for Windows Small Business Server 2003, you will be prompted to insert Windows Small Business Server 2003 CD 2, CD 3, and the Microsoft Office Outlook® 2003 CD, depending on the components you selected to install. Setup may resume automatically or you may need to click OK in the dialog box to accept the path to the distribution media.

5. If the Component Messages page appears, you have received error or warning messages about the installation status of the various components you chose. If you want to refer to the instructions accompanying the messages later, copy the message to the clipboard and paste it into Notepad so that it can be saved as a file. Click Next.

6. On the Finishing Your Installation page, click Finish. The Small Business Server computer will restart.

Review the To Do List

1. Log on again as the domain administrator. Setup will automatically start again. After some components are loaded, you will see the To Do List appear. We recommend that you go over these items in the order presented. If you intend to connect the server to the Internet, follow the recommendations and security considerations before doing so.

2. Once you have completed the items on the To Do List, continue with the prerequisites for Microsoft CRM installation.

Securing the Cache Against Pollution

Securing the cache against pollution prevents spoofed DNS records from polluting the cache. Unlike the external DNS, this is an additional security feature rather than a major requirement. You perform the following procedure on the Windows Small Business Server 2003 computer.

Secure the DNS cache against pollution

1. Log on to the Windows Small Business Server 2003 computer using an account that is a member of the Domain Administrators group.

2. On the Start menu, point to All Programs, point to Administrative Tools, and then click DNS.

3. In the DNS console, right-click the local Small Business Server 2003 computer, and then click Properties.

4. Select the Advanced tab, verify that the Secure cache against pollution check box is selected, and then click OK.

Configuring External DNS for the SMTP Virtual Server

An external DNS server needs to be configured so that the SMTP server refers to the Internet DNS when attempting to deliver e-mail to other domains. This is done by enabling the SMTP server to use the external DNS resolving servers. The SMTP virtual server within Exchange Server 2003 should be set to an external DNS server.

Configure the external DNS for the SMTP Virtual Server

1. On the Start menu, point to All Programs, click Microsoft Exchange, and then click System Manager.

2. Expand Servers, expand the local Small Business Server 2003 computer, expand Protocols, and expand SMTP.

3. Right-click Default SMTP Virtual Server and then click Properties.

4. Click the Delivery tab, and then click Advanced.

5. Click Configure, and add the IP address for the external DNS server.

6. Click OK, and then click OK again to close the dialog box.

Installing SQL Server 2000

Before you install Microsoft CRM Server, you need to install SQL Server 2000. Review your server installations and note the following:

• Only the Standard Edition of SQL Server 2000 can be installed on Windows Small Business Server 2003. The Enterprise Edition cannot be installed on it. Microsoft CRM does not support the Personal Edition of SQL Server 2000 or Microsoft SQL Server 2000 Desktop Engine (MSDE) as a database server for the Microsoft CRM server.

• Service Pack 3a or later must be installed.

• Microsoft CRM Server is supported only with a default instance of SQL Server. Named instances of SQL Server are not supported with Microsoft CRM.

• SQL Server can be installed using either Windows authentication or Mixed Mode authentication. Windows authentication is recommended for the increased security and Microsoft CRM uses only Windows authentication.

• If you do install using Mixed Mode authentication, be sure to set a strong password for the SA account, because this account often has administrative rights over the system, depending on how the service account is installed.

• The service account that SQL Server uses to log on to the network must either be a local system account or a domain administrator account until the installation of Microsoft CRM is finished. After Microsoft CRM installation is complete, a domain user account without administrator privileges may be used as the SQL Server service account for added security.

• The SQL Server service must be started. This service can be configured to automatically start when the computer is started.

• SQL Server Agent must be started. This service can be configured to automatically start when the computer is started.

• Although it is not mandatory, it is suggested that you accept the SQL Server default settings for Collation Designator, Sort Order, and SQL Collation. Microsoft CRM supports both case-sensitive and case-insensitive sort orders.

• Microsoft CRM Setup requires at least the Named Pipes network library to authenticate using SQL Server. Both Named Pipes and TCP/IP network libraries are enabled by default when you install SQL Server 2000.

• If you are using an existing installation of SQL Server and the computer name has been changed since SQL Server was installed, you need to change the computer name in SQL Server to the actual computer name. See the stored procedures sp_helpserver, sp_dropserver, and sp_addserver in "Windows Server System Online Books for SQL Server 2000" at msdn.microsoft.com/library/default.asp?url=/servers/books/sqlserver/default.asp.

Install SQL Server

1. Log on to the Small Business Server computer using an account that is a member of the Domain Administrators group.

2. Insert the SQL Server 2000 CD. The CD will start (double-click Autorun.exe if autorun is disabled) and display the Microsoft SQL Server 2000 opening page.

3. Select SQL Server 2000 Components.

4. In the Microsoft SQL Server 2000 Install Components dialog box, select Install Database Server to begin the database installation.

5. A warning message appears indicating that SQL Server 2000 SP2 and earlier is not supported by this version of Windows. Click Continue to proceed with the installation. You install Service Pack 3a or later following this initial installation.

6. On the Welcome to the Microsoft SQL Server Installation Wizard page, click Next.

7. On the Computer Name page, ensure that Local Computer is selected. The computer name will be displayed and appears dimmed. Ensure that the computer name is correct and then click Next.

8. On the Installation Selection page, ensure that Create a new instance of SQL Server or Install Client Tools is selected, and then click Next.

9. On the User Information page, type information for Name and Company, and then click Next.

10. Read the Software License Agreement. Click Yes to accept the agreement and continue.

11. The next page may ask for a product key - if so, enter the key located on the CD case, and then click Next.

12. On the Installation Definition page, select Server and Client Tools, and then click Next.

13. On the Instance Name page, ensure that Default is selected, and then click Next. A named instance of SQL Server is not supported with Microsoft CRM Server.

14. On the Setup Type page, click Typical. Under Destination Folder, in the Program Files location in <drive>:\Program Files\Microsoft SQL Server, edit the drive letter as appropriate for your server.

15. To set the Data Files location to <drive>:\Program Files\Microsoft SQL Server, click Browse, edit the drive letter as appropriate for your server, and then click OK.

    Important    We recommend that SQL Server data files are stored on a separate partition than the principal Small Business Server files (see the "Use Multiple Partitions" topic in the previous "Planning Your Deployment" section). For the greatest degree of disk fault tolerance, this separate partition should be located on separate physical disks from the principal Small Business Server partition. This configuration is required to use the Full Recovery model for your Microsoft CRM databases on SQL Server. If the disk where the SQL Server files are located fails, the Full Recovery model gives the highest probability of recovering to a more recent data modification than using the Simple Recovery model. For better performance, store the data files on a high-performance disk partition that uses the RAID specification. Specify a separate drive for the data files location in Setup. When the Microsoft CRM Server Setup program creates the Microsoft CRM databases, the files will be created in this default data directory unless you are using a three or four partition solution where the databases will need to be created prior running Microsoft CRM Server Setup.

16. Review Available to confirm that there is sufficient disk space on each drive before continuing, and then click Next.

17. Accept the default configuration settings until the Services Accounts page appears, and then select Use the Local system account or specify an account that is a domain administrator.

    Note   Microsoft CRM Server Setup will fail if the local administrator account is used as the SQL Server service account. We recommend that after the installation of Microsoft CRM is complete, you change the SQL Server service account to a domain user who is a not a domain administrator. User SQL Server Enterprise Manager to change the service account.

18. On the Authentication Mode page, ensure that Windows Authentication Mode is selected, and then click Next.

19. On the Start Copying Files page, click Next to begin the installation. The installation requires several minutes to complete depending on the system configuration.

    Note   You may also be prompted for the licensing mode for your copy of SQL Server.

20. The Setup Complete page indicates a successful installation of SQL Server.

21. Click Finish to exit the Setup program.

Configure SQL Server Agent service

1. From the server where SQL Server is installed (CRMSQL01), on the Start menu, point to All Programs, point to Microsoft SQL Server, and then click Service Manager.

2. In the Services drop-down list, select SQL Server Agent.

3. Select the Auto-start service when OS starts check box.

4. Click Start/Continue to start the SQL Server Agent.

5. Close SQL Server Service Manager.

Installing the Latest SQL Server 2000 Service Pack

After you install SQL Server 2000, you must apply the latest service pack before installing Microsoft CRM. Install SQL Server Service Pack 3a or later using the following procedure.

Install the latest SQL Server 2000 Service Pack

1. Log on to the Small Business Server computer using an account that is a member of the Domain Administrators group.

2. Insert the service pack media and double-click Setup.bat.

3. On the Welcome page, click Next.

4. Read the Software License Agreement. Click Yes to accept the agreement and continue.

5. On the Instance Name page, ensure that Default is selected, and then click Next.

6. On the Connect to Server page, ensure that the Windows account information I use to log on to my computer with (Windows authentication) option is selected, and then click Next.

7. On the SQL Server 2000 Service Pack Setup page, click Continue.

8. If your SA password is set to blank, whether you have mixed authentication enabled or not, you will receive a warning message that a blank SA password is a security threat. We recommend that you use a strong password for the SA account. Click OK to continue.

9. You may see a Backward Compatibility Checklist page, with the option to enable cross-database ownership chaining available, but not selected. We recommend that you do not select this option. Click Continue.

10. On the Error Reporting page, you can choose to send fatal error reports to Microsoft by selecting Automatically send fatal error reports to Microsoft. Click OK.

11. On the Start Copying Files page, click Next.

12. When the service pack installation finishes, you may see an informational message indicating that the master and msdb databases should be backed up. We recommend backing up these two databases as part of an overall backup strategy and whenever service packs or updates are installed.

13. The Setup Complete page indicates a successful installation of the service pack. Click Finish.

Installing Microsoft CRM

The following items are important for installing Microsoft CRM 1.2 on Microsoft Windows Small Business Server 2003:

• Obtain a license key, which is required during installation, from:

   https://mbs.microsoft.com/mbsregistration/chooserelationship.aspx

• For the most up-to-date information about installing Microsoft CRM, refer to the Readme located on the Microsoft CRM Server CD and on the Documentation CD.

• If you are installing Microsoft CRM using Terminal Services, you must install from a local drive or a shared drive, but not a mapped drive. Running Microsoft CRM Setup from a mapped drive on a remote computer using a Terminal Services session (Remote Desktop Session) fails.

• You must be logged on with Domain Administrator privileges on the Small Business Server computer when running Microsoft CRM Setup.

• During Microsoft CRM setup, you must use a Web site that refers to a local folder location in the Path field on the Home Directory of the IIS console. During Microsoft CRM setup, if you specify a Web site that uses a "home" network shared folder on another server, Microsoft CRM Setup fails with any of the following errors:

  "Error 1327. Invalid Drive: H:\"

  "Installation failed prematurely..."

  "Failed to install Microsoft CRM Server."

  "Failed to Install MSI part of Microsoft CRM Server Setup."

  "Unspecified error"

  "(80004005)"

Before you install Microsoft CRM, review your server installations and note the following:

• Windows Server components and services:

  • Internet Information Services (IIS) must be installed and the services started.

  • Windows Indexing Service must be started on the installation computer.

  • Microsoft Message Queuing Service must be installed as a Message Queuing Server and started.

  • Active Directory® must be in native mode.

• Microsoft XML Core Services (MSXML) 4.0 must be installed.

• The SQL Server service and SQL Server Agent must be started on the SQL Server computer.

Installation Prerequisites

Install prerequisite services - Internet Information Services

Internet Information Services (IIS) is installed by default on Windows Small Business Server 2003. You can ensure that IIS has started successfully by following these steps.

1. On the Start menu, click Administrative Tools, and then click Server Management.

2. Expand Advanced Management.

3. Expand Internet Information Services.

4. Click the local computer. In the details pane, you should see "Service is running" next to the Web Sites folder.

Install prerequisite services -Message Queuing

Message Queuing is not installed by default on Windows Small Business Server 2003. You need to install it from the Windows Components Wizard. 

1. On the Start menu, click Control Panel, and then double-click Add/Remove Programs.

2. Click Add/Remove Windows Components.

3. Select the Application Server check box, and click Details.

4. In the Application Server dialog box, select the Message Queuing check box.

5. When Message Queuing is highlighted, click Details.

6. In the Message Queuing dialog box, clear the Active Directory Integration check box. Click OK.

7. In the Application Server dialog box, click OK.

8. Click Next. 

9. Complete the installation.

Install prerequisite service - Indexing Service

The Indexing Service is not installed by default on Windows Small Business Server 2003. You need to install it from the Windows Components Wizard. 

1. On the Start menu, click Control Panel, and then double-click Add/Remove Programs.

2. Click Add/Remove Windows Components.

3. Select the Indexing Service check box, and then click Next.

4. Complete the installation.

Install prerequisite service - MSXML

1. In Windows Explorer, locate the Microsoft CRM Server distribution media. Double-click the MSXML directory.

2. Double-click MSXML.MSI to run the installation program.

3. Complete the installation.

Installing and Configuring Microsoft CRM

Create a Web site

For Microsoft CRM, we recommend that the Web functions of the Microsoft CRM server are not installed at the default Web site.  These steps create a new Web site that can be used to install the Microsoft CRM Web components.

1. On the Start menu, point to Administrative Tools and click Server Management.

2. Expand Advanced Management, and expand Internet Information Services.

3. Right-click the Web Sites folder, point to New, and then click Web Site. 

4. On the Welcome page, click Next.

5. Give the Web site a description, and then click Next.

6. From the Enter the IP address to use for this Web site drop-down list, select the IP address of the Microsoft CRM server and click Next.

   Important   If there is more than one Web site in use (such as Default Website, Microsoft CRM, and Small Business Server Manager), the Microsoft CRM Web site must have an IP address associated with it. Do not use All Unassigned IPs for the Microsoft CRM Web site. The IP address used should be the same as the server IP address.

7. On the Web Site Home Directory page, click Browse to browse to a location where the site will reside. For example, use C:\Inetpub\CRM for the location. Choose Make New Folder to create the Microsoft CRM folder. We recommend that the Web site be installed on a non-system partition, that is, one that doesn't contain the Windows operating system installation.

8. Click OK to close the Browse For Folder dialog box.

9. Clear the Allow anonymous access to this Web site check box and click Next.

10. Click Next and then click Finish.

Install Microsoft CRM

Important   Do not install Microsoft CRM Sales for Outlook (the Outlook client) on the Windows Small Business Server 2003 computer. It is not compatible with the Microsoft CRM Server installation.

1. Meet all requirements in the previous "Prerequisites" section.

2. Log on to the server as a user with Domain Administrator privileges.

3. Insert the Microsoft CRM Server CD into your CD-ROM drive. The autorun screen should appear.

4. Select Install Microsoft CRM Server from the opening screen.

5. On the License Agreement page, click I accept the license agreement, and click Next.

6. On the Enter License Number page, do the following:

7. Type < your_organization_name > for Organization Name. If you are doing a test or lab deployment and are planning to use the Microsoft CRM Sample Database, enter Adventure Works Cycle for the organization name.

   Note   If you are planning to use the Microsoft CRM Sample Database, see Chapter 21, "The Sample Database," for more information.

8. Type your license number in the License Number box, and click Add. If you have more than one license number, type each one and click Add. They will be displayed in the list box. Obtain a license key from:

    https://mbs.microsoft.com/mbsregistration/chooserelationship.aspx

   Note   Microsoft CRM cannot use two different license keys for the same license type. For example, if you have a license key for 10 users for Microsoft CRM Standard Server, you cannot add another Standard Server license key for 10 additional users.

9. Click Next.

10. On the Install Required Components page, select Install listed components, and click Next. This page appears only if you do not have Microsoft XML Core Services 4.0, the Microsoft .NET Framework 1.1, or the Windows 2000 Hotfix Q320211 installed.

    Note   These components are required before Microsoft CRM can be installed. You can exit Setup and install the components manually, or select Install listed components. The Next button on this page is disabled until Setup either detects these components are installed or the Install listed components check box is selected.

11. On the Select SQL Server page, select the SQL Server Standard edition default instance on the local Small Business Server computer. Select Create new databases or Connect to an existing database, and click Next.

12. On the Set Up Organization page, accept the default values and click Next. 

13. On the Select Installation Locations page, select the Web site and file installation locations. On a new server (one that has not had a previous Microsoft CRM Web site configured) choose the Web site that was created previously.

14. On the Specify Security Account page, select the security account for your Microsoft CRM installation, Crystal Enterprise, and ASP.NET. If you choose Domain User Account, enter the logon name and password for this account, and then click Next.

    Note   If you choose to install using a Domain User Account, and depending on the password policies you have implemented for your organization, the password for the user may expire. The user will need to change the password for Microsoft CRM services to be the same as his or her logon password.

    Note   If you choose to install using Local System as the security account for ASP.NET, all Web sites running under this instance of IIS using ASP.NET will be affected.

15. Review the Summary page, click Back to correct any errors; when you are ready to proceed, click Install.

16. A message box will be displayed indicating a successful install. Click OK.

17. Restart the computer.

Adding Microsoft CRM Accounts to the Pre-Windows 2000 Compatible Access Group

For the Microsoft CRM server to access the Active Directory organizational units (OUs) where users are located, you add the following accounts to the Pre-Windows 2000 Compatible Access group in Active Directory:

• Microsoft CRM Service Account (usually a local computer account)

• IIS Service Account on the Windows Small Business Server 2003 computer server (a local computer account by default)

• SQL Server Service Account (computer account if running as local system)

This procedure should be followed for all the domains in your organization.

Add accounts to the Pre-Windows 2000 Compatible Access group

1. On the Windows Small Business Server 2003 computer, on the Start menu, point to All Programs, point to Administrative Tools, and click Active Directory Users and Computers.

2. Expand the domain, and click Builtin to expose the objects in the Builtin folder in the details pane. Right-click Pre-Windows 2000 Compatible Access, and click Properties.

3. Click the Members tab, and then click Add.

4. To find the Small Business Server computer, in the Select Users, Contacts, Computers or Groups dialog box, click Object Types and make sure Computers is selected. Click Advanced and Find Now. A list appears of computers and other objects of the types you selected.

5. If IIS, SQL Server, or Microsoft CRM Server is running under the local system account, add the local Small Business Server computer. If any of these services are running under a domain user account, add that domain user account.

6. Click OK.

Changing the Crystal Enterprise Administrator Password

Crystal Enterprise is automatically installed during the Microsoft CRM Server installation. During the Crystal Enterprise portion of the installation, a Crystal Enterprise user is created (Administrator) who has full permissions to Crystal Enterprise with a blank password. This configuration is necessary for Crystal Enterprise to complete installation correctly. However, it is a good practice for you to replace the blank password with one that is more secure. See Chapter 11, "Planning the Security of Your Microsoft CRM System," for suggestions on creating secure passwords.

Note   The default Crystal Enterprise Administrator account is used to open reports in Crystal Reports and to save customized reports back to Crystal Enterprise. The Crystal Enterprise administrator account is not a domain user and is not subject to domain password and security policies. We recommend that you use a strong password for this account and change it often. Individuals in your organization who are designing reports will need to know the new administrator password. Good password security should be practiced at all levels of your Microsoft CRM deployment.

The program CrystalAdmin.exe is provided to change the password for the Crystal Enterprise Administrator user account.

Run CrystalAdmin.exe

1. On the Small Business Server computer, open Windows Explorer and navigate to the following folder:

   <InstallationRoot>\Program Files\Microsoft CRM\Tools

2. In the file list for this folder, double-click Microsoft.Crm.Tools.CrystalAdmin.exe.

3. The default value for the Website Port is 80. If this is not correct for your installation, enter the correct port number.

4. Leave the Old Password box blank, and type a new password in the New Password box.

5. Type the new password again in the Repeat New Password box, and click OK.

Changing Crystal Enterprise Page Server View Limit

Crystal Enterprise Page Server has a view-on-demand limit of 20,000 records. If you view an on-demand report containing more than 20,000 records, an error message appears indicating the report contains too many database records. The following procedure will change the default value in Crystal Enterprise Page Server so that more than 20,000 records can be viewed without an error message.

Run Crystal Configuration Manager

1. On the Small Business Server computer, on the Start menu, point to All Programs, point to Crystal Enterprise 9, and click Crystal Configuration Manager.

2. Right-click Crystal Page Server, and click Stop.

3. Right-click Crystal Page Server (again), and click Properties.

4. In the Command box, go to the end of the commands and type -maxDBResultRecords 0, and click OK.

5. Right-click Crystal Page Server (again) and click Start.

6. Exit Crystal Configuration Manager.

Adding a License Key

Add a License Key

1. On the Small Business Server computer, on the Start menu, point to All Programs, point to Microsoft CRM, and then click Deployment Manager.

2. In the tree view, click License Manager, right-click the organization name, point to New, and then click License.

3. Type your license key in the Add License dialog box, and click Next.

   Note   Microsoft CRM cannot use two different license keys for the same license type. For example, if you have a license key for 10 users for Microsoft CRM Standard Server, you cannot add another Standard Server license key for 10 additional users.

   Note   Refer to the "License Keys" section of the Readme in the root directory of the Microsoft CRM Server distribution media for license keys to be used with test or lab deployments. There are different license keys for an upgrade from Microsoft CRM 1.0 or a clean installation of Microsoft CRM 1.2.

4. Click Finish.

Installing the Microsoft CRM-Exchange E-Mail Router

The Microsoft CRM-Exchange E-mail Router (the Router) is a software component that provides an interface between the Microsoft CRM system and Microsoft Exchange 2000 Server and Microsoft Exchange Server 2003. When installed on the same computer as Exchange 2000 or Exchange 2003, the Router transfers e-mail to the Microsoft CRM system.

The Microsoft CRM system stores e-mail as activity records. These e-mail activity records are stored in the Microsoft CRM database and not only include the contents of the e-mail message (that is, the text of the message, its subject line, and so forth), but also relevant associations with other Microsoft CRM records. For example, when a salesperson replies to a customer about a case, he or she creates an e-mail activity record that includes the text of the message plus information associating the e-mail activity record with the appropriate case record.

Prerequisite Checklist

Regardless of the computer configuration, the following is a checklist of prerequisite software and configuration items that must be installed before installing the Router on Small Business Server computer:

• Microsoft Internet Explorer 6.0 SP1 or later.

• Microsoft CRM Server must be installed and operational.

• Microsoft Exchange Server 2003 must be installed and operational on the computer where the Router will be installed.

• The user installing the Router must be a member of the Domain Administrator group.

• It is required that you log on to the computer where the Router is to be installed as a user that has local administrative privileges on the computer running Microsoft CRM.

Install Microsoft CRM-Exchange E-Mail Router

The following procedure installs and configures the Router on the Windows Small Business Server 2003 computer.

For the most up-to-date information about installing Microsoft CRM, refer to the Readme located on the Microsoft CRM Server CD or the Microsoft CRM Documentation CD.

Install Microsoft CRM-Exchange E-Mail Router

1. Meet all requirements in the previous "Prerequisite Checklist" section.

2. Log on to the Small Business Server computer as a user with Domain Administrator privileges.

3. Insert the Microsoft CRM Server CD into your CD-ROM drive. The autorun screen should appear.

4. Select Install Microsoft CRM-Exchange E-mail Router from the opening screen.

5. On the License Agreement page, click I accept the license agreement, and click Next.

6. On the Specify Microsoft Business Solutions CRM Server page, click Configure. This page will configure the Router to connect to a Microsoft CRM server.

7. On the Configure Servers page, click Add.

8. On the Add Server page, in the Microsoft CRM Server Name box, type the name of the Small Business Server computer. In the Microsoft CRM Web site URL box, type the URL of the Microsoft CRM Web site you created on the Small Business Server computer.

9. Click OK to return to the Configure Servers page, click OK again to return to the Specify Microsoft CRM Server page, and then click Next.

10. On the Specify Security Account page, type the logon name and password.

11. On the Select Installation Locations page, select the Microsoft CRM Web Site and file installation directory, and then click Next. 

12. On the Ready to Install page, click Install.

13. A message box will be displayed indicating a successful install. Click OK.

Configuring Users and Queues

Before adding a user to Microsoft CRM, the Domain Users group must be given access to the Microsoft CRM databases.

Add domain users to SQL Server

1. On the Small Business Server computer, on the Start menu, point to All Programs, point to Microsoft SQL Server, and then click Enterprise Manager.

2. Expand Microsoft SQL Servers, expand SQL Server Group, expand the Small Business Server SQL_Server, and expand Security.

3. Right-click Logins, and then click New Login.

4. Click the ellipsis button (...), select Domain Users, click Add, and then click OK.

5. In the Properties dialog box for the Domain Users login, click the Database Access tab.

6. Select the Permit check box for the Organization_ MSCRM and Organization_ METABASE databases, and leave the default role of public.

7. Click OK to close the SQL Server Login Properties dialog box.

Add a User to Microsoft CRM

Before adding a user to Microsoft CRM, you must first add the user to Active Directory. When adding users, you must also have an Exchange Server 2003 mailbox created for them. To have the user created with an Exchange 2003 mailbox, run the Active Directory Users and Computers utility on the Small Business Server computer.

Add a user to Active Directory

1. Log on to the Small Business Server computer using an account that is a member of the Domain Administrators group.

2. On the Start menu, point to All Programs, point to Microsoft Exchange, and then click Active Directory Users and Computers.

3. In the console tree, double-click the domain node or the OU where user accounts are located. (This may vary depending on your forest and domain structure. The default location is the User OU.)

4. In the details pane, right-click the container where you want to add the user, point to New, and then click User.

5. In First name, type the user's first name.

6. In Initials, type the user's initials.

7. In Last name, type the user's last name.

8. Modify the full name as necessary.

9. In User logon name, type the name that the user will use to log on. From the drop-down list, click the UPN suffix that must be appended to the user logon name (following the at sign, @). Click Next.

10. In Password and Confirm password, type the user's password, and then click Next.

11. Verify that the Create an Exchange mailbox check box is selected, and then click Next.

12. Click Finish.

Follow these procedures for configuring users to use the Router for unsolicited e-mail.

Note   Using the Router for unsolicited e-mail is optional.

Note   The following procedure is necessary only if the user is either a queue user or wants to have all e-mail that is sent to the user created as e-mail activity records in Microsoft CRM.

Note   The Active Directory user account that was used to install the Microsoft CRM product is the only account that will have access to Deployment Manager at first. You need to add other users as necessary to the product.

Configure users

1. Log on to the Small Business Server computer as a user with Domain Administrator privileges.

2. On the Start menu, point to All Programs, point to Microsoft Exchange, and then click Active Directory Users and Computers.

3. Click View, and then click Advanced Features to enable viewing advanced feature property sheets.

4. In the console tree, click Users, right-click a user in the details pane, and then click Properties.

5. Click the Exchange Advanced tab and click Custom Attributes.

6. Select the first available extensionAttribute. (On a new installation, the first one should be available, however any extension attribute may be used.) Click Edit.

7. Type CRMEmailEnabled, and click OK.

8. Click OK to close the Exchange Custom Attributes dialog box, and then click OK to close the user Properties dialog box.

There are two ways to add users to your Microsoft CRM server deployment:

• User Manager Wizard

• Manually using the Microsoft CRM Web application

User Manager is part of Deployment Manager. User Manager can create user records in Microsoft CRM once those users exist in Active Directory. The benefit of User Manager is that you can create multiple user records at one time. User Manager creates user records through the User Manager Wizard.

Note   When you are using the sample database, add users through the Sample Database Wizard described later in this chapter.

Add a user to Microsoft CRM using the User Manager Wizard

1. On the Small Business Server computer, on the Start menu, point to All Programs, point to Microsoft CRM, and then click Deployment Manager.

2. Use the Deployment Manager Help, located on the Help menu, for the procedures to add users by using the User Manager Wizard.

Manually add a user to Microsoft CRM

1. On the Small Business Server computer, start Internet Explorer and in the browser address box, type http://localhost to open Microsoft CRM.

2. On the Home page, click Settings, click Business Unit Settings, and then click Users.

3. Click New User.

4. In the user form, type the first and last names in the appropriate boxes.

5. In the Domain Logon Name box, type the user domain and logon name using the domainname\username format. This name must be exactly the same as the user logon name you provided when you created the Active Directory user record.

6. Click Save.

7. Click the Licenses side tab, and then click Manage Licenses.

8. Select a license in the left column and click the button to move it to the right column, and then click OK.

9. Click the Roles side tab, click Manage Roles and select the check boxes for the roles you want to apply, and then click OK.

10. On the Home page, click Settings, click Business Unit Settings, and then click Users.

11. Click a user and select the General tab.

12. In the Primary E-mail box, type the complete e-mail address of this user, and click Save.

13. Repeat this procedure for each Microsoft CRM user.

Create and configure a queue user

This procedure provides the steps for creating and configuring a queue user that can receive incoming e-mail (for example, the e-mail address may be support@adventure-works.com).

1. Log on to the Small Business Server computer using an account that is a member of the Domain Administrators group.

2. On the Start menu, point to All Programs, point to Microsoft Exchange, and then click Active Directory Users and Computers.

3. Click View, and then click Advanced Features to enable viewing advanced features property sheets.

4. In the console tree, double-click the domain node.

5. In the details pane, right-click the container where you want to add the user, point to New, and then click User.

6. In First name, type the queue name (for example, support).

7. In User logon name, type the name that the user will log on with (support) and, from the drop-down list, click the UPN suffix that must be appended to the user logon name (following the at sign, @). Click Next.

8. In Password and Confirm password, type the user's password, select Account is disabled, and then click Next.

9. Verify that the Create an Exchange mailbox check box is selected, and then click Next.

10. Click Finish.

11. In the console tree, double-click the container in which you created the queue user.

12. Right-click the queue user in the details pane and click Properties.

13. On the Exchange Advanced properties tab of the disabled user object that owns the mailbox, click Mailbox Rights, and then search the list of accounts for one that has the Associated External Account permission.

    Note   By default, no account will have the Associated External Account permission; however, depending on how the account was created, it may already have this permission set. If another account currently has this permission, remove the Associated External Account permission from that account. Only one account at a time can have the Associated External Account permission. To reset the permission, you must first remove this permission.

14. If no account has this permission, grant the Associated External Account permission to the SELF account, and verify that Full Mailbox Access permission has been allowed.

15. Click OK to close the Mailbox Rights dialog box.

    Note   After the Exchange 2003 DSAccess cache is refreshed, the new configurations take effect and e-mail messages sent to the disabled account will not generate errors.

16. Click the Exchange Advanced tab and then click Custom Attributes.

17. Select the first available extensionAttribute. (On a new installation, the first one should be available.) Click Edit.

18. Type CRMEmailEnabled, and click OK. Click OK to close the Exchange Custom Attributes dialog box, and then click OK again to close the user Properties dialog box.

    Note   Ensure that this account is a disabled account. If this account is not a disabled account, the Microsoft CRM queue functionality will not work properly.

Add a queue user to the Microsoft CRM server

1. On the Small Business Server computer, start Internet Explorer and in the browser address box, type http://localhost to open Microsoft CRM.

2. On the Home page, click Settings, click Business Unit Settings, and then click Queues.

3. Click New Queue.

4. Enter the Queue Name (for example, Support), the Business Unit, the Owner, and the E-mail (for example, support@adventure-works.com).

Backing up Windows Small Business Server 2003

Microsoft Windows Small Business Server 2003 has the ability to back up files as a task that runs automatically according to a specified schedule. You can back files up to a hard drive or tape drive. You can specify the time to retain deleted e-mail messages, and how much space to allocate for backups of deleted files. You can also specify which files or folders should be excluded from the backup as long as the folder you intend to exclude is not required for a restore, or a parent of the folder to be excluded is not required for a restore.

The Windows Small Business Server 2003 Backup solution backs up all the files on the selected volumes of the Small Business Server computer. SQL Server database files will not automatically be included with the backup if the SQL Server service is running. SQL Server database files are locked for exclusive use by SQL Server when the SQL Server service is running. To ensure that your Small Business Server computer and SQL Server are backed up in a timely, coordinated way, choose a SQL Server backup plan, implement it, and then create a Small Business Server backup plan that works with the SQL Server backup.

Choose a SQL Server Backup Plan

You can use one of the three SQL Server backup plans in addition to the Small Business Server Backup: Full Recovery model, Simple Recovery model, and stopping SQL Server before starting Small Business Server Backup.

Using the Full Recovery Model

Use the Full Recovery model (the default) for the Microsoft CRM SQL Server databases and as long as you have disks that can be partitioned into separate drives where you can store the database files for all the Microsoft CRM databases, plus the organization_name_ MSCRMDistribution database. Use the two or three partition design as outlined in "Use Multiple Partitions" in the "Planning Your Deployment" section earlier in this chapter. With the three partition design, one partition serves as the principal Small Business Server partition, the second contains the SQL Server data files for the Microsoft CRM databases, and the third contains the transaction log files for the Microsoft CRM databases. If you have only two partitions, use one as the principal Small Business Server partition and the other for containing all the SQL Server database files, both data and transaction logs. This lowers the degree of disk fault tolerance, and still allows you to use the Full Recovery model for your Microsoft CRM databases.

Important   If you use the three or four partition solution, you need to create the Microsoft CRM SQL Server databases before installing Microsoft CRM and specify in Microsoft CRM Server Setup that the databases already exist. See "Use Multiple Partitions" in the "Planning Your Deployment" section earlier in this chapter. If you are using a two partition solution, you need to specify the separate partition as the default location for SQL Server data files when you run SQL Server Setup.

The SQL Server databases will be backed up by SQL Server full database backups and transaction log backups using the Transact-SQL BACKUP command or the Database Maintenance Plan Wizard. These files will be stored on the principal Small Business Server partition being backed up by Small Business Server backup. This creates a backup of the backup. The additional partition(s) where the database files are located will be specifically excluded from the Small Business Server backup.

This is the preferred backup plan because it provides the ability to back up SQL Server using both database and transaction log backups independently of the Small Business Server backup. This optimizes the chance for retaining the largest amount of work if either the principal Small Business Server partition or one of the SQL Server file partitions fail. With the SQL Server backups stored on a separate disk from the SQL Server database files, if the principal Small Business Server partition fails, SQL Server database files remain up to date on one or more different drives so you perform only a Small Business Server restore. If one of the partitions containing the SQL Server database fails and the principal Small Business Server partition is still available, you can restore the most recent database and transaction log backups to restore the databases to the instant of the failure. Using the three or four partition solution with separate disks for data files and transaction log files, if the data file partition fails and the transaction log partition is still available, you can back up the damaged database and restore this file as the last backup in the set, giving you the ability to restore right up to the failure. With the Small Business Server Backup making copies of the SQL Server backup files, you have the SQL Server backups stored in a location that permits up to the moment restores from a catastrophic failure of the Small Business Server computer.

Using the Simple Recovery Model

Use the Simple Recovery model for the Microsoft CRM SQL Server databases if you do not have additional disks to be partitioned into separate drives for the SQL Server database files. The entire Small Business Server computer including the SQL Server database files are on a single partition. The Simple Recovery model permits full database backups only, transaction log backups are not allowed. Using this method you create scheduled jobs using the Transact-SQL BACKUP command or the Database Maintenance Plan Wizard to perform full database backups of the Microsoft CRM databases plus master, msdb, and  organization_name_ MSCRMDistribution. The full database backup files are stored on the same partition and are backed up by the Small Business Server Backup.

Using this method you can keep your SQL Server up and running 24 hours a day, but if a failure of the partition occurs, you have to restore your SQL Server databases from the most recent SQL Server database backup. If you are running the Small Business Server Backup only once a day, a day's worth of work could be lost.

Stopping SQL Server Before Starting Small Business Server Backup

Stop the SQL Server service (the MSSQLSERVER service) prior to starting the Small Business Server Backup. This is the easiest way to ensure SQL Server database files are backed up. With the SQL Server service stopped, the SQL Server database files can be included in the Small Business Server backup. After the Small Business Server Backup finishes, you need to start the SQL Server service, the SQL Server Agent (SQLSERVERAGENT) service, and the Crystal APS service, because these services automatically stop when SQL Server stops.

Although this method is simple and easy to implement, it also incurs down time of SQL Server while the backup is in progress, and risks loss of work performed between the last Small Business Server backup and a disk or server failure.

Implementing a SQL Server Backup Plan

Implement the Full Recovery model

To implement the Full Recovery model for backing up SQL Server databases while still using Small Business Server Backup, perform these steps before installing SQL Server and Microsoft CRM Server.

1. Choose whether to have one partition in addition to the principal Small Business Server partition that will contain both SQL Server data files and transaction log files; or two partitions in addition to the principal Small Business Server partition, one for data files and one for log files.

2. Create the partitions. Use a RAID specification if you have the appropriate disks and controller.

3. Create \MSSQL\DATA directories on the partition(s) you created separately for SQL Server data files.

4. Install SQL Server (see the previous "Installing SQL Server" section). For the data file location, specify the separate partition \MSSQL\DATA path you created.

5. If you are using separate partitions for SQL Server data and log files in addition to the principal Small Business Server partition, create the following databases and specify the separate partitions for data and log:

   OrganizationName _MSCRM

   OrganizationName _METABASE

   OrganizationName _CRMCRYSTAL

6. Install Microsoft CRM Server (see the "Installing Microsoft CRM Server" section earlier in this chapter). If you have already created the Microsoft CRM databases in SQL Server, specify that the databases already exist. Otherwise, have Microsoft CRM Setup create the databases for you.

7. Create a SQLBackup directory on the principal Small Business Server partition to store the database and log backups.

8. For each of the Microsoft CRM databases, plus the master, msdb, and  OrganizationName _MSCRMDistribution databases, use the Database Maintenance Plan Wizard in SQL Server Enterprise Manager to create a maintenance plan for a full database backup. Choose to back up only the full database in this plan, not the transaction logs; they will be backed up separately. For the backup destination, specify a tape drive if one is connected to the Small Business Server computer, or the SQLBackup directory on the principal Small Business Server partition. Schedule this maintenance plan to run often enough to minimize the number of backups that have to be restored. Typically, a full database backup occurs every day during hours of off-peak resource utilization on the Small Business Server.

9. For each of the Microsoft CRM databases, plus the OrganizationName _MSCRMDistribution database, use the Database Maintenance Plan Wizard in SQL Server Enterprise Manager to create a maintenance plan for transaction log backups. Choose to back up only the transaction logs in this plan, not the full database. For the backup destination, specify a tape drive if one is connected to the Small Business Server computer or the SQLBackup directory on the principal Small Business Server partition. Schedule the maintenance plan to run often enough to minimize data loss if a disk or server fails. Transaction log backups are incremental backups and do not consume significant system resources so they can be scheduled throughout the day. Typically, transaction log backups occur every hour.

10. Monitor the history of the database maintenance plans to ensure they are working correctly. Check the SQLBackup directory or the tape drive to ensure the backup files are being created.

11. Create a Small Business Server backup plan (see the "Configure Small Business Server Backups" section later in this chapter).

Implement the Simple Recovery model

To implement the Simple Recovery model for backing up SQL Server databases while still using Small Business Server Backup, perform these steps before installing SQL Server and Microsoft CRM Server.

1. Install SQL Server (see the "Installing SQL Server" section earlier in this chapter). Use the default data file directory.

2. Have the Microsoft CRM Server Setup program create the databases in SQL Server.

3. Create a SQLBackup directory on the principal Small Business Server partition to store the database and log backups.

4. For each of the Microsoft CRM databases, plus the master, msdb, and  OrganizationName _MSCRMDistribution databases, use the Database Maintenance Plan Wizard in SQL Server Enterprise Manager to create a maintenance plan for a full database backup. For the backup destination, specify a tape drive if one is connected to the Small Business Server computer, or use the SQLBackup directory. Because the Simple Recovery model does not perform transaction log backups, the databases should be backed up at least once a day to minimize data loss.

5. Monitor the history of the database maintenance plans to ensure they are working correctly. Check the SQLBackup directory or the tape drive to ensure the backup files are being created.

6. Create a Small Business Server backup plan (see the following "Configure SBS Backups" section). Schedule Small Business Server backups in a timely way to make sure the most recent database backups have been copied to the backup destination shortly after their completion.

Implementing the Stop SQL Server before Starting Small Business Server Backup plan

To implement the Stop SQL Server before Starting Small Business Server Backup plan of backing up SQL Server databases as part of a Small Business Server backup, perform these steps for modifying the Small Business Server backup job.

1. Create a Small Business Server backup plan (see the following "Configure Small Business Server Backups" section).

2. Create a batch file containing the following line:

   net stop mssqlserver /y

   This will stop the SQL Server service, the SQL Server Agent service, and the Crystal APS service.

3. Create a scheduled task to run the batch file. On the Start menu, point to Control Panel, Scheduled Tasks, and double-click Add Scheduled Task to open the Scheduled Task Wizard. Use this wizard to specify the batch file path and name.

4. Schedule the batch file to run a minute or two before the start of the Small Business Server backup scheduled task.

5. Create a second batch file with the following lines:

   net start mssqlserver
   net start sqlserveragent
   net start "crystal aps"

6. Use the Scheduled Task Wizard to create a scheduled task to run the second batch file. Schedule it to run at a time that gives the Small Business Server backup scheduled task plenty of time to complete.

Configure Small Business Server Backups

To configure Small Business Server backups, run the Small Business Server Backup Wizard from the Server Management utility.

Configure Small Business Server backups

1. On the Small Business Server computer, on the Start menu, point to Administrative Tools, and click Server Management.

2. From the Server Management utility, expand Basic Management, and select Backup. In the Manage Small Business Server Backup details pane, click the Configure Backup link. This opens the Backup Configuration Wizard.

3. On the Welcome page of the Backup Configuration Wizard, click Next.

4. On the Backup Location page, choose the location that is the destination of the backup. If the Backup to a Tape Drive selection is disabled, this means a tape drive is not connected to the computer or is not recognized by Windows.

   Note   If you specify a disk location, make sure that it is a separate physical disk from those used by Small Business Server, Microsoft CRM, and SQL Server. The only files on a volume specified as the Small Business Server backup destination should be the backed up files. If a disk failure occurs on one of the principal drives, a backup on a separate physical disk minimizes risk and improves the probability of recovering right up to the time of a failure.

5. On the Backup Data Summary page, view the drives and folders that will be backed up by Small Business Server Backup and those excluded from the backup. To exclude additional folders from the Small Business Server Backup, click the Exclude Folders button followed by Add Folder to specify the folder to be excluded. You can also remove the folders that are previously in the excluded folder list.

6. On the Define Backup Schedule page, choose the days and time that you want Small Business Server Backup to start. You can also choose the number of backups to be archived. Choose a time that coincides with the completion of the SQL Server full database backups if you have chosen the Simple Recovery model backup plan for the Microsoft CRM databases.

7. On the Storage Allocation for Deleted Files and E-mail page, choose whether or not to back up deleted files and e-mail messages; if you do, enter the number of days for retaining deleted files and e-mail messages.

8. If you check Enable periodic snapshots of users' shared folders, Small Business Server Backup will take automatic snapshots of shared folders on the Small Business Server computer at 7:00 A.M. and noon. Once a file in a shared directory has been backed up, a user may recover a deleted file or a previous version of the file. You can also change the maximum amount of space allocated for storing these snapshots. The default amount is 10 percent of the hard disk space on the volume specified for storing backups.

9. Click Finish to complete the backup configuration.

Configuring the Adventure Works Cycle Sample Database

Configure licenses

1. On the Windows Small Business Server 2003 computer, start Internet Explorer. In the browser address box, type http://localhost to open Microsoft CRM.

2. On the Home page, click Settings, click Business Unit Settings, and then click Users.

3. Double-click the user who will run the sample database.

4. Click the Licenses side tab, and verify that the user has a license. If not, click Manage Licenses in the upper right corner. In the Manage Licenses dialog box, select Microsoft CRM Suite Professional license in the left column and click the button to move it to the right column, and then click OK.

5. On the File menu, click Save and Close.

Run the Adventure Works Cycle Sample Data Import Wizard

1. On Microsoft CRM Server CD, navigate to <CD_ROM_Drive> :\sampledata and double-click Microsoft.Crm.SampleDataWizard.exe.

2. On the Welcome to the Sample Data Import Wizard page, click Next.

3. On the Specify Microsoft CRM Server URL page, accept the default and click Next.

4. On the Select Users page, add the five users for the sample deployment by clicking the ellipsis button (...) and selecting each user from the list. Assign each user a security role by clicking the ellipsis button (...) and selecting each role from the list. When you have entered all five users and assigned them different roles, click Next.

5. On the Ready to Import page, review the organization hierarchy and click Next. The Importing Sample Data page shows the data importing status.

6. On the Completing the Sample Data Import Wizard page, click Finish.

7. Log off and back on as one of the five users to see the data for that user.

Microsoft CRM Folders

For a table of the default folders created during Microsoft CRM installation, see Chapter 13, "Installing Microsoft CRM on Windows Server 2003."

Installing Microsoft CRM Using the Command Line

For information about installing Microsoft CRM from a command line, see Chapter 13, "Installing Microsoft CRM on Windows Server 2003."