How to setup load balanced SSRS Servers for CRM 2016

While not very common, there are times when a customer or client requests two servers for the CRM SRS data connector/SSRS to be installed and have load balancing configured for the servers. The idea here is failover; when one server hosting SSRS crashes, all incoming requests are routed to the secondary server. There are a couple of ways to do this, but the following method is the most straightforward and simplistic way.

1.    Create a Virtual IP(VIP) to route to each SSRS server.

In order for this method to work, a virtual IP will need to be created. The virtual IP will accept incoming data packets, then route the requests to each of the IP addresses of the physical servers that will have SSRS installed.

2.      Install and configure SSRS on each server.

Install and configure SSRS on each server as you typically would by pointing to the SQL server and/or instance where you would like the report server databases to be located.

3.    Install the CRM SRS data connector on each server.

Grab the installation files for your respective version of CRM and install the data connector on both servers. Install the data connector as you would for a typical CRM deployment.

4.      Configure the host file on each SSRS server.

On both SSRS servers, open the host file: C:\Windows\System32\Drivers\etc\hosts. Edit the host file by adding the IP and DNS name of the virtual IP created in step 1:










5.      Add the BackConnectionHostNames registry key with the server name and FQDN.

Open Registry Editor on one of the SSRS servers, and locate the following registry key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\MSV1_0.

Right click MSV1_0, point to New and then click Multi-String Value. Type BackConnectionHostNames, then press ENTER.

Right click BackConnectionHostNames, then click Modify.

In the Value data box, type the host name of the VIP and FQDN of the VIP, and click OK.








Repeat these steps for the other SSRS server.

6.      Add hostname and URL root values.

On one of the SSRS servers, make a backup of the reportserver.config file located here: C:\Program Files\Microsoft SQL Server\MSRS11.MSSQLSERVER\Reporting Services\ReportServer.

Right click the original reportserver.config file and choose edit.

Modify the hostname and URL root tags of the .xml file located under the service tag by adding the FQDN of the VIP as shown below:



Save the file after making the changes.

Repeat these steps for the other SSRS server.

7.   Restart both SSRS servers.

8.   During the import or new creation of an organization in CRM, specify the name of the VIP.

Use the VIP created in step 1 when prompted for the reporting services URL during a new org creation or an org import:

ADFS setup error when using CRM 2016 and ADFS and Windows 2012 R2

An error occurred. Contact your administrator for more information” error when accessing CRM with ADFS/IFD set up.
After completing ADFS/IFD setup where ADFS is installed on a Windows Server 2012 R2 machine, you receive the below error:

 To resolve this issue you must enable Forms Authentication:

1.       Connect to the ADFS server

2.       Open the ADFS management console and click Authentication Policies







3.       Under Primary Authentication, click Edit next to Global Settings






4.    Put a check mark in the Forms Authentication option on the Extranet and Intranet sections

















5.    Click OK

6.       You should now be able to log in to CRM successfully

Thanks to Ian Holton, Client Field Engineer at Tribridge for putting this together!

Join me at CRMUG Summit in Reno NV October 13-16

Join me at the CRMUG Summit In Reno NV. This is the premier Dynamics CRM Event of the year. Don’t miss out, not too late to register below.



More details..

Here’s my preliminary schedule. Please refer to the website!

Monday, October 12

8:00pm-10:00pm @ Peppermill – Terrace Lounge Chapter Leader Bash

Tuesday, October 13

2:00pm-4:30pm @ Atlantis: Paradise D & E Volunteer Immersion at CRMUG Summit
5:00pm-8:00pm @ Hall 2 Welcoming Expo Reception

Wednesday, October 14

7:00am-8:00am @ Hall 1 Breakfast – Jump Into a Great Day
9:15am-9:45am @ Ballroom Lobby Networking Break
9:45am-10:45am @ D2 Getting Ready to Pull the CRM Trigger
11:15am-12:25pm @ C4 CRMUG Opening General Session – Microsoft Keynote
1:30pm-2:30pm @ D4 The CRM Superhero’s Tips, Tricks, and Toolbox
1:30pm-2:30pm @ D2 Scouting & Preparing as CRM GameDay Draws Near
2:30pm-3:00pm @ Ballroom Lobby Networking Break
4:00pm-4:30pm @ Ballroom Lobby Networking Break
4:30pm-6:00pm @ D2 ADFS & Upgrading with a Mobile State of Mind
6:00pm-8:00pm @ Hall 2 Expo Reception

Tribridge Customer Party – Invitation Only 7pm on..

