Clients fail to run software update cycle due to patch target ownership and scoping. Stuck in "Scheduled" status.
search cancel

Clients fail to run software update cycle due to patch target ownership and scoping. Stuck in "Scheduled" status.

book

Article ID: 164141

calendar_today

Updated On:

Products

Patch Management Solution Client Management Suite IT Management Suite

Issue/Introduction

Windows clients show pending Software Updates stuck in Scheduled status and never install, even when the update packages are downloaded and locally marked "READY". Agent logs show the client blocked by an auxiliary package error tied to the Patch Install Tools package (Auxilliary package GUID {832C527C-B9C9-46FB-B1F1-2F35434FF90D}). The Software Update Cycle exits without installing anything and returns to a "Ready" state.

Client Logs detail the change state to download packages and show errors package does not exist for the Patch Install Tools package GUID (Auxilliary package {832C527C-B9C9-46FB-B1F1-2F35434FF90D}), followed by warnings pertaining to "unknown exception" or "is not ready" on that package, and the process continues with assigning an install order for each targeted Software Update, yet when it tries to check on the Applicability, the warning is thrown for is not ready on that package.

Error: refreshPackageStatusVerbose(): Auxilliary package {832C527C-B9C9-46FB-B1F1-2F35434FF90D} does not exist.

Warning: DownloadPackage (id - {832C527C-B9C9-46FB-B1F1-2F35434FF90D})- unknown exception

Warning: Auxilliary package {832C527C-B9C9-46FB-B1F1-2F35434FF90D} is not ready.

Environment

ITMS 8.7.x, 8.8.x

Patch Management 8.7.x, 8.8.x

Cause

The Patch Install Tools package fails to reach affected clients because the target that scopes it, Windows Computers with Software Update Plug-in Installed (under Settings > All Settings > Software > Patch Management > Windows Settings > Windows Patch Remediation Settings policy), does not contain those clients. This happens when the target's owner is not the Application Identity (AppID), when the Windows Patch Remediation Settings policy points at a clone of the target instead of the default target, or both. Fixing ownership alone is sometimes not enough; the target's scoping roles and attributes also need to be corrected before membership rebuilds correctly.

The client-side symptom is always the same: the Patch Install Tools package is not scoped to the client, so the Software Update Agent's pre-install check fails and no patches install. The server-side cause has shown up in three overlapping forms:

 

Cause

Likelihood

Evidence

Assumptions

Target owner is not the AppID

High

Console shows owner as a different account or "Unknown"

None — directly observed

Windows Patch Remediation Settings policy points at a clone of the default target instead of the default target itself

High

Two clones of the target existed under the same display name; neither was owned by the AppID

Clones were created as a past workaround for a similar issue and left in place

Scoping roles on the target lack rights to All Computers

Medium

Target showed 0 resources even after owner was corrected, until Symantec Administrators role was added to scoping

Role gap, not a database corruption issue

In this case, the policy was pointed at one of two clones sharing the default target's name. Neither clone was owned by the AppID, and the default target itself was also not owned by the AppID. Correcting ownership on the default target alone was not sufficient — the target still returned 0 resources until the Symantec Administrators role was added to its scoping.

Confirmed that none of the scoping roles had ownership over the managed Clients included in the Filters which build the Windows Computers with Software Update Plug-in Installed - Target .

