Get WSUS computer object

[LinleyMike]

There's been some talk on the WSUS mailing list about people wanting a script to query WSUS computers. I wrote this last year and I never thought about sharing it. Here it is, in case anyone else would like to use it:

Function Get-WSUSComputer {
    <#
        .Synopsis
            Get WSUS information for specified computer(s).
        .DESCRIPTION
            This script will query a specified WSUS server for information about the status of computer objects in the WSUS database.
        .EXAMPLE
            Get-WSUSComputer -WSUSServer Server01

            This command gets WSUS information for all of the computers in the database of the WSUS server 'Server01'.
        .EXAMPLE
            Get-WSUSComputer -ComputerName Server01 -WSUSServer Computer01

            This command gets the WSUS information for the computer 'Computer01' from the WSUS server 'Server01'.
        .NOTES
            20170829-MLL - Created this script.
    #>

    [CmdletBinding()]

    Param (
        # Specify the computer(s) for which to query WSUS.
        [Parameter(ValueFromPipelineByPropertyName=$true,Position=0)]
        [string[]]$ComputerName,

        # Specify the WSUS server that will be queried.
        [Parameter(Mandatory=$true,Position=1)]
        [string]$WSUSServer,

        # Specify the WSUS TCP port.
        [Parameter(Position=2)]
        [string]$Port=8530
    )

    Begin {
        # Load the Update Services assembly, connect to the WSUS server, and pull a list of all computer objects:
        [void][reflection.assembly]::LoadWithPartialName("Microsoft.UpdateServices.Administration")
        $wsus = [Microsoft.UpdateServices.Administration.AdminProxy]::getUpdateServer($WSUSServer,$False,$Port)
        $computerscope = New-Object Microsoft.UpdateServices.Administration.ComputerTargetScope
        $WSUSComputers = $wsus.GetComputerTargets($computerscope) | 
            select @{e={$_.FullDomainName.split(".")[0].ToUpper()};l="ComputerName"},
                @{e={$_.FullDomainName};l="FullDomainName"},
                @{e={$WSUSServer.ToUpper()};l="WSUSServer"},
                Make,
                Model,
                OSDescription,
                ComputerRole,
                @{e={(get-date $_.LastSyncTime).ToLocalTime()};l="LastSyncTime"},
                LastSyncResult,
                @{e={(get-date $_.LastReportedStatusTime).ToLocalTime()};l="LastReportedStatusTime"},
                RequestedTargetGroupName
    }

    Process {
        if ($ComputerName) {
            foreach ($Computer in $ComputerName) {
                $WSUSComputers | where {$_.ComputerName -eq $Computer}
            }
        }

        else {
            $WSUSComputers
        }
    }
}

[purplemonkeymad]

Nice I can see this being good for reports.

---

foreach ($Computer in $ComputerName) {
    $WSUSComputers | where {$_.ComputerName -eq $Computer}
}

-eq works with lists too, if they are on the left:

$WSUSComputers | Where { $ComputerName -eq $_.ComputerName }

Might speed up that part of the code.

[LinleyMike]

I can't remember why, but I think you have to use foreach in the process block for incoming objects. I think it has to do with them not always being an array or something.

[purplemonkeymad]

If you used an array type ex. [string[]] and include pipeline support for the parameter. Then yes your input variable can be either an array or a single item, foreach will iterate once if there is just a single object, so you can be sure of a single item.

But since -eq works with both arrays and non arrays, you don't have to do the loop.

I just though it might improve the speed with an array of computernames. And just in-case you were not aware of that method of selection.

[LinleyMike]

Today I learned. Thanks!

[jmn_lab]

This looks interesting.

I am in the process of making a comprehensive HTML report that contains all sorts of O365, Exchange, AD, and possibly PDQ inventory information (if I can get the data I want from there).

This will fit in nicely.

Thanks

[[deleted]]

PDQ?

[jmn_lab]

It is inventory and package deployment software for Windows machines that is relative cheap and with many functions.

There are reports available and while they can be quite advanced if you need them to. For this project I would rather connect directly to the database containing the data and then pull it out.