This is for SQL Resource Provider (RP) 1.1.24.0 which is now superseded by 1.1.30.0 literally the next day after I executed the install. The only reason for posting this blog is to give a baseline for my update SQL RP post. The exact same install process will work for any newer Azure Stack deployments just skip the section where I rollback the PowerShell module version
This post will cover the deployment of the SQL RP with other posts in the series covering the various other steps and considerations
Scenario:
SQL01 - SQL 2016 RTM install (At this point in time I still recommend SQL2014 for DPM2016)
DPM01 – Data Protection Manager 2016 RTM install
When ‘check and install’ get the below error. Clicking on OK then closes the installer
How did we get here?
Install SQL 2016 RTM on SQL01. Setup remote access for DPM01. Install DPM Prereq’s on SQL01. attempt to Install DPM 2016 RTM… and baboom… Error 4387.
Moving SCOM 2012 R2 operationsdatabase to SQL Cluster. Process derived from this TechNet article http://technet.microsoft.com/en-au/library/hh278848.aspx Quick overview of the environment Versioning of my environment: System Center Operations Manger 2012 R2 w/ Update Rollup 4 SQL Server 2012 SP1 CU8 Windows Server 2012 R2
Existing servers and role: OM01 - Management Server OM02 - Management Server OM03 - Management Server OMSDB\OMDB - Operations Database Server / SQL Server 2012 SP1 OMSDW\OMDW - Data Warehouse Server / SQL Server 2012 SP1