Resolution

  1. Confirm the client-side symptom in Agent.log:

    Auxilliary package {832C527C-B9C9-46FB-B1F1-2F35434FF90D} is not ready.

    Also confirm that other targeted updates on the client show "READY" locally but are skipped with "Reason: Schedule or MW is not due yet", while an ASAP-flagged update alone triggers the failed pre-install check.

  2. In the console, go to: Settings > All Settings > Software > Patch Management > Windows Settings > Windows Patch Remediation Settings.
    Confirm which target the policy is pointed at. If it points at a clone rather than the default Windows Computers with Software Update Plug-in Installed target, note the clone's name and GUID before changing anything.

  3. Check for duplicate targets sharing the same display name. If more than one exists, identify which is the actual default target (this is normally the one referenced in the base Patch Management configuration, not one created later as a workaround).
  4. Point the Windows Patch Remediation Settings policy at the default target.
  5. Check if in the database the target used  in the "Windows Patch Remediation Settings" policy is not set the App Identity as the Owner:

    select i.Name as 'Target',
    i.Guid,
              t.Name 'Roles',
              case when rt.OwnerTrusteeGuid = '0FFFFFFF-FFFF-FFFF-FFFF-FFFFFFFFFFFF'
                       then 'App Identity'
                       else 'Unknown' end as 'Owner',
              rt.OwnerTrusteeGuid,
              rt.LastFullUpdate
      from ResourceTargetOwnerTrustees rtot
        join vRM_Trustee_Item t on t.Guid = rtot.TrusteeGuid
        join Item i                         on i.Guid = rtot.ResourceTargetGuid
        join resourcetarget rt       on rt.Guid = rtot.ResourceTargetGuid
    where ResourceTargetGuid in
              ('96F806F1-D46D-47AA-BB40-2E2E5EFBF4C3',
              'F74F662B-F586-457A-9A2E-804CC8F347E5',
              '7C8FCA03-3B41-4A82-A936-FD632B2EDCDA',
              '9E95B894-FC55-4C66-98D0-90C6403EEE2B',
              '9ED1C8F2-0FB6-45EF-AAE6-69285E48C949')
    order by i.name, t.name


    If any, take note of the GUID.



  6. Set the target's owner to the AppID:

    -- Change owner to AppID
    UPDATE ResourceTarget
    SET OwnerTrusteeGuid = '0FFFFFFF-FFFF-FFFF-FFFF-FFFFFFFFFFFF'  --App Identity
    WHERE guid IN ('F74F662B-F586-457A-9A2E-804CC8F347E5') --GUID of the affected target

    Note: Replace the target GUID with the one specific to the affected environment.

  7. Review the target's resource count. If it still shows 0 resources after the owner change, the scoping roles need correcting before membership will rebuild.
  8. Temporarily clear the target's attributes to allow edits:

    --Default attribute value: 274
    --Set attribute to 0 for Edit

    UPDATE item SET attributes = 0
    WHERE guid = 'F74F662B-F586-457A-9A2E-804CC8F347E5'


  9. In the SMP Console, add the "Symantec Administrators" role to the default scoping for Windows Computers with Software Update Plug-in Installed, alongside the existing Patch Management Rollout and Patch Management Administrators roles. Confirm the role has access to All Computers.





  10. Restore the target's original attribute value:

    UPDATE item SET attributes = 274
    WHERE guid = 'F74F662B-F586-457A-9A2E-804CC8F347E5'

  11. Confirm this is the correct original value for the affected target before restoring it — it is not a universal default.
  12. Confirm the AppID is still set as owner. If not, run again:

    UPDATE ResourceTarget
    SET OwnerTrusteeGuid = '0FFFFFFF-FFFF-FFFF-FFFF-FFFFFFFFFFFF'
    WHERE guid IN ('F74F662B-F586-457A-9A2E-804CC8F347E5')

  13. Confirm the target now shows the expected resource count.
  14. Run the following scheduled tasks on the SMP server, in order:
    • NS.Delta Resource Membership Update
    • NS.Windows Patch Remediation Settings
  15. To test the fix, on one of the affected clients, restart the Symantec Management Agent service and run a Windows Assessment Scan.


Verification

The target shows the expected number of resources after the ownership and scoping changes, instead of 0. After the scheduled tasks run and the agent service restarts, the client downloads the Patch Install Tools package and the is not ready warning stops appearing in Agent.log.

In this case, one endpoint downloaded the Patch Install Tools package (after restarting the Symantec Management Agent service and triggering the Windows Assessment Scan), started a Software Update Cycle, and installed a pending update. Full patching results across the environment may take additional cycles to confirm.

 

NOTE:

If unable to modify the Symantec_CMDB database; work through the following:

  1. Import the attached Patch Target Membership Roles custom report.
    • Open the Console > Reports > All Reports > Software > Patch Management
    • Highlight Patch Management > Right-click > Import
    • Browse to the storage directory of this custom report
    • Click Open
  2. Review the listed Roles; give them rights to the computers which are in the Target.
    • Generally the two roles owning this policy are Patch Management Rollout & Patch Management Administrators
    • Ensure they are able to own the All Computers filter and that will allow the permissions access to update the Windows Computers with Software Update Plug-in Installed - Target ownership associations in the database

Attachments

SQL Script - Add Symantec Admin to Patch Target.txt get_app
Patch Target Membership Roles.xml get_app