mscrm布署微软crm的应用技术文档.doc

.Table of ContentsOverview3Using a configuration file or the “CRM40IFDTool”3Setup test DNS record4Microsoft Dynamics CRM Data Connector for SQL Server Reporting Services5Scenario 1: Install or Upgrade Microsoft Dynamics CRM 4.0 through the user interface (UI) setup5Scenario 2: Install or Upgrade Microsoft Dynamics CRM 4.0 with a configuration file6How to use the CRM40IFDTool9Steps to run the tool9More Information12ISA Server12Turn off IFD12Log File12Installing CRM with IFD enabled against an existing website with Host headers or a Certificate enabled on the website.13Splitting Out Server Roles14Troubleshooting Information16FAQ18Send Feedback on the article24How to configure an Internet-Facing Deployment for Microsoft Dynamics CRM 4.0This document will cover the following Internet-Facing Deployment (IFD) scenarios for Microsoft Dynamics CRM 4.0. · Install or Upgrade Microsoft Dynamics CRM 4.0 through the user interface (UI) setup· Install or Upgrade Microsoft Dynamics CRM 4.0 with a configuration fileThis document is intended to cover how to set up Microsoft Dynamics CRM 4.0 to make it ready to be accessed from the Internet. This document will not cover the steps that you must complete to make a server available from the Internet. There will be additional steps depending on if you are using ISA server, firewalls or anything else in your environment that may need to be configured to get your server accessible from the internet.OverviewUsing a configuration file or the “CRM40IFDTool”To successfully set up a Microsoft Dynamics CRM 4.0 IFD environment, there are several items that must be set for authentication to work correctly. These options are set when you install Microsoft Dynamics CRM 4.0 by using a configuration file or by using the “CRM40IFDTool” after Microsoft Dynamics CRM is installed to enable IFD.Enabling IFD does the following:· The web.config file contains an authentication strategy parameter. This parameter will be updated to “ServiceProviderLicenseAgreement”· For example, you would see the following parameter in the web.config file:· <authentication strategy =”ServiceProviderLicenseAgreement”/>· The Enable anonymous access authentication method on the Microsoft Dynamics CRM 4.0 Web site is marked. · Note: The Integrated Windows authentication method must remain marked for internal users who do not access the Microsoft Dynamics CRM Web site by using the IFD deployment.· The DeploymentProperties table in the MSCRM_Config SQL database has three values that are updated.o IfdRootDomainScheme § or so IfdSdkRootDomain§ Domain.o IfdWebApplicationRootDomain§ Domain.· The IfdInternalNetworkAddress registry key on the Microsoft Dynamics CRM server is updated. This registry key determines whether the user is logging into the Microsoft Dynamics CRM Web site from the Internet or Intranet. This registry value then determines whether the user uses CRM ticket authentication (Internet) or Integrated Windows authentication (Intranet).o The IfdInternalNetworkAddress registry key is located here:o HKEY_LOCAL_MACHINESOFTWAREMicrosoftMSCRMo This key holds an example of an ip address and the subnet of the domain. For example, the key may hold the following ip address and subnet value:§ 192.220.100.96-255.255.255.0o If you have more than 1 subnet, you can add multiple values to the registry key.o Note: The values must be separated by a comma.§ 192.220.100.1-255.255.255.0, 192.220.64.1-255.255.252.0· Key encryption will be enabled. o For a user to log on to the Microsoft Dynamics CRM Web site with the CRM Ticket Authentication, the CRMTicketKey must to be enabled. Without a ticket the authentication will fail.o The key encryption is enabled by setting the <ifdsettings enabled="true"> option in the configuration file when you install or upgrade to Microsoft Dynamics CRM 4.0. You can also use the “CRM40IFDTool” to enable the key encryption after the install or upgrade. Setup test DNS recordAfter you have completed the installation or upgrade by using a configuration file or the “CRM40IFDTool,” you must set up a DNS record for each organization that will be accessed externally from the Internet. Setting up the DNS record enables the Web site to correctly resolve externally.· When Microsoft Dynamics CRM 4.0 is installed, or when you create a new organization, you provide a Display Name and a Name for each organization. The Name field is a unique name that must be less than 30 characters and cannot contain spaces or other special characters. This Name is used in the URL address when you open the Microsoft Dynamics CRM Web site. The DNS host record that needs to be setup is for the Name of each organization you need to access through IFD.o For example, assume the Display Name value is Microsoft CRM and the Name value is Microsoft. To open the Microsoft Dynamics CRM Web site for an IDF deployment, the URL address would be s:/microsoft.domain. You would need to create a DNS host record called Microsoft.o Note: This example assumes the DNS records are set up to correctly resolve this URL address externally.Microsoft Dynamics CRM Data Connector for SQL Server Reporting Services You must install the Microsoft Dynamics CRM Data Connector for SQL Server Reporting Services on the Microsoft SQL Server Report Server if users will run Microsoft Dynamics CRM reports when accessing Microsoft Dynamics CRM over IDF.Note: Microsoft SQL 2005 Workgroup Edition does not support custom data extensions for SQL Server Reporting Services. Therefore, the Microsoft Dynamics CRM Data Connector for SQL Server Reporting Services will not work when installed on the Microsoft SQL 2005 Workgroup Edition. For more information, see the following Microsoft Knowledgebase (KB) article: support.microsoft./kb/946753Scenario 1: Install or Upgrade Microsoft Dynamics CRM 4.0 through the user interface (UI) setupThere are no options to enable the Microsoft Dynamics CRM 4.0 IDF deployment in the Setup Wizard. Therefore the CRM40IFDTool must be used to enable IFD after Microsoft Dynamics CRM 4.0 is installed. In this example CRM has been installed or upgraded to CRM 4.0 and our unique Organization Name is called MicrosoftPost Installation Tasks for Scenario 1:1. Run the CRM40IFDTool to enable the IFD environment. This tool is available for download in the following Microsoft KB article: support.microsoft./kb/948779 For information on how to run the CRM40IFDTool see the How to use the Microsoft Dynamics CRM Internet Facing Deployment Configuration Tool section in this document. 2. Create a Host or Alias record in DNS for each Microsoft Dynamics CRM organization that will be accessed externally on the Internet. For the URL address to resolve correctly, you must create a DNS Host or Alias record for the for the unique organization name in Microsoft Dynamics CRM. For example: s:/ Microsoft.domain. would need a DNS host or alias record called Microsoft.a. To create a DNS host or alias record follow these steps:b. On your DNS server click Start, click Run and type in dnsmgmt.mscc. Expand Forward Lookup Zones and right click your domain. folder and choose New Host (A) or New Alias (CNAME)d. In the Name field or Alias name field type the unique organization name you specified when setting up CRM. e. Note: If you do not know the unique name you can check this in Deployment Manager on the Microsoft Dynamics CRM Server by selecting the Organizations node and then right click on your Organization name and choose properties.f.g. Then type in the IP address of the CRM Server if you are creating a host record and click Add Host, then click OK and click Done. If you are adding an Alias click Browse and add the Microsoft Dynamics CRM server and click OK.h.Scenario 2: Install or Upgrade Microsoft Dynamics CRM 4.0 with a configuration fileYou can create IFD settings in the configuration file. Then, you can use the configuration file during the Microsoft Dynamics CRM installation or upgrade to enable IFD. The following options are available in the configuration file:· <ifdsettings enabled="true"/"false">This option should only be used for Internet-facing deployments. Set enabled = "true" to notify Microsoft Dynamics CRM Server Setup to configure the deployment for Internet access. If the <ifdsettings> element is not specified, the enabled attribute value is set to false. · <internalnetworkaddress>IP Network Address-Subject Mask</internalnetworkaddress>· IP address and subnet mask, such as 157.56.137.105-255.255.255.0. This is the internal IP address and the associated subnet mask of the subnet where your internal users reside. The subnets you enter here will be for the computers that you want to be considered as internal and you do not want the users to login through the IFD environment when they are on these subnets. To enter multiple subnets use a comma to separate the values in the configuration fileNote: If you leave this element blank, all communication to the Microsoft Dynamics CRM server will be considered as internal and users will default to windows authentication when hitting the Microsoft Dynamics CRMwebsite.· <rootdomainscheme> s/ </rootdomainscheme> · Must be s, which will use secure sockets layer (SSL), or , which will use the nonsecure protocol.· Note: Setup does not require SSL on the Web site where Microsoft Dynamics CRM is installed. We strongly recommend that you specify the s value in the rootdomainscheme element. In addition, after Setup is complete, to help protect information that is transmitted between users and Microsoft Dynamics CRM Server, we recommend that you configure the Web site to require SSL. For more information about how to use SSL, see the Internet Information Services (IIS) Manager Help.· <sdkrootdomain>domain.</sdkrootdomain> · Specifies the domain name that will be used for applications that use the methods described in the Microsoft Dynamics CRM 4.0 Software Development Kit (SDK). The value that is set here will be prefixed by your unique organization name to form the URL so you only need to put in the domain.· <webapplicationrootdomain>domain. </webapplicationrootdomain> Specifies the domain name that will be used for the Microsoft Dynamics CRM Web application and Microsoft Dynamics CRM for Outlook. The value that is set here will be prefixed by your unique organization name to form the URL so you only need to put in the domain.Note: If you are going to split out your server roles see the More Information section at the end of this document.The following configuration file example contains an IFD section: <ifdsettings enabled="true"> <internalnetworkaddress>192.200.47.1-255.255.255.0</internalnetworkaddress> <rootdomainscheme> s</rootdomainscheme> <sdkrootdomain>domain.</sdkrootdomain> <webapplicationrootdomain>domain.</webapplicationrootdomain> </ifdsettings>NOTE: For more information about configuration file installations, see the Microsoft Dynamics CRM 4.0 Implementation Guide.After the installation is complete, when you log on to the Microsoft Dynamics CRM Web site from a computer that is outside the subnet zone(s) you specified in the IFDInternalNetworkAddress registry key, you will get redirected to the sign in page like in the screen shot below.Post Installation Tasks for Scenario 2:1. Create a Host or Alias record in DNS for each Microsoft Dynamics CRM organization that will be accessed externally on the Internet. For the URL address to resolve correctly, you must create a DNS Host or Alias record for the for the unique organization name in Microsoft Dynamics CRM. For example: s:/ Microsoft.domain. would need a DNS host or alias record called Microsoft.a. To create a DNS host or alias record follow these steps:b. On your DNS server click Start, click Run and type in dnsmgmt.mscc. Expand Forward Lookup Zones and right click your domain. folder and choose New Host (A) or New Alias (CNAME)d. In the Name field or Alias name field type the unique organization name you specified when setting up CRM. e. Note: If you do not know the unique name you can check this in Deployment Manager on the Microsoft Dynamics CRM Server by selecting the Organizations node and then right click on your Organization name and choose properties.f.g. Then if you are creating a host record type in the IP address of the Microsoft Dynamics CRM Server and click Add Host, then click OK and click Done. If you are adding an Alias click Browse and add the Microsoft Dynamics CRM server and click OK.How to use the CRM40IFDToolSteps to run the tool1. Download the CRM4IFDTool from the following Microsoft KB article: support.microsoft./kb/9487792. On the computer that is running the server installation of Microsoft Dynamics CRM 4.0, extract the CRM4IFDTool to the following directory: 3. drive :Program FilesMicrosoft Dynamics CRMTools4. Run the CRM4IFDTool.exe tool.5.6. Click the Authentication Strategy list and click IFD+On Premise.7.8. Type the IP Address and the subnet. Note: The IP address is just an example of a valid IP address on the specific subnet. It does not have to be the IP address for the Microsoft Dynamics server. You can enter more than one subnet. The subnets you enter here will be for the computers that are internal and you do not want the users to login through the IFD environment when they are on these subnets.9. Click the IFD Domain Scheme list, and then click either or S.10. Type the IFD App Root Domain and IFD SDK Root Domain. This will only be the domain name. For example, type domain. or subdomain.domain.Note: The IFD settings will be how the client computers will access the Microsoft Dynamics CRM 4.0 Website when not logged on the local Intranet. The domain name entered here will be prefixed by the unique organization name to form the full URL of the IFD environment when the user is logging in.11. The AD Domain Scheme should already be filled in from when you installed CRM.12. The AD App Root Domain and AD SDK Root Domain will also already be filled in from when you installed CRM. However, you can use this tool to change them if needed.Note: Do not type or s as that is already selected in the AD Domain Scheme list.Note: The AD settings will be how the client computers will access the Microsoft Dynamics CRM 4.0 Website when logged on the local Intranet and not logging on through IFD.13. Click File, and then click Apply Changes.14.More InformationThe CRM4IFDTool tool will enable IFD for Microsoft Dynamics CRM 4.0. However, you must create the DNS record and verify the server and Microsoft Dynamics CRM 4.0 website are accessi