ZENworks - Bundles starting via ZAPP are always opening in background (behind ZAPP)

Hi,

I just got reported a strange behaviour, that bundles, which are started via ZAPP, are always starting behind this.
Depending of the application you sometimes just see the icon at the taskbar. So for some people not the best user experience.

They are running Windows 11 22H2, also some machines with Windwos 11 23H2 and with ZENworks 23.3.

I also was able to replicate this (for both windows versions) and now I am just surprised, that now it is the first time I have heard of this. None other customers have reported this.

I know that the support for Windows 11 23H2 is comming with ZENworks 23.4, but since this behaviour also occures with the previous Windows versions, I just wanted to ask if someone else noticed this or if I am missing something?

So far I was not able to find some helpful entries in the Knowledge Base or somewhere else.
I just found the following:
www.novell.com/.../bvj1efc.html

There is the option "DisableForegroundLockTimeoutReset" mentioned to prevent newly launched applications from moving int the foreground, but so far the customer is not using this and in my environment the option is also not setted.


Thanks and regards
René

Parents
  • 0  

    Hi Rene,

    See - www.elevenforum.com/.../

    In short,  ForegroundLockTimeout  is a Registry Setting that controls the ability of new processes to "Take Focus".
    By Default, we set to "0", to ensure apps launched from ZAPP take Focus.

    However, changes to this value only take place after Explorer.exe is restarted.

    When the user's log into a PC, is is normally via a FRESH Profile because they move alot or are using Volatile DLU?
    If so, you may need to update the Default Profile so new profiles have this value....

    Further, as a Test check the value of ForeGroundLockTimeout and verify it's 0.
    Then restart Explorer.exe and test to see if you see the same issue.

    Did it work after restarting Explorer.exe?  Was the Value already 0 as expected?

    --

    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

Reply
  • 0  

    Hi Rene,

    See - www.elevenforum.com/.../

    In short,  ForegroundLockTimeout  is a Registry Setting that controls the ability of new processes to "Take Focus".
    By Default, we set to "0", to ensure apps launched from ZAPP take Focus.

    However, changes to this value only take place after Explorer.exe is restarted.

    When the user's log into a PC, is is normally via a FRESH Profile because they move alot or are using Volatile DLU?
    If so, you may need to update the Default Profile so new profiles have this value....

    Further, as a Test check the value of ForeGroundLockTimeout and verify it's 0.
    Then restart Explorer.exe and test to see if you see the same issue.

    Did it work after restarting Explorer.exe?  Was the Value already 0 as expected?

    --

    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

Children