It’s possible something went wrong because the Site tried to reinstall the Management Point before everything was ready. We found “Counter Thread Proc: MIFs/min counter missing” in the A solution is documented in https:// or
SMS_SITE_COMPONENT_MANAGER wasn’t disabled during this upgrade. articleid=479 I saw similar entries for other counters – SMS_NOTIFICATION_MANAGER Begin to update perf counter WARNING: Perf Counter Mgr is not initialized, performance counter Total bad files moved is not available to update.
They will act as tests for the Site Server Upgrade. As an added bonus I can use the same procedure to get them up-to-date.
Microsofts short description of the upgrade: https://docs.microsoft.com/en-us/sccm/core/servers/manage/upgrade-on-premises-infrastructure I based my upgrade plans on this document: Part I – Introduction Part II – Problems during the Upgrade Part III – Checklist during the Upgrade Part IV – Upgrade Screenshots Part V – Problems after the Site Server Upgrade Our SQL Administrator upgraded the SQL Servers. This was solved by changing SQL Server Cardinality Estimation level from 120 to 110.
This is recommended in https://docs.microsoft.com/en-us/sccm/core/servers/manage/upgrade-on-premises-infrastructure Our SQL Administrator also fixed a problem with SQL Reporting.
Error Message: Failed to load expression host assembly. On some systems I had to reinstall the BITS Feature.
One server lost its network settings during the upgrade. Data Ontap DSM for Windows MPIO needs to be removed, reinstalled and reconfigured after the upgrade. And afterwards the servers will reboot faster without the MSi Scsi Event.
After the upgrade the servers needed more time to restart. Part I – Introduction Part II – Problems during the Upgrade Part III – Checklist during the Upgrade Part IV – Upgrade Screenshots Part V – Problems after the Site Server Upgrade I downloaded the latest version for Windows 2012R2. Start I will install the updates after the upgrade.
CStatus Manager Perf Object:: Update Rate Counters can not complete because CStatus Manager Perf Object is not initialized.These articles will describe how I upgraded our Configuration Manager Environment.Configuration Manager 1702 doesn’t support Windows 2008R2 or SQL2008R2 for most Site System Roles. This is ment as an example to help anyone who needs to go through this upgrade.BITS_POST /CCM_Incoming/ (bits_error:,501,0×80070005) 443 – Microsoft BITS/7.8 501 0 0 1845 0 To fix this you need to remove and add the management point role to the site system https://gregramsey.net/2012/06/18/fix-for-error-in-iis-log-on-mp-bits_error5010x80070005/ I used a trick: Change the Management Point from https to http and back.Monitor and reboot the server after you see ‘Installation completed, but a reboot is required.’ This was the first production Site System I upgraded.WARNING: Perf Counter Mgr is not initialized, performance counter Total files processed is not available to update.Begin to get file list to process WARNING: Perf Counter Mgr is not initialized, performance counter Total files remained is not available to update.It’s not clear why Operation Manager didn’t report on outboxes with too many files. The problems with our Compliance Reports continued.I found the following entry in the IIS logs of one Management Point …We will upgrade Distribution Servers, SQL Server and then the Site Server.I decided to upgrade the Distribution Servers because they have similar prerequisites as the Site Server.