Introduction

This guide is a step by step "with pictures of the installation process of Dynamics CRM Server 2011 on a stage 'typical' and extends from the stage of preparing the necessary prerequisites to installation and post-installation tasks of the product.

It is an adaptation of the original series of 6 articles " Installing Microsoft Dynamics CRM 2011 "published inelblogdeDynamicsCRM.com and is based on the deployment guide Dynamics CRM 2011 available for free here.

In any case, this guide replaces the Installation Manual on the Implementation Guide, which is the official guide to Microsoft Dynamics CRM platform 2011.

Preparation. Pre-installation requirements

Below are the different checks Hardware and Software to be made ​​to install the Microsoft CRM application 2011.

The installation is based on a typical architecture of distributed product installation:

• A Dynamics CRM server 2011 with all roles (full installation)
• A server for SQL Server 2008/2008 R2 with the database engine and SQL Server Reporting Services.
• An existing Active Directory within the organization and the two older servers belonging to the same domain.

Hardware Requirements

Dynamics CRM Server 2011

These are requirements only for Dynamics CRM Server 2011 , based on an estimate of load up to 320 users:

Component	* Minimum	* Recommended
Processor	x64 architecture or compatible 1.5 GHz dual-core processor	Quad-core x64 architecture CPU 2 GHz or higher Such as Intel Xeon or AMD Opteron systems
Memory	2-GB RAM	8-GB RAM or more
Hard disk	10 GB of available hard disk space Note Computers with More Than 16GB of RAM will require more disk space for paging, hibernation, and dump files.	40 GB or more of available hard disk space Note Computers with More Than 16GB of RAM will require more disk space for paging, hibernation, and dump files.

SQL Server 2008/2008 R2 Server

These are requirements only for SQL Server on the same basis as above.

Component	* Minimum	* Recommended
Processor	x64 architecture or compatible 1.5 GHz dual-core processor	Quad-core x64 architecture CPU 2 GHz or higher Such as Intel Xeon or AMD Opteron systems
Memory	4-GB RAM	16-GB RAM or more
Hard disk	SAS RAID 5 or RAID 10 hard disk array	SAS RAID 5 or RAID 10 hard disk array

Software Requirements

Dynamics CRM server 2011

• Windows Server 2008 [Standard | Enterprise | Datacenter] (x64) with SP2 or Windows Server 2008 R2 (x64).
  (Also supported the Web and Small Business versions - x64)
• Language : English or the same as Dynamics CRM (if we will install the base version Spanish)
• IIS 7.0 | 7.5
• Services raised
  • Indexing Service
  • IIS Admin
  • World Wide Web Publishing
• Windows Data Access Components (MDAC) 6.0 (default would be the version of MDAC on Windows Server 2008.)
• Microsoft ASP. NET (registration, no need to be running)
• This server must be in the same domain as the SQL Server.

SQL Server 2008/2008 R2 server

• Windows Server 2008 [Standard | Enterprise | Datacenter] (x64) with SP2 or Windows Server 2008 R2 (x64).
• Microsoft SQL Server 2008 [Standard | Enterprise | Datacenter] (x64) with SP1 or sup. Or SQL Server 2008 R2 (x64) .
  (May also be the Developer edition for non-production environments)
• Language : English or the same as Dynamics CRM (if we will install the base version Spanish)
• The SQL must be configured for automatic startup
• SQL Server Reporting Services (can be installed on another SQL Server with these characteristics, but typically uses the same instance)
• The Reporting Services service must be configured for automatic startup
• SQL Server Agent service up
• SQL Server Full Text Indexing raised
• This server must be in the same domain as the Dynamics CRM.

Client for Outlook

• Supported operating systems
  • Windows 7 (Both 64-bit and 32-bit versions)
  • Windows Vista (Both 64-bit and 32-bit versions)
  • Microsoft Windows XP Professional SP3
  • Microsoft Windows XP Tablet SP3
  • Windows XP Professional x64 Edition
• Internet Explorer 7 / 8
• Office 2010 | 2007 | 2003 with SP3
• Indexing Service (installed and running)
• The following components are not installed if the installer automatically installs:
  • Microsoft SQL Server 2008 Express Edition (only if you require access Offline)
  • Microsoft. NET Framework 4.0
  • Microsoft Windows Installer (MSI) 4.5.
  • MSXML 4.0
  • Microsoft Visual C + + Redistributable
  • Microsoft Report Viewer 2010
  • Microsoft Application Error Reporting
  • Windows Identity Framework (WIF)

