Consider the following scenario:
- You're running Microsoft System Center Configuration Manager (current branch, version 1810 or a later version) in your hierarchy.
- The instance of Microsoft SQL Server that's hosting the database for the primary site is lost.
- You recover a primary site from a Central Administration Site (CAS) on a newly installed SQL Server instance (for the primary site).
In this scenario, Configuration Manager clients do not receive policy data, and the Configurations tab in client properties is blank (that is, baselines are not visible). Additionally, applications and software update deployments that were created before the recovery may not work.
This problem occurs because the Last Row Version registry entry for the Object Replication Manager and Policy Provider has a higher value than that of the rowversion entry in the site database.
To fix this issue, follow these steps:
- Stop the SMS_Executive and SiteComp services on the primary site server.
- Run the following query on the recovered primary database to obtain the current value for rowversion:
select min(rowversion) from CI_CIAssignments
- Update the Last Row Version value at the following location to match the value that's returned from the SQL query:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\COMPONENTS\SMS_OBJECT_REPLICATION_MANAGER\CI Assignment\Last Row Version
Start the SiteComp service on the primary site server. This will start the SMS_executive service.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.