Please contact me if your a customer or prospect and did not receive an invitation.

Thursday, October 15

7:00am-8:00am @ Hall 1 Breakfast – Jump Into a Great Day
8:00am-9:00am @ D2 Getting that CRM Upgrade to Purr Like a Kitten
9:00am-9:30am @ Ballroom Lobby Networking Break
10:30am-11:00am @ Ballroom Lobby Networking Break
11:00am-12:00pm @ C4 CRMUG General Community Session
12:00pm-2:00pm @ Halls 1 & 2 Networking Lunch and Expo
2:00pm-3:00pm @ D7 Going OnPremise to CRM Online
2:00pm-3:00pm @ C1 Take It to the Next Level with End User Experience Upgrades in CRM 2015
3:00pm-3:15pm @ Ballroom Lobby Networking Break
3:15pm-4:15pm @ D4 Ask the MVPs: Admin-Foundation Edition
3:15pm-4:15pm @ D7 Ask the Experts – User Adoption Edition: Enterprise CRM Strategies and Pitfalls to Avoid
4:15pm-4:45pm @ Ballroom Lobby Networking Break
4:45pm-5:45pm @ D2 Dissecting Multifaceted CRM Upgrades

Friday, October 16 – CANCLLED

8:00am-9:15am @ D2 Deployment Method of Choice  CANCELLED



Gearing up for Orion.. Are you ready to take the plunge?

The Microsoft CRM Product Team has been hard at work getting ready to deliver CRM “Orion” to the masses. We have heard we will receive the preview releases to begin testing very soon – (NDA-Safe :). We have also heard that Microsoft support was also training on the Orion Release. From Convergence 2013, there’s a lot of items we need to consider when getting ready Orion!

Remember, if you’re running CRM 3/4 you will still have to upgrade to CRM 2011 BEFORE moving to ORION.

Here’s my short list:

1. CRM namespace (jscript with crm.XXX) will no longer work and has been fully depreciated.)

2. Design Considerations for implementing the Process Flow UI – have you seen the process flow
UI available with (CRM Online code name Polaris)? If not, setup a trial or review my Convergence
debrief for screen shots. Sales users absolutely love the new Process Flow UI, great performance gains,
auto saves and one place instead of navigating to leads, accounts and contacts when working on an
opportunity. But consider how your business process can be revised in your existing CRM solution
to take advantage of this feature and the new form design. I expect that new features would only
be available to these new forms similar to the previous CRM Online Polaris release.

3. Consideration for running on SQL 2012 – CRM 2011 supports both 2008/2012 but for your new launch
consider migrating your servers to the latest releases.

4. Consideration for Windows Server 2012 – CRM 2011 supports both 2008/2012 but for your new launch
consider migrating your servers to the latest releases. ADFS 2.1 is also provided for Windows Server 2012,
but be currently not compatible with Online to OnPremise ADFS Federation if needed. (Use ADFS 2.0).

5. Remember to setup your test and development environments first! You will want to completely test this
rollout before deploying to your production servers. Also keep in mind that you need support your existing
CRM installation so a new development environment would be a good choice while you work thru testing Orion.

Stay tuned for more exciting announcements, screen shares and updates as we get closer!

Update Rollup 13 – Self Healing .MSP Patch Location CRM 2011 Install on Windows Server 2012

Installing CRM 2011 on Windows Server 2012 requires to use the Microsoft Self healing Process – manual patch that you download from the Windows Catalog. I searched all over and had a hard time finding it. Thanks to my good friend Corey Hanson at Microsoft for providing a direct link to the patch. The patch is listed on the KB article under manual installation, but its a bit unclear for those looking for the Self Healing Patch.

Once you download the patch, add this to a directory on the CRM server. You will then run a command line install of CRM 2011 in order to have the installer use this patch. The CRM 2011 setup program will be updated upon release of Update Rollup 14, no longer requiring this manual patch for installing on Windows Server 2012. Instruction on how to create the configuration file and use the patch can be found here:
Example Sample Config.XML File – Save as XML – Do not save as TXT and rename.

Running from the command line:

Some more Gotchas:
Apparently, your must expand/unzip this file on a Windows 7 or Windows 8 machine, and then copy it over to the Windows 2012 Server. I kept getting messages that this patch will not work on this application and the serversetup.log file stated it was an invalid windows installer package.



Once I expanded (you can extract via right click too!) on my Windows 8 machine, and copied it over, everything worked like a charm.  This should save some people a few hours of scratching their heads..