Issue:
After this update rollup is installed, the Configuration Manager console may not open. This issue occurs if there’s a provider that’s remote to both the site server and the server that’s running SQL Server for a given site. Additionally, errors that resemble the following are recorded in the Smsprov.log file when you try to open the console in this scenario:
Logfile:
*** [42000][2571][Microsoft][SQL Server Native Client 11.0][SQL Server]User
'{domain}\{provider_computer_account}' does not have permission to run DBCC TRACEON.
~*~*~[42000][2571][Microsoft][SQL Server Native Client 11.0][SQL Server]User
'{domain}\{provider_computer_account}' does not have permission to run DBCC TRACEON.
Failed
\r\nSystem.Management.ManagementException\r\nGeneric failure \r\n at
System.Management.ManagementException.ThrowWithExtendedInfo(ManagementStatus errorCode)
at System.Management.ManagementObjectCollection.ManagementObjectEnumerator.MoveNext()
at
Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlQueryResultsObject.<GetEnumerator>d__74.MoveNext()\r\nManagementException details:
instance of
__ExtendedStatus
{
Description = "[42000][2571][Microsoft][SQL Server Native Client 11.0]
[SQL Server]User 'Domain\\ComputerAccount$' does not have permission to run DBCC TRACEON.";
Operation = "ExecQuery";
ParameterInfo = "SELECT * FROM SMS_Site WHERE SiteCode = 'XXX'";
ProviderName = "WinMgmt";
StatusCode = 2147749889;
};
\r\n
Solution:
To resolve this known issue, set the following registry value to 0 (zero) on the remote provider computer:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\Providers\UseLegacyCardinality
After the registry change is made, restart the Windows Management Instrumentation (WMI) service on the provider computer.
This is a known error that now is also documented at the Update Rollup website: https://support.microsoft.com/en-us/help/4462978/system-center-configuration-manager-version-1806-update-rollup