This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(73.60000000000001, 93%, 17%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESV%3C/text%3E%3C/svg%3E)
Hi All,
CM 2006
On our client devices we're trying to determine the SUP information from where the devices are scanning from. We're querying the "LastScanPackageLocation" from the v_UpdateScanStatus view.
There are about 5903 devices which are showing blank (no information)
. Something I just recognized: out of the 5903 devices where we don’t have a “LastScanPackageLocation”, 5637 also are in the state of “Scan is running”. So my Assumption is that the “LastScanPackageLocation" might actually be empty until the scan is finished? Could there be any other reason?
Thank You.
This data is unrelated to hardware inventory. All software update activity and compliance scanning by clients is communicated to the site using state messages. Without having the dataset to directly examine, I can't offer any reasons on why this value could be blank other than you caught it at a transitional time.
What challenge exactly are you attempting to address or why is this significant?
Thanks again for getting back Jason.
The objective to identify the WSUS scan location is to determine which of the clients are covered by the SCCM-WSUS(inbuilt) infra or another Stand-Alone WSUS Infra which we have parallelly set up. Hence we're trying to check this specific field "LastScanPackageLocation" from the v_UpdateScanStatus view to identify the computer as being patched through SCCM. Since there were differing values ranging from a blank field to "Scan is running", we're trying to determine the intended scan behaviour and the updation of this field. Thank you.
OK, that's a fair ask although the way I normally address this is to use a CI and baseline to check the value of WUServer at HKLM:\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate to validate the actual configuration.
On our client devices we're trying to determine the SUP information from where the devices are scanning from.
The easy way to get this info is to review the WUServer value at HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate on managed systems. You can use CMPivot or a CI to validate this.
You can also leverage the Scan 1 - Last scan states by collection built-in report (which queries the view you referenced above). If you review the queries in this report, you may find logic or a translation for these values.
Hey Jason,
As always thank you for sharing your thoughts. While we do have the option of querying the alternate source in the Registry, I'm primarily trying to understand why the above database view field is blank. A further observation which seems to indicate that the above phenomenon is not constant. i.e. the data would populate eventually. But what's a bit strange is that for several machines that were missing the 'LastScanPackageLocation' data in the given view the same data got populated within a span of few hours and this did not happen due to a subsequent hardware inventory scan. i.e. the Hardware Inventory Scan timestamp remained the same before the data was observed missing and after the data got populated. Which makes us think there is some kind of Fast channel notification or state based notification which seems to be populating the v_UpdateScanStatus view.
Can you please chime-in as appropriate and let me know if I'm missing something?
I think we have now established that this behaviour is probably due to the state based messages of the WSUS scan which causes the data field to get updated multiple times irrespective of the Hardware Inventory Scan schedule.