Jeff Zabel

My feedback

  1. 3 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    4 comments  ·  Update Management » General  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Jeff Zabel commented  · 

    Hi, I just tried to reproduce this by installing server 2016 datacenter and there's no such driver missing. Update Management only lists the updates that each server thinks it needs, so for some reason.

    Here's a powershell script that simulates what Update Management does to get the list of needed updates.

    If the printer driver is showing up in the output, then the root cause lies with the server. Please let me know the outcome.

    # Get updates from Windows Updates
    $WUSession = New-Object -com "Microsoft.Update.Session";
    $WUSession.ClientApplicationID = "Install-Updates.ps1";
    $WUSearch = $WUSession.CreateUpdateSearcher();
    $SearchResults = $WUSearch.Search("IsHidden = 0 AND DeploymentAction=*");

    $wuUpdates = @();
    foreach ($wuUpdate in $SearchResults.Updates) {
    $update = @{
    RevisionNumber = $wuUpdate.Identity.RevisionNumber;
    UpdateID = $wuUpdate.Identity.UpdateID;
    DeploymentAction = $wuUpdate.DeploymentAction;
    Title = $wuUpdate.Title;
    Deadline = $wuUpdate.Deadline;
    Description = $wuUpdate.Description;
    IsHidden = $wuUpdate.IsHidden;
    IsInstalled = $wuUpdate.IsInstalled;
    IsMandatory = $wuUpdate.IsMandatory;
    MsrcSeverity = $wuUpdate.MsrcSeverity;
    Type = $wuUpdate.Type;
    RebootRequired = $wuUpdate.RebootRequired;
    IsPresent = $wuUpdate.IsPresent;
    SecurityBulletinIDs = @();
    };

    $wuUpdate.SecurityBulletinIDs | foreach {
    $update.SecurityBulletinIDs += $_
    }

    $wuUpdates += $update;
    }

    $wuUpdates | ConvertTo-Json

Feedback and Knowledge Base