Updates not deploying via SCCM to Windows 10 32-bit VM within Oracle VirtualBox

asked 2021-04-29T06:41:00.167+00:00
ShaneQV 1 Reputation point

Hi all,

I would like to raise a problem with updates not deploying via SCCM/Endpoint Manager to a Windows 10 32-bit VM within Oracle VirtualBox in a corporate environment.

The VM has Internet and VPN connectivity via the host machine, however, when I run the "Machine Policy Retrieval & Evaluation Cycle" and "Application Deployment Evaluation Cycle" tasks within the Configuration Manager in Control Panel to trigger the deployment within Software Center, nothing seems to be happening.

I know that several applications have been "pushed" to my VM but none of them actually seem to be being deployed.

As I understand it, SCCM in a VM is treated just like SCCM on a host machine.

Could anyone please suggest how I can get updates through to my Win 10 32-bit VM?

Thanks,

Shane,

Windows 10 Network
Windows 10 Network
Windows 10: A Microsoft operating system that runs on personal computers and tablets.Network: A group of devices that communicate either wirelessly or via a physical connection.
1,933 questions
Microsoft Configuration Manager Updates
Microsoft Configuration Manager Updates
Microsoft Configuration Manager: An integrated solution for for managing large groups of personal computers and servers.Updates: Broadly released fixes addressing specific issue(s) or related bug(s). Updates may also include new or modified features (i.e. changing default behavior).
626 questions
No comments
{count} votes

1 answer

Sort by: Most helpful
  1. answered 2021-04-30T07:53:33.34+00:00
    Amandayou-MSFT 10,941 Reputation points

    Hi @ShaneQV

    After deploying the software update, there might be seven steps to troubleshoot the common issues.

    Step 1: We could check Policyagent.log. When policy is received, the following entry is logged in PolicyAgent.log:

    92789-4301.png

    We could check if Deployment Unique Id on the console is consistent with policy id displayed in PolicyAgent.log.
    92808-4302.png

    Step 2: Software update would be checked if it is required by client, kindly check UpdatesStore.log. UpdateStore.log would record updates as missing if they are required. If it is not required or has been installed by client, there is no record in this log.

    Step 3: If the update is required, the content could be detected before downloading. We could refer to UpdatesDeploymentAgent.log.

    Step 4: The content could be downloaded. we could refer to UpdatesHandler.log, CAS.log, and ContentTransferManager.log.

    Step 5: After the download is completed, detection could be followed before installation. We could refer to UpdatesHandler.log,ScanAgent.log, UpdateStore.log, WindowsUpdate.log and WUAHandler.log.

    Step 6: Software update could be installed. We could refer to Windowsupdate.log and UpdatesDeployment.log.

    Step 7: After the updates are installed, Updates Deployment Agent checks whether any updates require a reboot, and then it notifies the user if client settings are configured to allow such notification. We could refer to UpdatesDeployment.log and UpdateStore.log.

    Here is an article about some detailed log screenshots.
    Using log files to track the software update deployment process


    If the response is helpful, please click "Accept Answer" and upvote it.
    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.