Credentials

• Required for installation of Dynamics CRM 2011
  • Domain administrator .
  • If you can not be domain administrator privileges are minimal:
    • Member of Active Directory Domain Users
    • Permissions to create security groups in Active Directory (alernatively you can ask an administrator to pre-create the required security groups; you must then install Microsoft Dynamics CRM 2011 from the command line specifying a configuration file).
    • Member of the Administrators group on the computer where you install the CRM
    • Read and write permissions on the folder 'Program Files' on that computer
    • Member of the Administrators group on the computer where SQL Server installed
    • SQL Server sysadmin server.
    • Reporting Services
      • Content Manager root level
      • System administrator for site-wide SSRS
• To run services
  • Important
    • The credentials used to run the services of Dynamics CRM and IIS App Pool can not be users of Dynamics CRM because it could cause problems and unexpected behavior of authentication.
    • The account that is installed Dynamics CRM 2011 should be different from the account or accounts with the service running for the same reasons.
    • The 2011 CRM installation fails if the SQL Server service is running with local administrator account.
    • Services can run with NETWORK SERVICE. However, this is not a good security practice and also operates at the level of organization through service Deployment Windows PowerShell or fail.
    • If you use domain accounts would only be necessary to create them in AD. The setup of Dynamics CRM will automatically assign the necessary privileges.
    • To avoid creating and managing multiple accounts can use the same for all services, although this is not the best security practice especially considering the service Web Service Deployment .
  • Microsoft Dynamics CRM Sandbox Processing Service
    • Domain User
    • Logon as a service in the Local Security Policy
    • Reading and writing in the folder \ Trace , by default located under \ Program Files \ Microsoft Dynamics CRM \ Trace , and the user folders under% AppData% in local máqiuna.
    • Read permissions on the key 
      HKEY_LOCAL_MACHINE \ SOFTWARE \ Microsoft \ MSCRM
  • Microsoft Dynamics CRM Asynchronous Processing
    • Domain User
    • You must be a member of Performance Log Users
    • Logon as a service in the Local Security Policy
    • Reading and writing in the folder \ Trace , by default located under \ Program Files \ Microsoft Dynamics CRM \ Trace , and the user folders under% AppData% in local máqiuna.
    • Reading and writing in keys 
      HKEY_LOCAL_MACHINE \ SOFTWARE \ Microsoft \ MSCRM 
      and subkeys 
      HKEY_LOCAL_MACHINE \ SYSTEM \ ControlSet001 \ services \ MSCRMSandboxService
  • Web Deployment Service (CRMDeploymentServiceAppPool Application Pool identity)
    • Domain User
    • Logon as a service in the Local Security Policy
    • Member of Local Administrators group on the server where you installed the web services
    • Member of Local Administrators group on the SQL Server server
    • Permissions on the SQL Sysadmin
    • Reading and writing in the folder \ Trace , by default located under \ Program Files \ Microsoft Dynamics CRM \ Trace , and the user folders under% AppData% in local máqiuna.
    • Reading and writing in keys 
      HKEY_LOCAL_MACHINE \ SOFTWARE \ Microsoft \ MSCRM 
      and subkeys 
      HKEY_LOCAL_MACHINE \ SYSTEM \ ControlSet001 \ services \ MSCRMSandboxService
    • Group member CRM_WPG . This group is created automatically during the installation of Dynamics CRM and membership also.
  • Application Service (IIS Application Pool identity CRMAppPool)
    • Domain User
    • You must be a member of Performance Log Users
    • Member of Local Administrators group on the SQL Server server
    • Member of Local Administrators group on the server where you installed the Dynamics CRM web site
    • Reading and writing in the folder \ Trace , by default located under \ Program Files \ Microsoft Dynamics CRM \ Trace , and the user folders under% AppData% in local máqiuna.
    • Reading and writing in keys 
      HKEY_LOCAL_MACHINE \ SOFTWARE \ Microsoft \ MSCRM 
      and subkeys 
      HKEY_LOCAL_MACHINE \ SYSTEM \ ControlSet001 \ services \ MSCRMSandboxService
    • Group member CRM_WPG . This group is created automatically during the installation of Dynamics CRM and membership also.
  • SQL Server
    • Domain account running SQL Server. (You can also run in NETWORK SERVICE and LOCAL SYSTEM)
    • The account can not be the local administrator.

