Share via

Installing; Windows Server 2003

  • Article

The previous chapter of this guide has focused on installing Microsoft® Business Solutions CRM on Microsoft Windows® 2000 Server. In this chapter, a step-by-step guide is provided on installing all the components necessary for your Microsoft CRM deployment on Microsoft Windows Server™ 2003, according to the server architecture shown in the following figure

Basic Microsoft CRM Server Architecture

Basic Microsoft CRM Server Architecture

As you look at this figure, keep in mind that this is just one example of architecture to support Microsoft CRM. When you go through the planning stages for Microsoft CRM, you may determine that a different infrastructure is appropriate for your environment. The Outlook client is designed to be installed on a client computer running Microsoft XP Professional. In addition, it is recommended that it not be installed on the same computer as the Microsoft CRM Server.

Note You may want to print out this figure and refer to it as the various components are discussed in this chapter.

In this chapter, it is assumed that you are building an environment to support Microsoft CRM completely from scratch with no existing Windows 2000 Server or Windows Server 2003 infrastructure in place. In many cases, your environment will already have Windows 2000 Server or Windows Server 2003, or you will be migrating from Microsoft Windows NT® 4.0 to Windows 2000 Server or Windows Server 2003. However, even if much of your infrastructure is already in place, you should still read this chapter in its entirety, because it will help you to make sure that your current infrastructure meets the necessary prerequisites for a successful Microsoft CRM deployment. It will also provide you with the steps to build a meaningful test environment for Microsoft CRM

On This Page

Installing Microsoft Windows Server 2003 Installing Microsoft Windows Server 2003
Installing Windows Server 2003 on the Remaining Microsoft CRM System Servers Installing Windows Server 2003 on the Remaining Microsoft CRM System Servers
Installing Microsoft Exchange 2003 Installing Microsoft Exchange 2003
Installing SQL Server 2000 Installing SQL Server 2000
Installing Microsoft CRM Installing Microsoft CRM
Installing the Microsoft CRM-Exchange E-Mail Router Installing the Microsoft CRM-Exchange E-Mail Router
Installing Microsoft CRM Sales for Outlook Installing Microsoft CRM Sales for Outlook
Using Microsoft CRM Server in a Multiple Domain Deployment Using Microsoft CRM Server in a Multiple Domain Deployment
Microsoft CRM Folders Microsoft CRM Folders
Installing Microsoft CRM Using the Command Line Installing Microsoft CRM Using the Command Line

Installing Microsoft Windows Server 2003

To prepare for creating your domain controllers, you must first install Microsoft Windows Server 2003 on the computers that will be promoted to be domain controllers. In the Microsoft CRM architecture, the domain controllers are named AD01 and AD02.

Installing Windows Server 2003 for the First Domain Controller

The first step is to install Windows Server 2003 in a workgroup, including the components in the following list:

Prepare the AD01 server

  1. Perform a default installation of Windows Server 2003 by using the CD boot or floppy boot method. Install the Support Tools from the Windows Server 2003 CD. Use appropriate naming conventions for your environment; however, for the purposes of this guide, the first domain controller should be named AD01. Enable only an internal facing, or private interface, which will be on the same Ethernet segment as the private interface of your Microsoft Exchange server. Once the operating system is loaded, go to My Computer, Properties and select the Allow users to connect remotely to your computer check box on the Remote tab. This allows you to use Remote Desktop client to connect to the computer. Only users with administrator privileges (or greater) can access this computer remotely.

  2. Apply any updates.

  3. Change the event log size for the Application, Security, and System event logs to 80000 kilobytes (KB).

Deploy AD01 as the first domain controller

  1. Log on to AD01 using an account that is a member of the local administrators group.

  2. On the Start menu, click Run, type DCPROMO, and then click OK to start the Active Directory® Installation Wizard.

  3. On the Welcome to the Active Directory Installation Wizard page, click Next twice, select Domain Controller for a New Domain, and then click Next.

  4. On the Create New Domain page, select Domain in a new forest, and then click Next.

  5. On the New Domain Name page, type the full DNS name for the new domain, and then click Next. (For example, in this architecture, the full DNS name is adventureworks.com.)

  6. On the NetBIOS Domain Name page, click Next to accept the network basic input/output system (NetBIOS) domain name.

  7. On the Database and Log Folders page, click Next to accept the default database and log locations.

Note If you have additional disks in your domain controllers, the recommended configuration is to keep the Active Directory database on a hard disk drive different from the log file.

  1. On the Shared System Volume page, click Next to accept the shared system volume location.

  2. On the DNS Registration Diagnostics page, select Install and configure the DNS server on this computer, and set this computer to use this DNS server as its preferred DNS server. Click Next.

  3. On the Permissions page, select Permissions compatible only with Windows 2000 or Windows Server 2003 operating systems, and then click Next.

  4. On the Directory Services Restore Mode Administrator Password page, type a strong password using a combination of letters, numbers, and symbols (such as "DS#Restore%1"), and then click Next.

    Note   For more information about this option, see the Microsoft Knowledge Base - 257988 at support.microsoft.com/?kbid=257988.

  5. On the Summary page, click Next to accept the settings shown in the summary. This starts the creation of the Windows Server 2003 domain and installs the DNS server. (Unless you installed DNS components when installing the server, you will be prompted for the location of the files. Insert your installation CD or type the location on your local disk.)

  6. When the process is complete, click Finish, and then select Restart Now to restart the server.

Check the DNS zone for your new domain controller

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

  2. Expand AD01, expand Forward Lookup Zones, and expand adventureworks.com.

  3. Confirm that the folders exist.

To validate that your domain controller is working as specified, run DCDIAG from a command prompt. DCDIAG was installed as part of the Windows Server 2003 Support Tools. The most important test you will see is the first one: connectivity. This test will tell you whether your domain controller is properly registered in DNS. If your tests are successful, you have a healthy domain controller and can go on to the next section.

Setting Active Directory to Native Mode

Active Directory must be in native mode before you can install Microsoft CRM.

Note You must perform this procedure on an Active Directory domain controller.

Set Active Directory to native mode

  1. Log on to AD01 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 Active Directory Domains and Trusts.

  3. In the console tree, right-click the domain name for the domain that you want to administer, and then click Raise Domain Functional Level.

  4. On the Raise Domain Functional Level page, if the current domain functional level of Windows 2000 Mixed is displayed, choose Windows 2000 native or Windows Server 2003 from the drop-down list and select Raise. Click OK to close the Properties dialog box, and then click OK on the replication message.

Installing Windows Server 2003 for the Second Domain Controller

The first step is to install Windows Server 2003 in a workgroup, including the components in the following list:

Prepare the AD02 server

  1. Perform a default installation of Windows Server 2003 by using the CD boot or floppy boot method. Install the Support Tools from the Windows Server 2003 CD. Use appropriate naming conventions for your environment; however, for the purposes of this guide, the second domain controller should be named AD02.

  2. Apply any updates.

  3. Change the event log size for the Application, Security, and System event logs to 80000 KB.

  4. Make the server a member of the adventure-works domain.

  5. Ensure that AD01 is configured as the primary DNS server for AD02.

