Installing CRM 2013

With the upcoming release of CRM 2013 and the current availability of the RC 1 build, thought I'd share the steps on how to get this installed.
Prerequisites
Windows 2008 Server x64 or Later
SQL Server 2008 x64 or Later

1. Launch the SetupServer.exe to start the install. Click Next

2. Here you can select the roles you want to install, for demonstration purposes I'm going to install all the roles on a single server. However it is strongly advised to separate roles across multiple computers to distribute processing load. Click Next

3. Select the "Create a new Deployment" option, then enter in the name of the SQL Server instance you want to use for this CRM 2013 deployment. Click Next

4. Select the OU you want to use for this CRM 2013 Deployment. Click Next

5. Specify the Service Accounts you want to use for each service listed. Click Next

6. Here you can decide if you want to install CRM to use the Default Website within IIS or create a new website with a specified port. Click Next

7. This is an optional step where you can specific the server name of the Email Router. If you plan to do this at a later stage, keep in mind that you will need to add the computer to the AD PrivUserGroup. Click Next

8. Enter in a unique name for the Database name, which will be used for the default CRM Organization name. Here you can also set the currency settings and SQL collation. Please note that the SQL collation cannot be changed later. Click Next

9. Enter in the URL to the SSRS report server. Click Next

10. Click Next

11. Select which option you want to use for Microsoft Updates and Click Next

12. The installer will perform the necessary system checks. You will notice a warning statement regarding Date encryption which is new to CRM 2013, this states: 

"Data encryption will be active after the install or upgrade. We strongly recommend that you copy the organization encryption key and store it in a safe place. For more information, see http://go.microsoft.com/fwlink/?LinkId=316366."

Click Next

13. Click Next

14. Confirm you are happy with all configuration settings and click Next

15. That's it, CRM 2013 is now installed successfully. Optionally you can install SSRS Reporting Extensions

CRM 2011 Installation Error - Setup failed to validate specified Reporting Services Report Server

When trying to install CRM 2011 in an environment where the SQL Server machine name has been changed, you may experience an error displayed below:

"Setup failed to validate specified Reporting Services Report Server"

You may have also experienced the issue The instance name must be the same as computer name

The  "Setup failed to validate specified Reporting Services Report Server" issue, is due to an incorrect server name being used by SSRS. 

1. To fix this, start the Reporting Server Configuration Manager and click on the Change Database option displayed below

2. Report Server Database Configuration Wizard

3. Click Next, you will see the server name being used

4. Correct the server name and use the Test Connection to confirm all is good

5. Select the Report Server Database

6. Click Next and wait for all tasks to complete

7. Click Finish and re-run the CRM Installer, now it should resolve the correct SSRS report server

CRM 2011 Installation Error - The instance name must be the same as computer name

Recently when installing CRM 2011, I came across an error I haven't seen in sometime. 
“The instance name must be the same as computer name.”

The cause of this error, was due to the SQL Server Instance machine name being changed. More Importantly the server name change was done after the SQL server software had been installed.

Fortunately the steps to rectify this are pretty simple as follows:

1. Connect to the SQL Instance using Management Studio and identify the current name

2. Next we need to drop this server name as displayed

3. Now we need to add the correct server name

4. Finally Restart the SQL Service Services

That's it, now when you re-run the installer and perform the system checks, the error should not appear.

CRM 2011 - Add/Remove Team Members

Records within CRM 2011 can be owned by either a User or a Team. 

Using Teams within CRM 2011 are a great way of sharing records between users whom:

• Are in different Business Units
• Do not have the correct security role against their User record
• Don't have ownership of the record(s) they want access too

However, the main benefit of Team ownership compared to User, is that ownership is shared by all members of the owning team, rather than a single user. Security Roles applied to that Team can elevate what a User can do when being a member.

An important part of maintaining this form of ownership, is to automate how members of a Team are added and removed, you may at times want to link certain UI actions to trigger these events. This can be done very easily from within a plugin as shown below:

127. /* Add Users to Team */
128. AddMembersTeamRequest addMembersTeamRequest = new AddMembersTeamRequest();
129. addMembersTeamRequest.TeamId = Guid.Parse("831F6F02-6947-46BC-BDDF-6571075569A9");    //Team
130. Guid[] arrMembers = new Guid[] {
131.   new Guid("A4349C86-6475-43E6-BC1D-C3244115107C"),                                   //User 1
132.   new Guid("8121CF3B-93B4-4907-9888-46FFAA11A169")                                    //User 2
133. };
134. addMembersTeamRequest.MemberIds = arrMembers;
135. AddMembersTeamResponse addResponse = (AddMembersTeamResponse)ServiceProxy.Execute(addMembersTeamRequest);
136.  
137. /* Remove Users from Team */
138. RemoveMembersTeamRequest removeMembersTeamRequest = new RemoveMembersTeamRequest();
139. removeMembersTeamRequest.TeamId = Guid.Parse("831F6F02-6947-46BC-BDDF-6571075569A9"); //Team
140. arrMembers = new Guid[] {
141.   new Guid("A4349C86-6475-43E6-BC1D-C3244115107C"),                                   //User 1
142.   new Guid("8121CF3B-93B4-4907-9888-46FFAA11A169")                                    //User 2
143. };
144. removeMembersTeamRequest.MemberIds = arrMembers;
145. RemoveMembersTeamResponse removeResponse = (RemoveMembersTeamResponse)ServiceProxy.Execute(removeMembersTeamRequest);