system center 2012 r2 service manager moving the data warehouse management server and reporting

by Nathan

(Hopefully) Useful Information on Microsoft System Center, Hyper-V and Cloud Previous PostNext Post 3David AllenSystem Center 2012 R2 Service Manager – Moving the Data Warehouse Management Server and ReportingPosted on May 3, 2015Evening All,As it’s a nice quiet bank holiday weekend, I thought I would take the opportunity to write up my experience this week with attempting to move the Data Warehouse Management Server and the Reporting Server in my Service Manager management group.The reason for wanting to move these components was to move all onto a newly implemented Hyper-V platform, as well as to reclaim Enterprise SQL licenses that had been incorrectly used during the initial installation.  First of all, I had to move all the databases for Service Manager to new SQL Servers, which was accomplished successfully following the guides available on TechNet,  After this was completed, I relaxed a bit and thought that that was the difficult bit over with, now to simply move the management servers, DW management server, and reporting.To “move” the management servers to new servers wasn’t a problem, as expected, as I just installed new management servers on the new Hyper-V platform and then decommissioned the old ones.  The DW MS and Reporting Server, however, turned out to be a very different story.My first inclination that moving these components may be difficult was when I tried to look up Microsoft guides on how to do so, and couldn’t really find anything.  I couldn’t find anything at all on moving the Reporting Server, and I could only find a guide on recovering a Data Warehouse Management Server, which is here,, and on further investigation is itself lacking important information for a successful recovery.So, to start with I thought I would use the DW MS recovery guide to try and install a new DW MS with a new Reporting Server.  I followed the guide exactly, changing the ReportServer URL to the new URL from the new Reporting Server, however I just couldn’t get the DW MS to install.  After some investigation through the logs, and discussion with Microsoft, it turns out that if you want to install the DW MS on a new server, the new server must have the same name as the original server, as the encryption key contains host name information.  This extremely important piece of information is omitted from the recovery guide!!Then, I started to look at how I could implement a new Reporting Server, and the same thing applied; you must use a new server with the same as the original, and it must be the restored Report Server instance from the original, as reports will not redeploy from Service Manager.With all this information, I was able to put together a step by step guide on how to put the DW MS and Reporting Services on a new server: Get details of all service accounts used by the DW management group, as the re-installation must use the same service accounts.Backup the DW encryption key from the DW MS, if not already done so ( the Data Warehouse Management Server from the original server.Shutdown the Data Warehouse Management Server.Backup the SQL Reporting Services databases and encryption key ( server hosting SQL Reporting Services.Start the new server to host SQL Reporting Services – this server must have the same computer name as the original server.Install a SQL Reporting Services instance on the new server with the same instance name as the original.Configure SQL Reporting Services for Remote SQL Server Reporting Services, following this guide, the new server to host the Data Warehouse Management Server which must have the same computer name as the original.Restore the DW Management Server encryption key on the new server.Install the DW Management Server and choose the existing Service Manager DW databases when the asked to provide database information.When prompted for service accounts, use the same service accounts noted earlier.The installation wizard will pick up details of Management Group name, database and SQL Reporting Services instance from the DB to complete the wizard and installation.Restore the Report Server databases and encryption key over the newly created SQL Server Reporting Services databases, and verify the report manager URL can be accessed and reports exist.Once installation completes, the new servers will be running the DW MS and Reporting Services.A couple things to note…Remember to use the same IP addresses for the new servers as the old to prevent any name resolution issues, or make sure DNS is updated.The new servers will need to join the domain, so ensure records about the old servers is removed first.Decommission the old servers once the new ones are verified as working, to prevent them being booted back up and conflicting with the new servers.Although this isn’t straight forward, it can be done, it’s just a real shame Microsoft haven’t published any official guide on how to do so.Working with Microsoft, it was confirmed that this is the only approach that will work.  Due to encryption keys, and report deployment issues, renaming the computer hosting any of the components will prevent it from installing.So, good luck to everyone who needs to attempt this, and I hope this helps!! DavidShare this:Click to share on Twitter (Opens in new window)Click to share on Facebook (Opens in new window)Click to share on Google+ (Opens in new window)Click to share on LinkedIn (Opens in new window)Click to email this to a friend (Opens in new window)Click to print (Opens in new window)Click to share on Skype (Opens in new window)Click to share on WhatsApp (Opens in new window)RelatedTags: Data Warehouse, Reporting, SCSM3 CommentsJonRunheim April 11, 2017Big thanks for this info, very helpful!ReplyOzge Ozkaya May 23, 2017Hi David, Thank you for the valuable information. I have a similar case where i only need to move the Reporting service to a new SQL server. What would you suggest as implementation steps?ReplyDavid Allen May 26, 2017Unfortunately, when moving the reporting services server, the new server has to have the same name as the original server. There is no way in SCSM to update the server name of the reporting server.So, you need to take down the original reporting server, build the new server with the same name as the original server and the same instance name and config as the original. SCSM will then use the new server.ReplyLeave a Reply Notify me of follow-up comments by email. Notify me of new posts by email.This site uses Akismet to reduce spam. Learn how your comment data is processed.Recent PostsAzure Stack – Development Kit (Single Node)Cireson Survey – Pre-Selecting The Satisfaction SliderSCOM – Monitor SCSM Data Warehouse JobsSCOM – Updated Unsealed MP Backup Management PackMicrosoft Azure – Securing Accounts With Access To The EA PortalArchivesOctober 2017September 2017July 2017November 2016August 2016January 2016December 2015November 2015October 2015September 2015August 2015July 2015May 2015February 2015October 2014September 2014CategoriesAzureAzure AutomationAzure StackCiresonClusterConfiguration ManagerData Protection ManagerData WarehouseEventsHyper-VIgniteManagement PacksMicrosoft AzureOMSOperations ManagerOrchestratorPassword ResetPortalPowerShellSCU EuropeService ManagerSystem CenterTechEdUncategorizedUpdatesVisual StudioWelcomeWindows Azure PackWindows Server 2012 R2Windows Server 2016TagsAutomation Azure Backup Barcelona Cireson Cloud Compliance Containers Dashboard Data Warehouse DCM DPM Events Grooming Hyper-V Ignite iPad Library Sharing Log Shipping Management Pack MPSync MVP Performance PowerShell Remediation Reporting RSAT SCCM SCOM SCSM SCU SQL SquaredUp System Center System Center 2016 Tape TechEd Technical Preview Update Rollup VMM WAP Window Server Windows Server Windows Server 2016 WorkflowUseful SitesAquilaweb Cloud SolutionsClustrMap  Loading data…MVP© 2018 – Design by Back to top