Install the Domain Name System Service on AD02

  1. From AD02, on the Start menu, point to Settings, click Control Panel, and then double-click Add/Remove Programs

  2. Click Add/Remove Windows Components.

  3. Click Networking Services, and then click Details.

  4. Select the check box for Domain Name System (DNS), click OK, and then click Next.

  5. Complete the installation.

Promoting the Second Domain Controller

In this procedure, you will promote the AD02 server you installed to be a domain controller

Promote the second domain controller

  1. Log on to AD02 using an account that is a member of the Domain Administrators group.

  2. On the Start menu, point to All Programs, point to Accessories, point to Communications, and click Network Connections. 

  3. Right-click your internal-facing network connection (usually called Local Area Connection) and select Properties.

  4. Select Internet Protocol (TCP/IP), and click Properties.

  5. Select the Use the following DNS server addresses and enter the IP address of the first domain controller, AD01 in the first text box.

  6. Click OK, and then click OK again.

  7. On the Start menu, click Run and, in the Open dialog box, type DCPROMO, and then click OK to start the Active Directory Installation Wizard.

  8. On the Welcome to the Active Directory Installation Wizard page, click Next twice, select Additional Domain Controller for an Existing Domain, and then click Next.

  9. Enter the administrator user name and password, enter adventureworks (the domain information is usually populated by default) for the domain name, and then click Next.

  10. Enter the full DNS name of the domain, adventureworks.com, and then click Next.

  11. Click Next to accept the default database and log locations.

Note If you have additional disks in your domain controllers, the recommended configuration is to keep the Active Directory database on a hard disk drive different from the log file.

  1. Click Next to accept the shared system volume location.

  2. On the Directory Services Restore Mode Administrator Password page, type a strong password using a combination of letters, numbers, and symbols (such as "DS#Restore%1"), and then click Next.

  3. Click Next to accept the settings shown in the summary, and then click Next.

  4. When complete, click Finish, and then click Restart Now to restart the server.

  5. After the server restarts, log on using an account that is a member of the Domain Administrators group.

To validate that your domain controller is working as specified, run DCDIAG from a command prompt. DCDIAG was installed as part of the Windows Server 2003 Support Tools. The most important test you will see is the first one: connectivity. This test will tell you whether your domain controller is properly registered in DNS. If your tests are successful, you have a healthy domain controller and can go on to the next section.

Configuring Domain Controllers as Global Catalog Servers

The first domain controller in the forest (AD01) is automatically configured as a global catalog server. For additional resilience, you should also configure AD02 to be a global catalog server

Configure AD02 as a global catalog server

  1. Log on to AD02 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 click Active Directory Sites and Services.

  3. Expand Sites.

  4. Expand the Default-First-Site-Name site.

  5. Expand the Servers folder.

  6. Expand the AD02 server object.

  7. Right-click the NTDS Settings object, and then click Properties.

  8. Select the Global Catalog check box, and then click OK.

  9. Close Active Directory Sites and Services.

Additional DNS Configuration

You must provide some extra configuration of the internal Active Directory integrated zone. This configuration includes restricting the list of computers for zone transfers, creating a reverse lookup zone to secure the cache against pollution, disabling recursion, and removing root hints

Creating the Reverse Lookup Zone

Configuring a reverse lookup zone provides the ability to make efficient reverse lookups for services that require this functionality.

Create the reverse lookup zone on your domain controllers

  1. Log on to AD01 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, expand the AD01 server.

  4. Right-click Reverse Lookup Zones and then click New Zone.

  5. On the Welcome page, click Next.

  6. Select Primary Zone to verify that Store the zone in Active Directory is selected, and click Next.

  7. On the Active Directory Zone Replication Scope page, select To all DNS Servers in the Active Directory forest <domainname> option.

  8. Enter the subnet network ID for your Microsoft CRM network, or work with your network team to verify the reverse lookup zone IP range for your environment. Click Next.

  9. On the Dynamic Update page, choose Allow only secure dynamic updates (recommended by Active Directory). Click Next.

  10. Click Finish to complete the wizard.

Adding the Domain Controller Pointer Records to the Reverse Lookup Zone

Configuring a reverse lookup zone helps provides bi-directional name resolution (IP address to host name and host name to IP address) for the domain controllers.

Add pointer records for the domain controllers in the reverse lookup zone

  1. Log on to AD01 using an account that is a member of the Domain Administrators group.

  2. From a command prompt type ipconfig /registerdns.

  3. Repeat steps 1 and 2 on AD02.

  4. In the DNS console on AD01, expand the AD01 server.

  5. Expand Reverse Lookup Zones, and select the reverse lookup zone that you created in the previous section.

  6. Verify that pointer records have been created for AD01 and AD02 in the reverse lookup zone.

Configuring Zone Transfers

Zone transfers for the Active Directory integrated forward and reverse lookup zones should be allowed only between the same domain controllers.

Configure zone transfers for AD01

  1. Log on to AD01 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, expand the AD01 server.

  4. Expand Forward Lookup Zones, right-click adventureworks.com, and then click Properties.

  5. Select the Zone Transfers tab, and then select the Only to the Following Servers option.

  6. Add the IP address for AD02 and then click Add.

  7. Click OK.

  8. Repeat these steps for the reverse lookup zone.

Configure zone transfers for AD02

  1. Log on to AD02 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, expand the AD02 server.

  4. Expand Forward Lookup Zones, right-click adventureworks.com, and then click Properties.

  5. Select the Zone Transfers tab, and then select the Only to the Following Servers option.

  6. Add the IP address for AD01, and then click Add.

  7. Click OK.

  8. Repeat these steps for the reverse lookup zone.

Securing the cache against pollution helps to prevent 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 both domain controllers.

Secure the DNS cache against pollution on AD01 and AD02

  1. Log on to AD01 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 AD01, and then click Properties.

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

  5. Repeat these steps on AD02.

Removing root hints will prevent the internal DNS servers from knowing about the root (.) or DNS servers and attempting to send name resolution requests to those computers. You perform the following procedure on both domain controllers.

Remove all root hints on AD01 and AD02

  1. Log on to AD01 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 AD01, and then click Properties.

  4. Select the Root Hints tab, remove any entries that are present, and then click OK.

  5. Repeat these steps on AD02.

The cache.dns file also contains the addresses of the root DNS computers. Removing this file means that there is no record of these computers on any of your internal DNS servers. You perform the following procedure on both domain controllers.

Remove the cache.dns file on AD01 and AD02

  1. Open Windows Explorer on AD01.

  2. Locate your Windows Server 2003 installation directory, and then expand \system32\dns.

  3. Delete the file named cache.dns.

  4. Repeat these steps on AD02.

Verifying DNS

Verify DNS

To verify DNS, run the NSLOOKUP utility and check that the names can be resolved both as a relative name (for example, AD01 and AD02) and as a fully qualified domain name (FQDN) (for example, ad01.adventureworks.com and ad02.adventureworks.com).