Ports

Dynamics CRM server

These are the ports that are used in a full installation (all roles of CRM installed on the same server)

Protocol	Port	Description	Explanation
TCP	80	HTTP	Default Web application port. This May Be Different port as it changed DURING Can Be Microsoft Dynamics CRM Server Setup. For new websites, the default port number is 5555.
TCP	135	MSRPC	RPC endpoint resolution.
TCP	139	NETBIOS-SSN	NETBIOS session service.
TCP	443	HTTPS	Default HTTP secure port.
TCP	445	Microsoft-DS	Active Directory directory service Active Directory required for access and authentication.
UDP	123	NTP	Network Time Protocol.
UDP	137	NETBIOS-NS	NETBIOS name service.
UDP	138	NetBIOS-dgm	NetBIOS datagram service.
UDP	445	Microsoft-DS	Active Directory Active Directory service required for access and authentication.
UDP	1025	Blackjack	DCOM, used as an RPC listener.

Server SQL Server / SQL Server Reporting Services

These are the ports that are used on the server that has reporting services installed Dynamics CRM Reporting Extensions.

Protocol	Port	Description	Explanation
TCP	135	MSRPC	RPC endpoint resolution.
TCP	139	NETBIOS-SSN	NETBIOS session service.
TCP	445	Microsoft-DS	Active Directory Active Directory required for access and authentication.
TCP	1433	ms-sql-s	SQL Server sockets service. This port is required for access to SQL Server.This number May Be Different if You Have configured your default instance of SQL Server to use a port number or Different Are you using a named instance.
UDP	123	NTP	Network Time Protocol.
UDP	137	NETBIOS-NS	NETBIOS name service.
UDP	138	NetBIOS-dgm	NetBIOS datagram service.
UDP	445	Microsoft-DS	Active Directory Active Directory service required for access and authentication.
UDP	1025	Blackjack	DCOM, used as an RPC listener.

Server Location [Dynamics CRM, SQL and AD]

Microsoft Dynamics CRM data stores all customer relationship management (CRM) in a database SQL Server. It is important that the computer running SQL Server is located close to the Microsoft CRM server. This means that there must be a high-speed network standing between the team of Microsoft CRM server and the computer running SQL Server to have an efficient performance of Microsoft CRM. An error in the network communications between computers running Microsoft CRM Server and SQL Server can cause data loss and service can no longer be available.

The same applies to Active Directory. Microsoft CRM depends on Active Directory for security information. If you lose communication with Active Directory, Microsoft CRM will not work correctly. If communications with Active Directory are not effective, will be affected the performance of Microsoft CRM. It is therefore important to locate a domain controller for Active Directory on the same network connection speed permanent than computers that run Microsoft CRM and Microsoft SQL Server.

2011 Dynamics CRM installation

Once treated the prerequisites mentioned in the previous section, proceed to install the product, which is described in detail in this section.

We begin with a section devoted to the installation of SQL Server 2008/2008 R2 if the case is not yet installed.

Installing SQL Server 2008/2008 R2

1. If you have not already installed, first install SQL Server 2008 / 2008 R2 64 bits. 
   
2. Ensure that the required ports are allowed at the firewall. 
   

   Protocol	Port	Description	Explanation
   TCP	135	MSRPC	RPC endpoint resolution.
   TCP	139	NETBIOS-SSN	NETBIOS session service.
   TCP	445	Microsoft-DS	Active Directory Active Directory required for access and authentication.
   TCP	1433	ms-sql-s	SQL Server sockets service. This port is required for access to SQL Server.This number May Be Different if You Have configured your default instance of SQL Server to use a port number or Different Are you using a named instance.
   UDP	123	NTP	Network Time Protocol.
   UDP	137	NETBIOS-NS	NETBIOS name service.
   UDP	138	NetBIOS-dgm	NetBIOS datagram service.
   UDP	445	Microsoft-DS	Active Directory Active Directory service required for access and authentication.
   UDP	1025	Blackjack	DCOM, used as an RPC listener.

3. When installing SQL Server, choose at least the following (assuming that the Reporting Services will run on the same server as SQL) 
   
4. Establish the service accounts for the various SQL services. We recommend using a domain account or otherwise, NETWORK SERVICE. Leveraged to configure automatic startup of services and it will be necessary for both SQL Server, SQL Server Agent as the Full Text Indexing are raised at the time of installation of Dynamics CRM.
   
