ConfigMgr 2012 RC2 – Primary Site is Read-Only

Tuesday, 7. February 2012

In the course of evaluating ConfigMgr 2012 in my lab, I ran into an issue where my Primary site would be in read-only mode. This only occured when using the Primary site along with a Central Administration Site; a standalone Primary site would not exhibit this issue.

Another blog explained my issue perfectly, but they had no solution (link). In short, I received the following message when launching the ConfigMgr console on the Primary site server:

Your Configuration Manager console is in read-only mode while this site completes tasks related to maintenance mode.

After these tasks are complete, you must reconnect you Configuration Manager console before you can edit or create new objects.



The cause for this issue is a lack of replication between the CAS and the Primary site. When you look in Monitoring -> Database Replication, you will probably see that the “Link is being configured”. Until the link is configured, and the necessary replication from the CAS to the Primary site has occured, the Primary site will remain read-only.

The solution (at least in my case) was quite simple. Both sites were using unique instances on the same SQL server, and the SQL Server Service Broker (SSB) port was left at the default value of 4022 when installing each site. A conflict arises when both sites attempt to use the same port for the SSB. To avoid the issue, use a different (and unused!) port for each CAS/Primary site.

If you’re already experiencing the issue, you may re-run the installer and change this:

  1. Run the installer from the local installation directory (for example: C:\Program Files\Microsoft Configuration Manager\bin\X64\SETUP.EXE).
  2. Choose Perform site maintenance or reset this Site from the Available Setup Options screen.
  3. Choose Modify SQL Server configuration from from the Site Maintenance screen.
  4. Adjust the SSB Port setting on the Database Information screen and complete the wizard.

Once you complete the wizard, you will begin to see increased activity on SQL server. It may take a few minutes, but you will notice the Database Replication status will change as the replication setup progresses. You can also monitor the rcmctrl.log file on each site for activity noting that replication is progressing.

(Credit goes to an unknown ConfigMgr at Microsoft who was able to answer questions that I passed through another contact.)