Installing Windows Server 2003 on the Remaining Microsoft CRM System Servers

When you install Windows Server 2003 for the remaining servers, make sure that you include the components in the following list:  

Prepare the remaining servers

  1. For each server listed in the following table, perform a default installation of Windows Server 2003 using the CD boot or floppy boot method. Also install the Support Tools from the Windows Server 2003 CD. Use appropriate naming conventions for your environment; however, for the purposes of this guide, name the computers based on the information in the following table. Enable only an internal facing, or private interface, which will be on the same ethernet segment as the private interface of domain controllers.

  2. Apply any Windows Server 2003 updates.

  3. Change the event log size for the Application and System event logs to 80000 KB.

  4. Ensure that all servers listed in the following table are members of the adventureworks domain and that all "additional components" are installed according to instructions in the previous sections.

Note On the Microsoft CRM server, the Microsoft .NET Framework 1.1 or later is a required component for Microsoft CRM. Although the framework is already installed on Windows Server 2003, it is also available from the Microsoft CRM installation CDs.

Note In the following chart, the name of the Microsoft CRM Server computer is shown as CRM01. This name, as are all the other computer names used in this guide, is for illustration and discussion purposes. In naming your own computers in your implementation, avoid using "extended characters", meaning those characters between decimal number 128 and 255 of the ASCII character chart. Some DNS servers are not able to recognize server names using these characters.

<table>
<colgroup>
<col style="width: 20%" />
<col style="width: 20%" />
<col style="width: 20%" />
<col style="width: 20%" />
<col style="width: 20%" />
</colgroup>
<thead>
<tr class="header">
<th><p>Computer name</p></th>
<th><p>BackNet IP configuration</p></th>
<th><p>FrontNet IP configuration</p></th>
<th><p>Member of domain</p></th>
<th><p>Additional components</p></th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td><p>CRM01</p></td>
<td><p>IP:<br />
Mask:<br />
Gateway:<br />
DNS1: AD01<br />
DNS2: AD02</p></td>
<td><p>None</p></td>
<td><p>Yes, adventureworks.com</p></td>
<td><p>Network Monitor, Internet Information Services (IIS), ASP.NET, Windows Server 2003 Support Tools</p></td>
</tr>
<tr class="even">
<td><p>CRMSQL01</p></td>
<td><p>IP:<br />
Mask:<br />
Gateway:<br />
DNS1: AD01<br />
DNS2: AD02</p></td>
<td><p>None</p></td>
<td><p>Yes, adventureworks.com</p></td>
<td><p>Network Monitor, Windows Server 2003 Support Tools,</p></td>
</tr>
<tr class="odd">
<td><p>EXBE01</p></td>
<td><p>IP:<br />
Mask:<br />
Gateway:<br />
DNS1: AD01<br />
DNS2: AD02</p></td>
<td><p>None</p></td>
<td><p>Yes, adventureworks.com</p></td>
<td><p>Network Monitor, Network News Transport Protocol (NNTP), SMTP, IIS, Windows Server 2003 Support Tools, ASP.NET</p></td>
</tr>
</tbody>
</table>

Installing Microsoft Exchange 2003

In the following sections, you install and configure Exchange 2003 in the Microsoft CRM environment. Note that in the example deployment, the following naming convention is used:

  • Active Directory DNS Domain: adventureworks.com (ISP company)

  • Exchange Organization: adventureworks

  • SMTP Domain: adventureworks.com

Note This section shows the overall steps necessary for an Exchange 2003 installation. However, due to the many variations in Exchange configurations in different organizations, it doesn't provide detailed steps. If this installation is purely for test purposes, the simple installation outlined in this section will suffice.

Preparing Active Directory for Microsoft Exchange Server 2003

A number of pre-installation steps must be accomplished to install Exchange Server 2003 into an Active Directory environment. Checklists for these steps are created during the installation process depending on the type of installation scenario being implemented. This procedure describes a brand new installation of Exchange for the adventure-works.com environment. For other scenarios, see the Exchange Deployment guide at: microsoft.com/downloads/details.aspx?FamilyId=77B6D819-C7B3-42D1-8FBB-FE6339FFA1ED&displaylang=en

Prepare Active Directory for an Exchange 2003 installation

  1. Log on to the server that acts as the Exchange server (EXBE01) using an account that is a member of the Domain Administrators group.

  2. Insert the Microsoft Exchange Server 2003 CD or click on the setup.exe file in the root of the Exchange Server 2003 CD.

  3. On the welcome page, click Exchange Deployment Tools.

  4. The Exchange Deployment Tools window will open; click Deploy the first Exchange 2003 server.

  5. Click New Exchange 2003 Installation.

  6. Verify each pre-installation step as outlined in the checklist. For purposes of the guide, we will assume that Steps 1 though 5 of the checklist have been verified.

  7. Step 6 of the checklist prepares the Active Directory Forest for Exchange. Click Run ForestPrep Now. You can also  manually start this process by starting the Exchange 2003 Setup program with the /ForestPrep switch (for example, f:\setup\i386\setup.exe /ForestPrep), and then click OK. 

  8. On the Welcome page, click Next.

  9. Click the I agree option and then click Next.

  10. On the Component Selection page, click Next.

  11. On the Exchange 2003 Administrator Account page, select the account you want to have Exchange Full Administrator permissions and click Next. When the forest preparation procedure is complete, click Finish to close the window.

  12. Step 7 of the checklist prepares the Domain for Exchange. Click Run DomainPrep Now. You can also manually start this process by starting the Exchange 2003 Setup program again, this time using the /DomainPrep switch (for example, f:\setup\i386\setup.exe /DomainPrep).

  13. On the Welcome page, click Next.

  14. Click the I agree option and then click Next.

  15. On the Component Selection page, click Next.

Note If you see a warning that the adventureworks domain is currently unsecured, click OK and continue.

  1. Click Finish to close the window when the domain preparation is complete.

Note Before continuing, if you have multiple domain controllers, allow sufficient time for replication to occur (typically 15 to 30 minutes). If you do not want to wait for replication, you can use Active Directory Sites and Services to force replication to occur.

  1. Step 8 of the checklist begins the installation of Exchange 2003. Click Run Setup Now. You can also manually start this process by starting the Exchange 2003 Setup program with no switches. (for example, f:\setup\i386\setup.exe)

  2. On the Welcome page, click Next

  3. Click the I agree option and then click Next.

  4. On the Component Selection page, choose the components you would like installed with the Exchange 2003 installation. For the requirements of this test, click Next to accept the Typical installation.

  5. On the Installation Type page, select Create a New Exchange Organization and click Next.

  6. On the Organization Name page, enter the organization name adventureworks.

  7. On the Licensing Agreement page, select I agree that I have read and will be bound by the license agreements for this product and click Next.

  8. The installation summary page appears so you can review your installation choices. Click Next to continue.

  9. When installation is complete, click Finish to close the window.

Configuring the /3GB Parameter

Exchange 2003 servers that contain more than 1 gigabyte (GB) of physical RAM require changes to the overall virtual memory allocation. You complete these steps on all Exchange Server 2003 servers; in our example deployment, this is EXBE01.

