Dual scan column

Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • #8704
    can00k
    Participant

    Love the product and the latest update that allows for a scan of MS’s wonderfully annoying “Dual Scan” function. However, I see that when I run that option the result populates the “Windows Update Config” column and overwrites whatever is in there. Can we get a new column for the dual scan results?

    #9870
    doug
    Moderator

    We thought it made sense to use the same column because the dual scan check also reports the windows update config info, which you can see if you expand the row or middle click on the field. Additionally, we don’t view the dual scan check or the windows update configuration check to be things that generally would be changing… that is to say that there shouldn’t generally be a need to be checking either of these items on a regular basis because if a computer is set properly, then it’s set and it’s not going to change its configuration all of a sudden. I’d be curious to hear why you think it would make a significant difference to put these in separate columns.

    This is what the expanded result looks like for the dual scan check. The WUServer value is the same as the result that you would see if you use ‘get windows update configuration’:


    Dual Scan Enabled: FALSE . . .

    WUServer: Windows Update
    DefaultAUService: Windows Update


    Thanks,

    Doug

    #9871
    can00k
    Participant

    It’s only relevant to my situation because I’m literally in the middle of configuring WSUS and BatchPatch and had noticed that Dual Scan had been enabled on some of our Server 2016 machines. So I’ve been refreshing the Windows Update Config and Dual Scan settings to check that they’re correct. I understand how once it’s set up correctly, I’d rarely if ever need to see both pieces of info in a column.

    #9872
    doug
    Moderator

    Thanks for explaining. We’ll consider it.

    -Doug

Viewing 4 posts - 1 through 4 (of 4 total)
  • You must be logged in to reply to this topic.