5. Select the authentication mode. With Windows Authentication Mode is sufficient for the purposes of Dynamics CRM as it is used.
   
6. Reporting Services installation must be in native mode (native mode) . This is the only way in which CRM can work. 
   
7. Continue the wizard steps to begin the installation and wait for it to complete successfully: 
   
8. Corroborated by opening the SQL Server Management Studio that everything is OK, they are the basis for Reporting Services and SQL Server Agent up: 
   

Installing pre-requisites in Dynamics CRM server 2011

1. If IIS (Internet Information Services) is not installed on Windows Server 2008 server, add the role Web (IIS) as shown below: (if you do not see this option when you start your server, you can add new roles by clicking on Start-> Administrative Tools-> Server Manager )
   
2. Among the components of IIS, select 'ASP.net'. It is likely that a new dialog appears asking for confirmation to add other roles required for this.
   
3. Also select 'Management Service' and 'IIS 6 Management Compatibility' under 'Management Tools' and 'Windows Authentication' under 'Security'
   
4. "IIS 6 Management Compatibility ' is required to register and raise the service 'IIS Admin' required by the installation of Dynamics CRM.
   
   Proceed with the installation until the end of it successfully .. 
   
   
5. If Indexing Service is not registered as a service, we install it and raise it as follows: Start-> Administrative Tools-> Server Manager
   
6. Select the role 'File Services'
   
7. In the next step, choose the service 'Indexing Service' under 'Windows Server 2003 File Services "
   
8. Continue the wizard to successfully complete the installation: 
   
   
9. If previous installations were correct (these components are already installed), should have the following installed services and raised:
   • IIS Admin Service
   • Indexing Service
   • World Wide Web Publishing 
     
     
     These 3 services are required to be installed and erected at the time of installation.

2011 Dynamics CRM installation

1. After satisfying the requirements, go to the directory or the installation media Dynamics CRM 2011 at the route: 
   \ Server \ amd64 \ SetupServer.exe
2. By the way, the implementation is recommended to do it with 'Run as Administrator' 
   
3. In the first step, the setup will ask if we are to seek and obtain pre-install updates, which is recommended. 
   
4. To be very recent release of version 2011, updates are not yet there but probably later. 
   
5. The next step is to enter the product key . You can use the Trial version key and then within 90 days of change for the corresponding key. The key trials are:
   • Microsoft Dynamics CRM Workgroup Server 2011 (5 CAL limit): 
     H84KC-JH8DF-7PDYK-TXBXR-2RMMT
   • Microsoft Dynamics CRM Server 2011 (no CAL limit): 
     MQM2H-JYYRB-RRD6J-8WBBC-CVBD3 
     
6. Accept the license terms: 
   
7. Automatic installation of components required . These components come with the installation media Dynamics CRM setup 2011 and automatically checks if they are already installed and failing, to install from here, pressing the 'Install'.
   
   
8. Once successfully installed all components, press 'Next' to continue with the next step. 
   
9. Indicate the folder where the files will stay the application. 
   
10. Indicate the roles of Dynamics CRM 2011 to be installed. By default, the setup suggests a Full installation is that we are addressing here, and generally being a typical case (except where there really is a load of users and transactions to justify distribute work on different servers).
    
    
    Then leave all roles selected as suggested by the setup.
11. Provide the SQL Server server containing the databases to the system. This is the name of SQL Server 2008/2008 R2 we installed earlier for this purpose or an existing one. Recall that the server must belong to the same domain as the server you are installing Dynamics CRM. For a new installation of Dynamics CRM, we selected the option 'Create a new deployment . "
    
12. Identify Active Directory Organization Unit that will contain the groups required for Dynamics CRM system 2011. You can specify the root directory if you want.
    
13. Indicate the service accounts to be used for different services Dynamics CRM 2011. We recommend using a domain account. If you use domain accounts would only be necessary to create them in AD are not yet created. The setup of Dynamics CRM will automatically assign the necessary privileges. It is important to remember here:
    • The credentials used to run the services of Dynamics CRM and IIS App Pool can not be users of Dynamics CRM because it could cause problems and unexpected behavior of authentication.
    • The account that is installed Dynamics CRM 2011 should be different from the account or accounts with the service running for the same reasons.
    • The 2011 CRM installation fails if the SQL Server service is running with local administrator account.
    • Services can run with NETWORK SERVICE. However, this is not a good security practice and also operates at the level of organization through service Deployment Windows PowerShell or fail.
    • If you use domain accounts would only be necessary to create them in AD. The setup of Dynamics CRM will automatically assign the necessary privileges.
    • To avoid creating and managing multiple accounts can use the same for all services, although this is not the best security practice especially considering the service Web Service Deployment .
      
