Loading

×Sorry to interrupt
This page has an error. You might just need to refresh it.
[NoErrorObjectAvailable] Uncaught ReferenceError: addCTracking is not defined
Failing descriptor: {markup://c:KM_ArticleThemeLayout}

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

FAQ: Windows 10 Updates (77189)

Last Updated: 4/9/2020Categories: InformationalTotal Views: 6361Language:
JapaneseEnglish

7 like this article

Subscribe to get an email
newsletter with new updates

7 people found this helpful Please provide article feedback:

Solution

Where do the updates shown in console come from?
They come from the devices themselves. They do not come directly from Microsoft Windows Update servers.

Why don’t certain updates show up in console?
If a device doesn’t see an update, neither will the console. This also extends to things like localized or OS specific updates that may not apply to any of the devices in your environment.

Why don’t the devices see the updates from Microsoft?
Devices have a scan frequency value which is configurable in WS1 from 1-22 hours. The default value is 22 hours. If an update is released by MS but your devices haven’t scanned yet, it won’t appear on the device which means it won’t show in console.

The devices are scanning and seeing updates but why do they still not show up in console?
 The console communicates (checks-in) with devices at specific intervals (samples) that are unique to each type of data they are sampling. The Update Sample is set to 1 day (24 hours) and is not configurable to a lower value. This means even if the device sees the update it can be up to 24 hours before console would then see it from a device.

Console now shows the update and I’ve approved (or it was auto approved), some devices are installing it right away while others aren’t, why?
Not all devices have necessarily seen the update yet. While you may have approved it for all devices, the fact it shows in console only indicates that at least one device has seen it and is ready to install it, given its approved.

What happens if I approve an update, but the device hasn’t scanned and see it from MS yet?
This is actually ideal. Once seen, the device will immediately download and install it because you’ve already approved it. If you were to delay approvals and the device scanned, it wouldn’t be allowed to download and would have to wait until the next scan (up to 22 hours) before it can scan again.

I approved the updates, the device has discovered/downloaded/installed but console indicates it’s in a state other than the installed status, why?
The Update Sample hasn’t occurred yet. If the device has fully completed all the steps (downloads, installs, reboots) but hasn’t been sampled by the console yet then whatever the last status during the sample was is still going to be the indicated status.

What’s the maximum amount of time it should take from approving an update to seeing it in “Installed” status in the console?
If you approved an update for all devices, it’s likely that some haven’t yet discovered it. This process can be up to 22 hours. Once discovered, it will download and install and then it can be up to 24 hours until the device communicates back to the console. This means even with no other variables; it can be around 46 hours to see an update as installed if approved.

It’s been over 46 hours and I still don’t see a status, or the status hasn’t changed, why?
There are many variables that can impact the timing. While 46 hours would be the maximum for an approved update the following can impact that timing.

Device Availability

Deferrals

Required and Auto Approvals

Device Active Hours

Update Sample <24h

Restart Requirements

Bandwidth (WAN and LAN) Limitations

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
JapaneseEnglish

Attachments

Additional Resources

No results for undefined

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware Workspace ONE

Related Versions:

Take Our Survey

Support Assistant