Fix SCCM Automatic Client Upgrade Greyed Out or Disabled

In this post, I’ll describe how to resolve SCCM automatic client upgrade greyed out issue. If the automatic client upgrade settings are disabled after an SCCM upgrade, don’t worry; you can fix this.

Today I received an email from a Configuration Manager administrator who had a weird issue with an automatic client upgrade in SCCM. The email stated the following: I have a problem with SCCM hierarchy settings. I recently upgraded my current SCCM 2207 version to SCCM 2211. I want to auto-upgrade my client agents, but I can’t select the box for an upgrade in the client upgrade tab. Can you please help me to resolve this difficulty?

There are two methods for updating a client agent in ConfigMgr: automatic upgrade and manual upgrade. The recommended method for upgrading multiple clients in a production setup is an automatic upgrade, especially if you have a lot of computers. Whereas with a manual client upgrade, you perform a manual client installation on every computer.

The client upgrade settings are often grayed out, which makes it impossible for ConfigMgr admins to automatically update clients to the latest version. Let’s take a look at some screenshots that explain the concern and try to solve the grayed-out SCCM automatic client upgrade issue.

Automatic Client Upgrade Options are Disabled

You can see in the below screenshot that the following options under Site Hierarchy Settings > Client Upgrade are grayed out.

  • Upgrade all clients in the hierarchy using production client.
  • Do not upgrade servers.
  • Automatically upgrade clients within days.
  • Upgrade all clients in the pre-production collection automatically using pre-production client.
  • Exclude specified clients from upgrade.

To summarize, all the options available on the client upgrade tab are disabled. The production client version and pre-production client version details are visible.

SCCM Automatic Client Upgrade Greyed Out
SCCM Automatic Client Upgrade Greyed Out

Client upgrade options being disabled is something that I haven’t personally encountered in my lab setup. I have done several SCCM upgrades in the past and I always ensure the SCCM clients are updated to latest version. However, I have seen this issue reported in multiple forums by many users after the ConfigMgr upgrade and there is a solution available. While configuring the Automatic Client Upgrade the option to upgrade clients is grayed out and rest of other options are also not available.

Fix SCCM Automatic Client Upgrade Greyed Out

The primary reason why the client upgrade options are greyed out in SCCM is because the user doesn’t have enough permissions to access the ConfigMgr objects. This issue is commonly seen on new Configuration Manager installations or after upgrading SCCM to next version.

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

  • Sign-in to the SCCM 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 select Properties.
  • Under Security Scopes, select All Instances of the objects that are related to the assigned security roles. Click Apply and OK.
Fix SCCM Automatic Client Upgrade Greyed Out
Fix SCCM Automatic Client Upgrade Greyed Out

After you make the above changes, close the Configuration Manager console and launch it again. Now go to the SCCM primary site and select Hierarchy Settings. In the hierarchy settings tab, switch to the Client Upgrade tab. Now we can see that the client upgrade options are turned on and that the current user can set them up.

When multiple users are logging into the Configuration Manager console, you might occasionally need to restart the server once to make changes take effect.

Fix SCCM Automatic Client Upgrade Greyed Out
Fix SCCM Automatic Client Upgrade Greyed Out

8 Comments

  1. Avatar photo Dinesh Kumar says:

    This itself greyed out – All instances of the Object that are related to th assigned security roles

  2. Avatar photo Chris Payne says:

    Hello,

    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?

    Thanks

  3. 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

  4. 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.

  5. 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]!>

  6. It figures it’s a permissions issue.

  7. 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

Leave a Reply

Your email address will not be published. Required fields are marked *