Configure the /3GB parameter on EXBE01

  1. Log on to EXBE01 using an account that is a member of the administrators group.

  2. Remove the read-only attribute from the C:\Boot.ini file. If you cannot see Boot.ini on C:\, it may be because you have set Windows to hide system files. You may need to clear the Hide Protected Operating System Files (recommended) check box in Windows Explorer. To do this:

    1. On the Tools menu, click Folder Options, click the View tab and scroll down to the Hide Protected Operating System Files (recommended) entry.

    2. Also, confirm that the Show Hidden Files and Folders entry is selected.

  3. Copy the C:\boot.ini file to C:\save_boot.ini in case you make any mistakes with the boot.ini file.

  4. Open C:\Boot.ini in a text editor, such as Notepad.

  5. Add /3GB and /USERVA=3030 (remember to leave a space before the slash characters) to the end of the line under the heading [Operating Systems], and then save the file. An example of what you would see is the following:

    [Boot Loader]  

Timeout=30 Default=multi(0)disk(0)rdisk(0)partition(2)\WINNT [Operating Systems] multi(0)disk(0)rdisk(0)partition(2)\WINNT = "Microsoft Windows Server 2003" /fastdetect /3GB /USERVA=3030

**Note**   This entry is shown on multiple lines for readability. However, they will appear in a single line.
  1. Close the text editor.

Note For more information on this switch, see Microsoft Knowledge Base - 823440. (support.microsoft.com/default.aspx?scid=kb;en-us;823440).

Configuring External DNS for the SMTP Virtual Server

You need to configure an external DNS server so that the SMTP server looks to the Internet DNS when attempting to deliver 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 EXBE01, 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 (the procedure for installing Microsoft CRM Server is later in this chapter), review your server installations and note the following:

  • Microsoft SQL Server( 2000

    • Service Pack 3a or later must be installed.

    • Microsoft SQL Server can be, but is not required to be, installed on the same computer as Microsoft CRM Server.

    • If Microsoft CRM and SQL Server are installed on different computers, they must be in the same Active Directory domain.

    • Microsoft CRM Server is supported only with a default instance of SQL Server. Named instances of SQL Server are not supported with 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 will use only Windows authentication).

    • 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. Installation of CRM will fail if the SQL Server service account is the local administrator.

    • 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.

    • Microsoft CRM does not support the personal edition of SQL Server 2000 and Microsoft SQL Server 2000 Desktop Engine (MSDE) as a database server for the Microsoft CRM server.

    • 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 SQL Server Books Online at https://www.microsoft.com/sql/prodinfo/previousversions/books.mspx.

Install SQL Server

  1. Log on to the server that will host SQL Server (CRMSQL01) using an account that is a member of the Domain Administrators group.

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

  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.

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

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

  2. 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 (CRMSQL01), and then click Next.

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

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

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

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

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

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

  9. 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.

  10. 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.

Note For performance reasons, it is recommended that you store the SQL Server program files on a different physical disk than the data. Typically, program files are located on the system partition. You may want to store the data files on a high-performance disk partition that uses the RAID specification. The Microsoft CRM setup program will store the files for the Microsoft CRM databases in this default data directory.

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

  2. On the Services Accounts page, select Use the Local System account or specify an account that is a domain administrator.

Note Microsoft CRM Setup will fail if the local administrator account is used as the SQL Server service account until Microsoft CRM is installed. After Microsoft CRM installation is complete, the SQL Server service account can be changed to a lower privilege account.

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

  2. On the Start Copying Files page, click Next to begin the installation. The installation will take 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.

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

  2. Click Finish to exit the Setup program.

  3. Remove the SQL Server default databases NorthWind and pubs from production servers.

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, you must apply the latest service pack before installing Microsoft CRM. Install SQL Server Service Pack 3a or later using the following procedures.

Install the latest SQL Server 2000 service pack

  1. Log on to the server that will host SQL Server (CRMSQL01) 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. It is recommended you make the complex with a combination of upper and lowercase characters, numbers, and special characters. 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. It is not recommended that you select this option. Click Continue.

  10. On the Error Reporting page, you can select 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. It is recommended that these two databases are backed up as part of an overall backup strategy or whenever service packs and 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 as you install Microsoft CRM on Microsoft Windows Server 2003.

  • Obtain a license key, which is required during installation, from:
    https://mbs.microsoft.com/mbsregistration/chooserelationship.aspx

  • Microsoft CRM Server should not be installed on a Domain Controller. 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. However, it is recommended that the installation is not conducted using Terminal Services.

  • You must be logged on with Domain Administrator and Local Administrator privileges when running Microsoft CRM Setup.

  • During Microsoft CRM setup, you must use a Web site that uses a local folder location in the Path field on the Home Directory in 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 errors such as the following:

    "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.

    • Windows Server components and services

  • Install Microsoft XML Core Services 4.0 (MSXML 4.0) if required.

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

Installation Prerequisites

Install prerequisite services - Internet Information Services (IIS) and Message Queuing

  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. Click Details.

  4. From the Application Server dialog box, check the Application Server Console, ASP.NET, Enable network DTC access, Internet Information Services, and Message Queuing check boxes.

  5. When Message Queuing is highlighted, choose 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

  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 folder.

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

  3. Complete the installation.

Installing and Configuring Microsoft CRM

Install Microsoft CRM

Important Do not install Microsoft CRM Sales for Outlook on the Microsoft CRM server. It is not compatible with the Microsoft CRM Server installation.

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

  2. Log on to CRM01 as a user with Domain Administrator and Local 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, then 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 in 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 type license. For example, if you have a license key for 10 users for Microsoft CRM Sales Standard , you cannot add another Sales Standard license key for 10 more users.

  1. Click Next.

  2. On the Install Required Components page, select Install listed components, and click Next. This page appears only if you do not have the 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 either Setup detects these components are already installed or the Install listed components check box is selected.

  3. On the Select SQL Server page, select the database server (CRMSQL01) that you want to use. Select Create new databases or Connect to an existing database, and click Next.

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

  5. 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) accept the default Web site then click Next.

  6. 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   As a security precaution, you should select Domain User account instead of Domain Administrator account. 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 have 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 to be the security account for ASP.NET, then all Web sites running under this instance of IIS using ASP.NET will be affected.

  7. On the Summary page, click Install.

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

  9. Restart the computer.

Add Microsoft CRM Accounts to Pre-Windows 2000 Compatible Access Group

For the Microsoft CRM servers to have access to Active Directory organizational units where users are located, you will add the following accounts to the Pre-Windows 2000 Compatible group in Active Directory:

  • Microsoft CRM Service Account (usually local computer account)

  • IIS Service Account on Microsoft CRM server (default is local computer account)

  • 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 a domain controller, on the Start menu, point to All Programs, point to Administrative Tools, and click Active Directory Users and Computers.

  2. Expand the domain, expand Builtin, right-click Pre-Windows 2000 Compatible Access, and click Properties.

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

  4. Add the Microsoft CRM Server (CRM01) and the computer running SQL Server (CRMSQL01). (This assumes you have used LocalSystem as the service account for SQL Server, IIS, and Microsoft CRM.)

  5. Click OK.

