SCCM Automatic Client Upgrade Greyed Out

If you notice the automatic client upgrade settings greyed out after SCCM upgrade, not to worry you can fix this issue.

Today I received an email via my contact form & here is the email description – “I have problem with SCCM 1910 Hierarchy settings”. I recently upgraded my current SCCM 1906 version to SCCM 1910. I want to auto upgrade my client agents, but I can’t select box for upgrade in client upgrade tab. Can you help me to resolve this problem ?.

Here is the screenshot and you can see the following options are greyed out under Site Hierarchy Settings > Client Upgrade.

  • Upgrade all clients in the hierarchy using production client.
  • Upgrade all clients in the pre-production collection automatically using pre-production client.
  • Exclude specified clients from upgrade.

SCCM Automatic Client Upgrade Greyed OutTo be honest, I never encounter this issue in my lab setup. So far I have done several upgrades and I always ensure my SCCM clients stay updated to latest version.

However I have seen this issue reported in multiple forums. While configuring the Automatic Client Upgrade the option to upgrade clients is grayed out and rest of other options are also not available.

SCCM Automatic Client Upgrade Greyed Out

If you are dealing with same issue where the Automatic Client Upgrade settings are greyed out on your SCCM primary site, here is the solution.

  • First of all log in to the primary site server with the account that you used to install the primary site server.
  • In the SCCM console, navigate to Administration > Overview > Security > Administrative Users. Right click the user account and click Properties.
  • Under Security Scopes, select All Instances of the objects that are related to the assigned security roles. Click Apply and OK.

SCCM Automatic Client Upgrade Greyed Out

After you perform the above step, go back to Hierarchy Settings Properties > Client Upgrade. Now you can enable or configure the client upgrade options.

I hope this helps.

SCCM Hierarchy Settings


  1. Avatar photo Chris Payne says:


    We just upgraded from SCCM 2004 to 2103. When I did the upgrade a did a test deployment of the client to a limited collection. However, now that I am ready to push the new client out to all of our computers the promote pre-production client option is greyed out. I have read several articles where they talk about the way to fix this problem if you are using role based administration from AD was to add your account directly to SCCM as a full Administrator with access to all of the scopes. I have done this. I have also added my self as a local administrator to the server. I have checked the client upgrade settings under hierarchy setting and it is set to upgrade all clients automatically. The problem is that it still has the old client because the system will not allow me to promote the new client. I have tried all the suggestions that I found so far but nothing has worked. I have had one of our domain admins log in with the account that was used to setup SCCM in the first place but the option to promote is greyed out even for them. Any thoughts?


  2. Avatar photo dmedinamoreno says:

    hi Desai,
    I’m trying to follow their steps in my sccm console with the user installer but the option of “All instances of the objects that ….” is greyed out both, i didnĀ“t solve this problen to upgrade the SCCM Client Package. I would really appreciate your help

  3. Hey Desai,
    After the upgrading to 1910. i stuck at client upgrade. I was trying to set to automatic client upgrade. when i see Production client is showing 1902’s client version and Promote Pre-Production Client is 1910’s.
    can you please help to update production client version to new version.

  4. Hi Mr Prajwal.
    Can you help us for this the following logs.

    We also tried manual agent installation and sccm console installation methods.
    We always encounter the same error.

    A5C203EAC23CD61F5DB1D70C5DD22AB3EEB095188C9200F856F2ATUK SMSSITECODE=TUK FSP=ConfMgrMS. ConfMgrMS. ‘]LOG]!>
    <![LOG[The MP name retrieved is 'ConfMgrMS.' with version '8853' and capabilities '’]LOG]!>

  5. It figures it’s a permissions issue.

  6. Hi Prajwal,

    Even the Security Scopes for All Instances is disabled (Greyed Out). How can we enable that?
    Found in some article that it can only be done by the account that installed the SCCM.
    Unfortunately the installation user left the org. Any other possibility.

    1. From the SQL Mgmt console, list all the Administrative Users :

      select * from RBAC_Admins
      Take the AdminID from the Super Admin

      In the SCCM console, create a new Administrative Users and run the query again :

      select * from RBAC_Admins
      Take the AdminSID of the newly created user

      In the SCCM console, delete the newly created Administrative Users

      Run this query

      update RBAC_Admins
      set AdmdinSID=Enter_the_AdminSID_HERE,LogonName = ‘Domain\Username’ where AdminID=Enter_the_AdminID_HERE

      Issue Fixed

Comments are closed.