14. The next step is to select the website that hosts the Dynamics CRM Web application. Here you can use the default website (port 80) or create a completely new website on another port. Unless there is any reason not to install in the default website, leave it as is because among other advantages, will be much easier for users to access by not having to remember a port number. If you plan on creating an Internet Facing Deployment (IFD) and need to install ADFS on the same server as CRM you should choose to install CRM to a new web site. ADFS is required to be installed to the default web site. 
    
15. Specify whether we are using the component E-mail Router for Dynamics CRM on another server, the file name. Most likely, this is not because of what in most cases simply leave this blank .
    
16. Specify the name of the organization and the base currency . The organization's name represents the name of the company. The base currency indicates the currency will default to monetary transactions and records to be made ​​within the application (for example, the return value of a business opportunity).It is the currency as the basis for reports and for conversions from other currencies.
    
17. Indicate Reporting Services 2008/2008 Server R2 to use. This is the server installed and configured earlier for this purpose or may be others that have been installed in native mode (default mode SSRS installation.) Suggests automatically setup the server path which typically is correct. Anyway, we can verify and test in a separate Internet Explorer window. It is worth noting that the path is required here is the the ReportServer and not the ReportManager. 
    
    
    Important: 
    
    Make sure the account you are installing Dynamics CRM 2011 is explicitly added in the local Administrators group on SQL Server server where Reporting Services. Even as Domain admin can originate from the error 'rsAccessDenied'. Just 'auto-adding' to the local administrators group, the error disappears.
    
    Also make sure that port 80 (default port where you install Reporting Services) to accept connections s incoming firewall settings on the server SQL Server Reporting Services. If everything is correct, when we put the path of ReportServer in Internet Explorer from the server you are installing CRM, you should see something like the following:
    
18. The next step is to indicate if we participate in the Customer Experience Improvement Program. 
    
19. Indicate if you want to use Microsoft Update to keep updated our CRM server 2011. The recommendation here is unless there is a very good reason not to, take advantage of Microsoft Update which is one of the great innovations and advantages of this version of Dynamics CRM.
    
20. The setup makes a check of the system before proceeding with the installation. Here we will see if everything is OK and / or have some error or warning to address.
    
    If you've followed all the steps above should have everything OK here or how much less a warning such as Sandboxing service that indicates that you are using the same service account that the other services, which is not the best security practice. Anyway, this does not pose a major issue in most scenarios by which we will continue.
21. Here, the setup simply indicates the services that can be stopped and restarted during installation. 
    
22. Here is a summary of preferences before proceeding to install. If we agree, we should simply press 'Install'
    
23. Installation begins ... 
    
24. If everything flows correctamante in the end the setup displays the following dialogue: 
    
25. To finish we must press on 'Finish' and wait for the server is restarted.
26. After rebooting the system should be available for access. We can simply open an Internet Explorer window and go to the path where it was installed. If the installation was the default website, the path would be: http:// <servername> <servername> where is the server name. By charging we find a page like this (no data):
    
27. We may charge you automatically sample data that can help us in displays / analysis / requirements gathering, etc.. To do this, we must go to Settings-> Data Management and click on Sample Data :
    
28. Clicking on Sample Data will open a new dialogue that will allow us to install the sample data or remove if any are already installed. 
    

Post-Installation.

Although so far we have successfully installed the product, we still have one more step to work with reports, view them and create our own reports. Also, if we operate the system in Spanish, we proceed to install the language pack (language pack) accordingly. This section will describe these activities.

Installing Microsoft Dynamics CRM Reporting Extensions

That step is to install Reporting Services extensions to Dynamics CRM, which is performed on the server SQL Server Reporting services by following these steps :

1. Within the SQL Server Reporting Services has run SetupSrsDataConnector.exe which is under the folder \ Server \ amd64 \ SrsDataConnector in the middle of Dynamics CRM installation 2011. By the way, run the installer with a 'Run as Administrator'
   
2. Like the 2011 installer Dynamics CRM Server, the setup asks if you want to check if updates are available for download and apply before proceeding with the installation. This is recommended to leave the system to check this. Since the release of the product is very recent, when there are no updates, but it is likely that in the future do exist and we should check this.
   
   
3. We accept the licensing terms: 
   