Change the Crystal Enterprise Administrator Password

Crystal Enterprise is automatically installed during the Microsoft CRM Server installation. During the Crystal Enterprise part of the installation, a Crystal Enterprise user is created (Administrator) who has full permissions to Crystal Enterprise and also has 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. Those individuals in your organization who are designing reports will need to know the new administrator password. The Crystal Enterprise administrator account is not a domain user and is not subject to domain password and security policies. It is recommended that you use a strong password for this account and change it often. 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 CRM01, 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.

Change 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 Microsoft CRM 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 field, go to the end of the commands and type -maxDBResultRecords 0, and click OK.

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

  6. Exit Crystal Configuration Manager.

Add a License Key

Add a license key

  1. On the Microsoft CRM server, 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 type license. 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 more users.

  1. 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 or 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:

  • Microsoft Exchange Server 2003.

  • 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 that the Router is to be installed.

  • The user installing the Router must be a member of the Domain Administrators 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 installation procedures will install and configure the Router on EXBE01.

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 EXBE01 as a user with Domain Administrator and Local 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 Microsoft CRM server (CRM01). In the Microsoft CRM Web site URL box, type the URL of the Microsoft CRM Web site.

    Typically, the Microsoft CRM server and the Microsoft CRM Web site are on the same computer and share the same names. If you are doing a test or lab deployment and are planning to use the Microsoft CRM Sample Database, and also using the adventure-works.com sample Active Directory DNS name, enter https://crm01.adventure-works.com for the Microsoft CRM Web site URL.

  9. Click OK, and you will return to the Configure Servers page. Click OK, and you will return to the Specify Microsoft CRM Server page. Click Next.

  10. On the Specify Security Account page, type the logon name (in the format domainname\username) and password. For the Adventure Works Cycle sample deployment, enter adventure-works\administrator for the logon name, enter the correct password, and then click Next.

Note For a production environment, it is recommended that a domain user account be established as the service account.

  1. On the Select Installation Locations page, accept the Default Web Site and file installation directory, and then click Next. On this page, the Default Web Site is the Web site on the computer on which you are installing the Router, not the Microsoft CRM server.

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

  3. 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 SQL Server computer (CRMSQL01), 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 SQL_Server (CRMSQL01), 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 MSCRM and 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 2003 mailbox created for them. To have the user created with an Exchange 2003 mailbox, you must run the Active Directory Users and Computers on a server that has Exchange 2003 System Manager installed. You can also run Active Directory Users and Computers from any of the Exchange Server 2003 servers.

