This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Windows Feature Update and ZCM Agent login Issue

I am dealing with an issue where the ZCM agent will not show user specific bundles after a Windows feature update. When you go the Technician Application area, you see "Logged In As: Not Logged In".

My situation:
Windows 10 x64 Education version 1709 - updated through WSUS from Windows 10 x64 Education version 1607
ZCM 2017 - user logged in before the feature update but after feature update no user login
Domain/eDir hybird login-login to domain and then pass credentials to OES Client and ZCM agent
Computer based bundles and applications work fine, user based are not work at all.

Here is what I have tried so far.
1. Updated ZCM agent to ZCM2017U1 and that seems to fix the issue, but can not necessarily update all systems ZCM agents and OS at the same time.
2. Tried the tuning registry setting HKLM\software\novell\zcm\zenlogin\DisableZENCredientalProvider by changing it to both 0 and 1 and not change either time
3. Tried adding registry setting HKLM\software\novell\zcm\zenlogin\readcachedn with value of 0 - no change in behavior

I need to start updating system to version 1709 because updates for version 1607 will not last until after March 2018. Does anyone run into this issue or have registry settings that could try?
Any help would be appreciated!

Tim Overdorf
Cedarville University
Parents
  • 0  
    Unfortunately, This is not a known issue.
    The only reported issues occurring after a Windows OS Upgrade is that sometimes an additional reboot or two is required....before all configured services are fully operational again.
    (This seems to impact even Non-ZCM Services...)

    Other than extra reboots after the upgrade.....You seemed to have covered most issues.
    You could test Uninstalling and Reinstalling the CASA MSIs to see if that helps.
    Clearly the agent Upgrade Re-installs SOMETHING.....or that is my guess more than it being an issue with the older version of the agent.....

    And Technically you COULD upgrade Both the Agent and the OS at the same time.......
    The OS Upgrade can actually be delivered via a bundle.....
    There is a cool solution showing how to create a custom bundle and deliver via ZPM....though the use of ZPM is not required for the solution.
    Bundle can have 2 actions....
    Action 1 - Upgrade OS
    Action 2 - Apply Stand-Alone Upgrade Agent.

    Alternately, you can have a bundle just push the stand-alone updater....
    Set to Force-Run with SYSREQ of Older Agent and Windows 1709.
    That way as soon as the OS upgrade is complete...the agent will then upgrade itself............

    --

    If you found this post useful, give it a “Like” or click on "Verify Answer" under the "More" button

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

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

  • 0 in reply to   
    Working with our VAR for Microfocus, we were able to open an SR on this issue and found out that a bug was started Nov 9 and that this is a known issue. The tech said it was going to be fixed with ZCM 2017 Update 2 and they are working on a fix for current systems that are having this issue.

    Thanks for your help Craig!

    Tim Overdorf
Reply
  • 0 in reply to   
    Working with our VAR for Microfocus, we were able to open an SR on this issue and found out that a bug was started Nov 9 and that this is a known issue. The tech said it was going to be fixed with ZCM 2017 Update 2 and they are working on a fix for current systems that are having this issue.

    Thanks for your help Craig!

    Tim Overdorf
Children