4. The installer identifies the components required to install automatically and allows so much as we did with the previous installation of Dynamics CRM. Then pressed 'Install' to automatically install these components.
   
   
5. Components installed successfully we are able to continue, press 'Next'
   
6. Wait a few seconds until a new dialogue. This can take several seconds .
7. In this step we must specify the SQL Server server that contains the Dynamics CRM database. Surely it is the same for Reporting Services where we are performing this installation. So write your name and press 'Next'.
   
8. Next we must specify the instance of SQL Server Reporting Services to use. Probably the suggestion that we be the only and correct, so click on 'Next' to continue.
   
9. As with the installer for Dynamics CRM, this can indicate whether you wish to use Microsoft Updateto keep current components. The recommendation here is the same: unless there is a very good reason not to, take advantage of Microsoft Update which is one of the great innovations and advantages of this version of Dynamics CRM.
   
10. Specify the path where the files will stay. 
    
11. Before proceeding, check your system setup. If there is an error and / or warning, the installer will indicate to us here.
    
12. In this step, the setup tells us that the SQL Server Reporting Services will probably be stopped and restarted during the installation process. 
    
13. In this step, the setup provides us with an overview of the system parameters in order to proceed with it. If we agree simply click on 'Install' to begin the installation.
    
14. Start the installation .. 
    
15. If the installation was successful you should see the end the following dialogue: 
    
16. Got here, and our reports should work. Let us check this by accessing the area of Dynamics CRM reports. To do this in the area of ' Workspace 'click on' Reports '. If everything is OK, we should now see the list of available reports. 
    
    We can open any of them and run to finish to confirm that everything is working correctly. 
     
    
    
    

Installing the language pack for Spanish

So far we have fully installed Dynamics CRM 2011 and what remains for us is putting on the Spanish language pack for our users to use the system in this language instead of the base language (English in this case).

We can also perform an installation base directory being the Spanish language if we wish, provided that both the operating system and SQL Server are in Spanish or otherwise, in English. Eg if the Windows Server 2008 is the Portuguese can not do an installation of Dynamics CRM 2011 in Spanish, but that we do in English or Portuguese.

In essence, there are substantial benefits to justify installing it directly in Spanish beyond the customization of entities can be done only in the base language. The end user will not notice any difference.

It is worth mentioning that the language pack must be installed in both Dynamics CRM server and client using Outlook (except to install the Outlook client from the Web CRM via the button 'Get CRM For Outlook' and are working on Spanish).

However, the steps for installing the Spanish language pack on the server, are :

1. Download language pack from here . (File CRM2011-Mui-XXX-amd64.exe) Important to note that prior to downloading the package we select the language in the combo "Change Language." and press the button 'Change'
   
2. After downloading the package, start the installation. In the first step we asked to select a folder where you unzip the package contents.
    
   
3. After extraction, the installation automatically starts and asks us to accept the license terms and pressures on 'Install' to continue.
   
4. Start the installation .. 
   
5. The installation continues and completes successfully. Press 'Finish' 
   
6. We must first enable the language to later users (including ourselves as managers) to choose. To do this, logged in as administrator in Dynamics CRM must go to Settings-> Administration and click on 'Languages ​​'. 
   
7. Opens a new dialogue in which we will be able to choose 'Spanish' 
   
8. Click on ' Apply 'to enable the language pack. There is a new confirmation dialog asking and letting us know that the operation may take a few minutes ..
   
9. Click on 'OK' to enable packet ... 
   
10. The language pack must change their status to ' Enabled '(enabled)
    
11. This package enables only the language. Still we make the change. To make the change from the CRM Web application must click on File-> Options in the Ribbon.
    
12. In the Options window, go to tab 'Languages'
13. Indicate where the language "Spanish" for both the graphical interface to help. 
    
    The language base (Base Language) is English and is shown for informational purposes only, read-only and can not be changed once created the organization.
14. We press OK to apply the change.
15. Now automatically refreshes the graphical interface and we should see it in Spanish. 
    
16. Keep in mind that as managers if we want customized bike builders entities and / or create solutions, this can only be logged if you are working with the base language (English in this case).Therefore, we ought to change the language if is that we leave our default user configured with Spanish. Otherwise, these options are available as shown in the following figures:
    
    

I hope you have found the guide useful. You can access this guide step by step at elblogdeDynamicsCRM.com.