Add a user to Active Directory

  1. Log on to the Exchange Server 2003 (EXBE01) 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 you want.

  9. In User logon name, type the name that the user will log on with and, from the drop-down list, click the UPN suffix that must be appended to the user logon name (following the @ 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 the following procedures for configuring your 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 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 the Deployment Manager at first. You will need to add other users as necessary to the product.

Configure users

  1. Log on to the Microsoft Exchange Server computer (EXBE01) 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, 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. You can use User Manager to create user records in Microsoft CRM once those users exist in Active Directory. The benefit to using User Manager is that you can create multiple user records at one time. User Manager creates user records by using the User Manager Wizard.

Note   When 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 Microsoft CRM server, 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 Microsoft CRM server, start Internet Explorer and in the browser address box, type https://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 in 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 Exchange Server 2003 (EXBE01) 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 @ 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. Therefore, 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.

    Note   By default, the SELF account will already have Full Mailbox Access permissions if this is a disabled account. The SELF account is available in all Microsoft Windows Server 2003 domains. All SELF accounts share a well-known security identifier (SID) that is the same across all domains. If the SELF account is not already listed in the Permissions dialog box, you can add it by typing SELF as the account name.

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

Note After the Exchange 2003 DSAccess cache is refreshed (which may take some time), the new configurations will take effect and e-mail messages that are sent to the disabled account will not generate errors.

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

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

  3. Type CRMEmailEnabled, click OK, click OK to close the Exchange Custom Attributes dialog box, and then click OK 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 Microsoft CRM server, start Internet Explorer and in the browser address box, type https://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).

Configuring the Adventure Works Cycle Sample Database

Configure licenses

  1. On the Microsoft CRM server (CRM01), start Internet Explorer and in the browser address box, type https://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). From 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. From the File menu, choose 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.Tools.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.

Installing Microsoft CRM Sales for Outlook

Microsoft CRM Sales for Outlook (the Outlook client) is the integrated Microsoft® Outlook® client for Microsoft Business Solutions CRM that enables access to the same data as the Microsoft CRM Web client application. In addition, the client application also comes with offline functionality. Thus, salespeople who require offline support for sales force automation application data while they work out in the field, have access to their customer data using laptops.

The Outlook client is targeted at sales and marketing people and provides sales module functionality. The offline Outlook client will give sales and marketing people visibility into many customer service items (for example, cases) that are related to customers, but will not give them the ability to create new customer service items.

The Outlook client resides within Outlook for its main application interface and is available from the Outlook shortcut bars and folder navigation that is displayed within the main window of Outlook. Installing Microsoft CRM Sales for Outlook creates an icon on the Outlook bar and one folder within the user's mailbox folder structure. Microsoft CRM Sales for Outlook will also add a link to the Start menu.

System Requirements

To optimize the performance of the Outlook client, the following system requirements are recommended:

  • A personal computer with an Intel or compatible Pentium 300-MHz or higher processor.

  • Minimum of 256 MB of RAM. (More RAM is recommended.)

  • Microsoft Windows 2000 Professional with Service Pack 4, Windows XP Professional with Service Pack 1. (Windows 98, Windows 98 SE, Windows Millennium Edition, Windows NT 4.0 Workstation, and Windows XP Home Edition, are not supported.)

  • Microsoft Office 2003 Editions

    OR

  • Microsoft Office XP (2002) with Service Pack 2

    OR

    Microsoft Office 2000 with the following additional requirements:

  • Microsoft Internet Explorer 6.0 SP1 or later.

  • Microsoft SQL Server 2000 Desktop Engine (MSDE) is installed as part of the Outlook client.

One of the reasons for these requirements is that the Outlook client will maintain a data store on the user's computer for Microsoft CRM data. Data from the Microsoft CRM server will synchronize with this local store for offline access to data. In addition, there is two-way synchronization between this local store and Outlook for contacts, tasks, the calendar, and e-mail items. When the user's computer is again attached to the organization's network, synchronization also takes place between the Microsoft SQL Server 2000 Desktop Engine and the Microsoft CRM server posting client-side transactions back to the server.

Prerequisite Checklist

The following is a checklist of prerequisite software and configuration items that must installed before installing Microsoft CRM Sales for Outlook:

  • Microsoft CRM Server must be installed and running.

  • The client computer must be installed with the system requirements listed in the previous section.

  • Indexing Service must be installed and running on the client computer.

  • Outlook must be started at least once. (This insures that Outlook is configured prior to installing the Outlook client.)

    Note   Starting Outlook creates a default profile. During installation, the Outlook client binds to the default profile. Problems may occur preventing the Outlook client from functioning properly if you then create (or already have) additional profiles and try to change or delete the default profile.

  • The person installing the Outlook client must be a valid Microsoft CRM user with roles and a license as well as a local administrator on the client computer.

  • The Outlook client computer is not the same computer as the Exchange server or the Microsoft CRM server.

Installing the Outlook Client

Follow the procedures in this section to install the Outlook client.

Important Do not install the Outlook client on the Microsoft CRM server. It is not compatible with the Microsoft CRM Server installation.

Install Microsoft CRM Sales for Outlook

  1. Meet all requirements in the previous "Prerequisite Checklist" section and make sure all Microsoft Office security hotfixes are installed.

  2. Log on to the computer as a user with Local Administrator privileges.

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

  4. Click Install Microsoft CRM Sales for Outlook on the opening screen.

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

  6. On the Install Required Components page, select Install listed components, and click Next.

    Note   These components are required before the Outlook client 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 either Setup detects these components are already installed or the Install listed components check box is selected.

  7. On the Specify Microsoft CRM Server page, type the URL for the Microsoft CRM server (https://crm01), and click Next.

  8. On the Specify Installation Directory page, choose an installation folder for the Outlook client files. Accept the default path, use the Browse button, or enter a location path, and click Next.

  9. On the Ready to Install page, click Install to begin installation. This page provides a summary of the installation information. You can click Back to return to a previous page.

  10. A message box will be displayed indicating a successful install. Click OK. You will be prompted to restart the computer.

Creating a Server-Based Setup Location

You can create a server-based setup location and then allow clients to connect to the share in order to install the product. Use the following procedure to achieve this.

Install Microsoft CRM Sales for Outlook in Admin Mode

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

  2. Make sure that your Microsoft CRM server is properly installed.

  3. Map a drive to the network location where you want to create an image of the Microsoft CRM Sales for Outlook CD. This location can be entered as \\networkshare during setup.

  4. From the Microsoft CRM Sales for Outlook CD, run setup.exe /a.

  5. Point to the mapped drive or provide the network share where you want to create the admin image.

  6. Enter a valid Microsoft CRM server name.

Configuring Offline Use of the Outlook Client

If a user wants to use the Outlook client when the computer is disconnected from the network, the Outlook client requires the user to be able to use his or her domain credentials (even when the computer is not on the domain). You must configure the computer to allow the user to log on to his or her computer and set domain policies to allow cached credentials on the local computer. Windows allows ten sets of user credentials to be stored by default.

Allow cached credentials

  1. On the Start menu, point to Programs, point to Administrative Tools, and click Local Security Policy.

  2. Expand Local Policies, and then select Security Options.

  3. Set the value in Number of previous logons to a value greater than 0. Or, if using Windows XP, set the value Interactive Logon: Number of previous logons to cache to a value greater than 0 (the default value is 10).

Using Microsoft CRM Server in a Multiple Domain Deployment

In an organization that has multiple Active Directory domains, Microsoft CRM Server is typically installed on only one of the domains. However, users assigned to the domains other than the one where Microsoft CRM Server is installed may want to use Microsoft CRM Server. To allow these users access to the computer running Microsoft CRM Server, they must be added to the Microsoft SQL Server security for the Microsoft CRM Server databases.

To add users from other Active Directory domains to the Microsoft CRM databases, add a prefix to the domain user's name of those domain users being added to the Microsoft CRM database security.

Add users from other Active Directory domains

  1. Open Microsoft SQL Server Enterprise Manager.

  2. Expand to Security/Logins for the SQL Server that contains the Microsoft CRM databases.

  3. Add <domainname> \ <prefix> domain users as a login.

  4. On the Database Access tab, select both the MSCRM and Metabase databases and set the access level to the default value.

  5. Repeat for each domain.

Microsoft CRM Folders

Microsoft CRM creates the default folders listed in the following table during installation.

Folder

Shared

Permissions

<systemdrive>:\Program Files\Microsoft CRM\bin

Note   Do not modify the permissions of this folder. Any modifications to this folder will disable the program.

No

Dependent on parent folder and special permissions for the security service.

<systemdrive>:\Program Files\Microsoft CRM\

Microsoft CRM Server program files

No

Dependent on parent folder

<systemdrive>:\Program Files\Microsoft SQL Server\MSSQL\Data

Microsoft CRM SQL Server database files

No

Default settings

<systemdrive>:\Program Files\Microsoft CRM\Crystal Decisions\Enterprise 9\

Crystal Enterprise

No

Dependent on parent folder

<systemdrive>:\Program Files\Microsoft SQL Server\REPLDATA\mscrm

Microsoft CRM Sales for Outlook data store

Yes

Everyone - Read

<systemdrive>:\Program Files\Microsoft CRM\MSCRMConnector

Microsoft CRM-Exchange E-mail Router

No

Dependent on parent folder

<systemdrive>:\Inetpub\wwwroot\MSCRMServices

No

Dependent on parent folder

Installing Microsoft CRM Using the Command Line

The Microsoft CRM Server, Microsoft CRM Sales for Outlook (the Outlook client), and the Microsoft CRM-Exchange E-mail Router (the Router) can be installed from the respective CD using the command line. The required setup information is provided both as command-line parameters and as an XML configuration file that is referenced by the setup program.

One advantage of installing Microsoft CRM using the command line is that you do not have to attend the installation. Attended installation requires you to make various decisions and provide information so that installation can complete successfully. Unattended installation via the command line requires you to provide the installation information as command-line parameters and an XML setup configuration file. No other action is required until setup is complete. Errors and installation progress can be logged to a file that can be viewed and analyzed at a later time.

General Procedures

The procedures for accessing the Setup.exe program on the individual CDs are basically the same. All prerequisites for each of these products as discussed in previous sections of this chapter also apply.

  1. Log on to the computer as a user with Domain Administrator and Local Administrator privileges.

  2. Insert the Microsoft Business Solutions CRM Server CD into your CD-ROM drive. The autorun screen should appear. Exit the autorun screen.

  3. Open a command window.

  4. Change drives to the CD-ROM drive containing the Microsoft CRM CD.

    • Setup.exe for Microsoft CRM Server is located in the root of the Microsoft Business Solutions CRM Server CD.

    • Setup.exe for Microsoft CRM Sales for Outlook is located in the root of Microsoft Business Solutions CRM Sales for Outlook CD.

    • Setup.exe for Microsoft CRM-Exchange E-mail Router is located in the \Exchange folder on the Microsoft Business Solutions CRM Server CD.

Install Microsoft CRM Server

The following command will install Microsoft CRM Server:

Setup.exe [/?] [/Q] [/L [drive:][[path] logfilename.log]] [/config [drive:] [[path] configfilename.xml]]

Setup.exe for Microsoft CRM Server is located in the root of the Microsoft Business Solution CRM Server CD.

Parameters

None

Used without parameters, Setup.exe will install with all display screens.

/?

Displays parameter information.

/Q

Quiet mode installation. Requires a configuration file in XML format specified by the /config parameter. No dialog boxes or error messages will appear on the display screen. To capture error message information, a log file must be included as an option.

/QN+

Requires a configuration file in XML format specified by the /config parameter. Displays only the final message at the end of installation indicating success or failure. No other dialog boxes or error messages are displayed.

/QR

Requires a configuration file in XML format specified by the /config parameter. Displays installation progress bars and all error messages.

/L [ drive :][[ path ] logfilename.log ]]

Creates a log file of installation activity. The file name of the log file and the location where it is to be placed must be specified. Log file entries from the Crystal Reports part of the installation will be included in this log file. The following options are available:

/LV Log verbose.

/L* Log all information except verbose.

/L*V Log all information including verbose.

/config [ drive: ] [[ path ] configfilename.xml ]]

