ZAPP Window and systray Icon are related processes in ZCM 2017.
So in several situations when ZAPP Window is starting up it is not recognizing any startup parameters because the parent process is already running (due to previous startup of zenicon.exe, etc.)
If ZAPP is started via OES Loginscript the startup parameters get ignored all the time.
To kill zapp.exe processes before starting ZAPP again is not a charming solution.
And before you ask - starting ZAPP via RUN Key is not a solution because ZEN Explorer Policies are not effective at this time. So the user can do things until the policy is in effect I want to prevent.
So please divide the ZAPP from other processes again or do anything else to make startup switches really working again.
Thanks Tobi
by: Tobias F. | over a year ago | Other
Comments
ZENworks 2017 Update 1 addressed this by adding new commandline switches back that can be used for these use cases. Please refer to the What's New documentation.