applicationspax.blogg.se - Flexi 12 cloud latest update 2017

Set the service account to the account used previously.From SCCM add back in the Reporting Point Role.Download and run the "SQL Server® 2017 for Microsoft® Windows Latest Cumulative Update ".Encryption Keys - Restore the key saved earlier.Web Portal URL - Reports for HTTP default settings were adequate.Database - Set Database to the existing SRS database, accept the defaults.You will a warning that the URL was overwritten.Web Service URL - ReportServer for HTTP default settings were adequate.Service Account using either virtual or a specified service account.Set SCCM, ReportServer and ReportServerTempDB properties to:.Select Next until you get to Upgrade, select Upgrade.Reporting Services will be uninstalled, you have to select the check box indicating you understand this.Hit Next until you get to Reporting Services Migration.

Copy the product key when its shown, you'll need it for reporting

Install > Upgrade from previous version.

Check the SMS_SRS_Reporting_Point status monitor to see that its removed.

Remove the SCCM Reporting Services Point, give it a few minutes to work.

Open SRS Configuration for the SRS instance, save the encryption key to a location where you can find it and saving the password for the file created.

Locate the password for the SQL Reporting Service Account if you are using it.

Backup databases and other stuff like normal.

If anyone has any suggestions on improvements or things I missed, I appreciate the effort to improve Note, this is using SCCM 1806, Windows Server 2012 R2, and I'm not using HTTPS on any of the internal facing interfaces. Please go over to the SQL group and smack them for me for pulling SRS out of SQL. Once I figured it out it actually worked pretty good. Since I couldn't find this anywhere and it took me some time to figure out, here are the steps to upgrade in place the SQL database from 2012 to 2017.