The /config parameter uses the specified XML configuration file to provide Setup with additional information required to complete installation successfully. An example configuration XML file is discussed in the following section.

Note Setup will also look for a valid XML configuration file called "SETUP.XML" in the working directory and will use this file for setup even if the /config parameter is not specified. However, using the /config parameter takes prescience over any " SETUP.XML" file.

The XML Configuration File

The /config [drive:] [[path] configfilename.xml]] command-line parameter provides Microsoft CRM Server Setup with required information. The information supplied by the XML configuration file is the same that is required by each of the installation screens. The XML elements must be in US English. Using a XML configuration file with localized XML elements will not work properly. An explanation of each of the XML elements and a sample XML file follows:

<CRMSetup> </CRMSetup>

The configuration file must be a valid XML file using <CRMSetup> as the root element.

<Server> </Server>

Specifies a Microsoft CRM Server installation.

<SqlServer>SQLServername</SqlServer>

The name of the Microsoft SQL Server instance that will manage the Microsoft CRM Server database files.

<Database create="True"/ "False"/>

Values for this parameter are either "true" or "false". "True" causes Setup to create a new Microsoft CRM database. "False" causes Setup to connect to an existing Microsoft CRM database as indicated by the Active Directory organizational name (see the <Organization> element below).

<Organization> OrganizationName </Organization>

Specifies the name of your organization.

<OU>LDAP://OU= value ,DC= value ,DC= value ,DC= value ,DC=com</OU>

The <OU> element specifies the Active Directory organizational unit (OU) and domain controller (DC) values that this Microsoft CRM server is to be associated with. Note that LDAP is the protocol specified to communicate this information to Active Directory.

<LicenseKeys>
**     <LicenseKey>** KeyValue </LicenseKey>
**     <LicenseKey>** AnotherKey </LicenseKey>
</LicenseKeys>

The configuration file can accommodate any number of Microsoft CRM Server license keys you have.

<WebsiteUrl>/LM/W3SVC/1</WebsiteUrl>

Specifies the path for the Web site to be created on the Microsoft CRM server.

<InstallDir>c:\program files\mscrm</InstallDir>

Specifies the folder on the Microsoft CRM Server computer where the Microsoft CRM Server files are to be placed.

<CrmServiceAccount type="DomainUser">
**     <ServiceAccountLogin>** login </ServiceAccountLogin>
**     <ServiceAccountPassword>** password </ServiceAccountPassword>
</CrmServiceAccount>

Specify the Microsoft CRM service account type. <ServiceAccountLogin> and <ServiceAccountPassword> are required.

Caution: Maintaining the configuration file with <ServiceAccountLogin> and <ServiceAccountPassword> values specified is a security risk because you are storing a password in plain text. Delete these elements as soon as the configuration file is used to install your Microsoft CRM Server.

<CrystalServiceAccount type="DomainUser">

**     <ServiceAccountLogin>** login </ServiceAccountLogin>
**     <ServiceAccountPassword>** password </ServiceAccountPassword>

</CrystalServiceAccount>

Specifies the service account for Crystal Reports. The accepted values are "LocalSystem" and "DomainUser". If "DomainUser" is used, <ServiceAccountLogin> and <ServiceAccountPassword> are required. If "LocalSystem" is used, the following simplified XML entry can be used:

<CrystalServiceAccount type="LocalSystem"/>

Caution: Maintaining the configuration file with <ServiceAccountLogin> and <ServiceAccountPassword> values specified is a security risk because you are storing a password in plain text. Delete these elements as soon as the configuration file is used to install your Microsoft CRM Server.

<AspNetServiceAccount type="DomainUser">

**     <ServiceAccountLogin>** login </ServiceAccountLogin>
**     <ServiceAccountPassword>** password </ServiceAccountPassword>

</AspNetServiceAccount>

Specifies the service account for ASP.NET. The accepted values are "LocalSystem", "NetworkService", and "DomainUser". If "DomainUser" is used, <ServiceAccountLogin> and <ServiceAccountPassword> are required. If "LocalSystem" or "NetworkService" is used, the following simplified XML entry can be used:

<AspNetServiceAccount type="LocalSystem"/>

<IntegrationAccount type="DomainUser">

<ServiceAccountLogin>login</ServiceAccountLogin>

<ServiceAccountPassword>password</ServiceAccountPassword>

</IntegrationAccount>

Specifies the service account for Integration. The accepted value is "DomainUser" only, and <ServiceAccountLogin> and <ServiceAccountPassword> are required. In addition, the <ServiceAccountLogin> must use the format domain\user.

Caution: Maintaining the configuration file with <ServiceAccountLogin> and <ServiceAccountPassword> values specified is a security risk because you are storing a password in plain text. Delete these elements as soon as the configuration file is used to install your Microsoft CRM Server.

Sample server XML configuration file

<CRMSetup>
    <Server>
    <SqlServer>MYSQLSERVER</SqlServer>
        <Database create="false"/>
        <Organization>OrganizationName</Organization>
        <OU>
            LDAP://OU=value,DC=value,DC=value,DC=value,DC=com
        </OU>
        <LicenseKeys>
            <LicenseKey>LicenseKey</LicenseKey>
            <LicenseKey>AnotherKey</LicenseKey>
        </LicenseKeys>
        <WebsiteUrl>/LM/W3SVC/1</WebsiteUrl>
        <InstallDir>c:\program files\mscrm</InstallDir>
        <CrmServiceAccount type="DomainUser">
            <ServiceAccountLogin>
                login
            </ServiceAccountLogin>
            <ServiceAccountPassword>
                password
            </ServiceAccountPassword>
        </CrmServiceAccount>
        <CrystalServiceAccount type="DomainUser">
            <ServiceAccountLogin>login</ServiceAccountLogin>
            <ServiceAccountPassword>
                password
            </ServiceAccountPassword>
        </CrystalServiceAccount>
        <AspNetServiceAccount type="DomainUser">
            <ServiceAccountLogin>login</ServiceAccountLogin>
            <ServiceAccountPassword>
                password
            </ServiceAccountPassword>
        </AspNetServiceAccount>
        <IntegrationAccount type="DomainUser">
            <ServiceAccountLogin>
                domain\user
            </ServiceAccountLogin>
            <ServiceAccountPassword>
                password
            </ServiceAccountPassword>
        </IntegrationAccount>
    </Server>
