Feature Update to Win 10 Version 20H2 x64 2020-10 via Enablement Package for Win 10, version 2004 missing from my ZPM

I don't seem to have this in my list of available patches?

Is there some trick to making this available?

Running ZENworks 2017.4.0 appliance

Parents
  • This should be there....

    Search for "KB4562830"

    However, make sure the Pre-Requisites have also been deployed....

    https://support.microsoft.com/en-us/topic/feature-update-through-windows-10-version-20h2-enablement-package-02d91e04-931e-f00d-090c-015467c49f6c

    Perhaps it is some issue where it is not downloading because it is not applicable to any devices.

    --

    Be sure to "Like" My (and a few others) Cool Solutions below! 

    https://community.microfocus.com/members/craigdwilson/bookmarks

  • Hi Craig,

    That KB is not there.

    Almost all of our workstations are at v1909 and many of them have been working from home for the past many months. Some come into the office once in a few weeks and are getting some patches via ZPM.

    About 30 have updated to v2004 on their own outside the office. About 12 of those have been in the office and have since upgraded to v20H2.

    The over 300 users still running v1909 have started receiving Windows prompts to upgrade. Those who answered Yes are now at v2004 and having all kinds of problems. Slowness and freezing of Citrix sessions are the main concerns. Some users can't login anymore. Some fail the update and roll back. Our Helpdesk is swamped with calls.

    The ones that come into the office, and are still capable of logging in, seem to be getting upgraded to v20H2 and have v20H2 patches available in ZPM. We are trying to determine if we can force the v2004 ones to upgrade to v20H2 via ZPM and hoping that might fix the problems that the users are experiencing.

    But the v20H2 Enablement Package is not there. Perhaps the workstations coming in are already past that point?

    Somebody has made a real mess to the patching and upgrading of their OS!

    Any suggestions, ideas or thoughts are welcome at this stage.

    Thanks,

    Chris

  • I'm probably not being clear in my explanation.

    The laptops in question are coming back into the office already upgraded from v1909 to v2004 via the Internet.

    They are connecting to ZENworks for the first time in weeks or months and are then upgrading to 20H2. I assume that ZPM is doing this?

    I've read the Cool Solutions article several times and that is a possibility. We have been trying to upgrade from v1909 to v2004 via WSUS with mixed results - it often fails and rolls back.

    With so many laptops out of the office for so long, and not getting regular updates, when staff do come into the office to see clients (sometimes only for an hour or two) we don't want to risk making their laptop unusable during a client session.

    We are a children's health care provider and are under lockdown here. Clients are only being seen in person when the need is required for their treatment. We are trying to find the least impactful way to resolve this situation.

    Since we have had some v2004 laptops connecting to ZENworks, I was wondering why the v20H2 enablement package was not being detected as being needed? 

  • Keep in mind that running Windows v2004 is not SUFFICIENT to meet the requirements for the Enablement Package.

    So it can be that....

    #1 - Your v2004 devices are not running the DAU scan to indicate they need it.

    #2 - Your v2004 devices may lack the other requirements for the Enablement KB and hence are not reporting they need it.  Those requirements are detailed in the MS link in an earlier comment.

    --

    Be sure to "Like" My (and a few others) Cool Solutions below! 

    https://community.microfocus.com/members/craigdwilson/bookmarks

  • Keep in mind that running Windows v2004 is not SUFFICIENT to meet the requirements for the Enablement Package.

    So it can be that....

    #1 - Your v2004 devices are not running the DAU scan to indicate they need it.

    #2 - Your v2004 devices may lack the other requirements for the Enablement KB and hence are not reporting they need it.  Those requirements are detailed in the MS link in an earlier comment.

    --

    Be sure to "Like" My (and a few others) Cool Solutions below! 

    https://community.microfocus.com/members/craigdwilson/bookmarks

  • Keep in mind that running Windows v2004 is not SUFFICIENT to meet the requirements for the Enablement Package.

    So it can be that....

    #1 - Your v2004 devices are not running the DAU scan to indicate they need it.

    #2 - Your v2004 devices may lack the other requirements for the Enablement KB and hence are not reporting they need it.  Those requirements are detailed in the MS link in an earlier comment.

    --

    Be sure to "Like" My (and a few others) Cool Solutions below! 

    https://community.microfocus.com/members/craigdwilson/bookmarks

  • Keep in mind that running Windows v2004 is not SUFFICIENT to meet the requirements for the Enablement Package.

    So it can be that....

    #1 - Your v2004 devices are not running the DAU scan to indicate they need it.

    #2 - Your v2004 devices may lack the other requirements for the Enablement KB and hence are not reporting they need it.  Those requirements are detailed in the MS link in an earlier comment.

    --

    Be sure to "Like" My (and a few others) Cool Solutions below! 

    https://community.microfocus.com/members/craigdwilson/bookmarks

  • Keep in mind that running Windows v2004 is not SUFFICIENT to meet the requirements for the Enablement Package.

    So it can be that....

    #1 - Your v2004 devices are not running the DAU scan to indicate they need it.

    #2 - Your v2004 devices may lack the other requirements for the Enablement KB and hence are not reporting they need it.  Those requirements are detailed in the MS link in an earlier comment.

    --

    Be sure to "Like" My (and a few others) Cool Solutions below! 

    https://community.microfocus.com/members/craigdwilson/bookmarks

  • Keep in mind that running Windows v2004 is not SUFFICIENT to meet the requirements for the Enablement Package.

    So it can be that....

    #1 - Your v2004 devices are not running the DAU scan to indicate they need it.

    #2 - Your v2004 devices may lack the other requirements for the Enablement KB and hence are not reporting they need it.  Those requirements are detailed in the MS link in an earlier comment.

    --

    Be sure to "Like" My (and a few others) Cool Solutions below! 

    https://community.microfocus.com/members/craigdwilson/bookmarks

  • Thanks Craig.

    They have probably missed getting one of the prerequisite updates.

    However, they do seem to upgrade to v20H2 without any issues after re-connecting to ZPM and successfully get updates to v20H2 via ZPM.

    Some have needed to have the ZEN Agent re-installed when they come back into the office after the Internet upgrade to v2004. We then run zac ps and manually push needed updates to them.

    Thanks for the clarifying links. It has helped to explain this confusing situation.

  • Are you reinstalling because ZCM Logons are failing after the Windows OS Upgrade?

    See - https://community.microfocus.com/collaboration/zenworks/w/zenworkstips/5148/windows-in-place-upgrade-may-remove-zenworks-network-providers---automated-repair

    There is a known Windows Upgrade issue were on some small percentage of upgrades it may break 3rd party credential Providers.  The link above has a bundle that will Detect and optionally automatically repair that issue.

    There was ANOTHER OS Upgrade issue where it may delete all 3rd Party Certificates.  If you upgrade from "CURRENT" Windows Media that was republished Dec 2020 or later, this will not occur.  This may be another explanation of why you had to re-install.

    --

    Be sure to "Like" My (and a few others) Cool Solutions below! 

    https://community.microfocus.com/members/craigdwilson/bookmarks

  • The situation appears to be the first one. ZCM Logons are failing after the OS upgrade.

    Since we've only had 3 laptops do this so far, the uninstall and re-install was the fastest solution.

    Thanks for the info. I had seen that Tip previously, but we are not at the stage where investing the time in testing is likely to pay off.

Reply
  • The situation appears to be the first one. ZCM Logons are failing after the OS upgrade.

    Since we've only had 3 laptops do this so far, the uninstall and re-install was the fastest solution.

    Thanks for the info. I had seen that Tip previously, but we are not at the stage where investing the time in testing is likely to pay off.

Children
No Data