</CRMSetup>

Install Microsoft CRM Sales for Outlook

The following command will install Microsoft CRM Sales for Outlook:

Setup.exe [/?] [/A] [/Q] [/L [drive:][[path] logfilename.log]] [/config [drive:] [[path] configfilename.xml]]

Setup.exe for Microsoft CRM Sales for Outlook (the Outlook client) is located in the root of the Microsoft Business Solution CRM Sales for Outlook CD.

Parameters

None

Used without parameters, Setup.exe will install with all display screens.

/?

Displays parameter information.

/A

This parameter allows for administrative installs of the Outlook client. This parameter must be used along with the <AdminInstallDir> element in the XML configuration file discussed in the following section.

/Q

Quiet mode installation. Requires a configuration file in XML format specified by the /config parameter. No dialog boxes or error messages will appear on the display screen. To capture error message information, a log file must be included as an option.

/QN+

Requires a configuration file in XML format specified by the /config parameter. Displays only the final message at the end of installation indicating success or failure. No other dialog boxes or error messages are displayed.

/QR

Requires a configuration file in XML format specified by the /config parameter. Displays installation progress bars and all error messages.

/L [ drive: ][[ path ] logfilename.log ]]

Creates a log file of installation activity. The file name of the log file and the location where it is to be placed must be specified. The following options are available:

/LV Log verbose.

/L* Log all information except verbose.

/L*V Log all information including verbose.

/config [ drive: ] [[ path ] configfilename.xml ]]

The /config parameter uses the specified .XML configuration file to provide setup with additional information required to complete installation successfully. An example configuration XML file is discussed in the following section.

The XML Configuration File

The /config [drive:] [[path] configfilename.xml]] command line parameter provides the Outlook client Setup with required information. The information supplied by the configuration file is the same that is required by each of the installation screens. The XML elements must be in US English. Using a XML configuration file with localized XML elements will not work properly. An explanation of each of the XML elements and a sample XML file follows:

<CRMSetup> </CRMSetup>

The configuration file must be a valid XML file using <CRMSetup> as the root element.

<Client> </Client>

Specifies a Microsoft CRM Sales for Outlook installation.

<WebsiteUrl> https://website </WebsiteUrl>

Specifies the URL for the Web site associated with the Microsoft CRM server.

<InstallDir>c:\program files\ mscrm_client </InstallDir>

Specifies the folder on the Outlook client computer where the client files are to be placed.

<AdminInstallDir>\\share\ mscrm_client_admin </AdminInstallDir>

Specifies the network shared folder where the Outlook client CD image will be stored for administrative installations. Admin Installation directory does not have to be located on the local computer. A mapped drive or network share such as \\share\mscrm_client_admin can be used.

Sample Outlook client XML configuration file

<CRMSetup>
    <Client>
        <WebsiteUrl>https://website</WebsiteUrl>
        <InstallDir>
            c:\program files\mscrm_client
        </InstallDir>
        <AdminInstallDir>
            \\share\mscrm_client_admin
        </AdminInstallDir>
    </Client>
</CRMSetup>

Install Microsoft CRM-Exchange E-Mail Router

The following command will install Microsoft CRM-Exchange E-mail Router:

Setup.exe [/?][/Q] [/L [drive:][[path] logfilename.log]] [/config [drive:] [[path] configfilename.xml]]

Setup.exe for Microsoft CRM-Exchange E-mail Router is located in the \Exchange folder on the Microsoft Business Solutions CRM Server CD.

Parameters

None

Used without parameters, Setup.exe will install with all display screens.

/?

Displays parameter information.

/Q

Quiet mode installation.  No dialog boxes or error messages will appear on the display screen. To capture error message information, a log file must be included as an option.

/QN+

Requires a configuration file in XML format specified by the /config parameter. Displays only the final message at the end of installation indicating success or failure. No other dialog boxes or error messages are displayed.

/QR

Requires a configuration file in XML format specified by the /config parameter. Displays installation progress bars and all error messages.

/L [ drive: ][[ path ] logfilename.log ]]

Creates a log file of installation activity. The file name of the log file and the location where it is to be placed must be specified. The following options are available:

/LV Log verbose.

/L* Log all information except verbose.

/L*V Log all information including verbose.

/config [ drive: ] [[ path ] configfilename.xml ]]

The /config parameter uses the specified XML configuration file to provide Setup with additional information required to complete installation successfully. An example configuration XML file is discussed in the following section.

The XML Configuration File

The /config [drive:] [[path] configfilename.xml]] command line parameter provides the Microsoft CRM-Exchange E-mail Router Setup with required information. The information supplied by the configuration file is the same that is required by each of the installation screens. The XML elements must be in US English. Using a XML configuration file with localized XML elements will not work properly. An explanation of each of the XML elements and a sample xml file follows:

<CRMSetup> </CRMSetup>

The configuration file must be a valid XML file using <CRMSetup> as the root element.

<ExchangeConnector> </ExchangeConnector>

Specifies a Microsoft CRM-Exchange E-mail Router installation.

<CRMServers>
**    <CRMServer name="** CRMServerName " URL=" https://WebsiteURL "/>
</CRMServers>

Indicates the Microsoft CRM server to which e-mail will be routed to. Any number of Microsoft CRM servers can be specified.

<WebsiteUrl> https://website </WebsiteUrl>

Specifies the URL for the Web site associated with the Microsoft CRM server.

<InstallDir>c:\program files\ mscrm </InstallDir>

Specifies the folder on the Microsoft Exchange Server computer where the Microsoft CRM-Exchange E-mail Router files are to be placed.

<ServiceAccount type="DomainUser">
**    <ServiceAccountLogin>** login </ServiceAccountLogin>
**    <ServiceAccountPassword>** password </ServiceAccountPassword>
</ServiceAccount>

Specify the Microsoft CRM-Exchange E-mail Router service account. <ServiceAccountLogin> and <ServiceAccountPassword> are required.

Caution: Maintaining the configuration file with <ServiceAccountLogin> and <ServiceAccountPassword> values specified is a security risk because you are storing a password in plain text. Delete these elements as soon as the configuration file is used to install your Microsoft CRM-Exchange E-mail Router.

Sample CRM-Exchange E-mail Router XML configuration file

<CRMSetup>
    <ExchangeConnector>
        <CRMServers>
            <CRMServer name="CRMServerName"
            URL="https://WebsiteURL"/>
        </CRMServers>
        <WebsiteUrl>https://website</WebsiteUrl>
        <InstallDir>c:\program files\mscrm</InstallDir>
        <ServiceAccount type="DomainUser">
            <ServiceAccountLogin>login</ServiceAccountLogin>
            <ServiceAccountPassword>
               password
            </ServiceAccountPassword>
        </ServiceAccount>
    </ExchangeConnector>
</CRMSetup>