Welcome Serena Central users! CLICK HERE
The migration of the Serena Central community is currently underway. Be sure to read THIS MESSAGE to get your new login set up to access your account.
Highlighted
nathelpdesk
New Member.
1096 views

Launch action "delay" does not recognize process explorer

Hi folks,

we are working with ZCM11.3 latest updates and wanted to launch an application with user login, but not before the user desktop has fully started. Therefore we thought, we might just look out for "explorer.exe", which, being the user shell, finally pulls up the desktop.
Unfortunately we cannot get the "delay" action to actually see the process on our Windows 7 64bit machines. We tried different spellings including just "explorer.exe", nothing works. Even when started from a fully initialized user environment, the bundle would not be aware of explorer as an existing process. However replacing that process by other programs, there is no problem at all.

Anyone has some useful idea, how to resolve this or why this is happening? We would very much appreciate your contribution to that topic.
Thanks

nat-admin
Labels (2)
0 Likes
2 Replies
Anonymous_User Absent Member.
Absent Member.

Re: Launch action "delay" does not recognize process explorer

I have not tested this, but I don't see how this would accomplish
anything......

Explorer.exe loads LONG before you even see a desktop.
It loads almost instantly after you have entered your credentials.

You would be better served by keying on later loading user processes,
such as perhaps ZenNoticyIcon.exe and then adding an brief additional
delay based upon some std delays in your environment between that
process loading and the desktop being ready.


On 10/9/2014 1:16 PM, nat-admin wrote:
>
> Hi folks,
>
> we are working with ZCM11.3 latest updates and wanted to launch an
> application with user login, but not before the user desktop has fully
> started. Therefore we thought, we might just look out for
> "explorer.exe", which, being the user shell, finally pulls up the
> desktop.
> Unfortunately we cannot get the "delay" action to actually see the
> process on our Windows 7 64bit machines. We tried different spellings
> including just "explorer.exe", nothing works. Even when started from a
> fully initialized user environment, the bundle would not be aware of
> explorer as an existing process. However replacing that process by other
> programs, there is no problem at all.
>
> Anyone has some useful idea, how to resolve this or why this is
> happening? We would very much appreciate your contribution to that
> topic.
> Thanks
>
> nat-admin
>
>



--
Going to Brainshare 2014?
http://www.brainshare.com
Use Registration Code "nvlcwilson" for $300 off!


Craig Wilson - MCNE, MCSE, CCNA
Novell Technical Support Engineer

Novell does not officially monitor these forums.

Suggestions/Opinions/Statements made by me are solely my own.
These thoughts may not be shared by either Novell or any rational human.
0 Likes
nathelpdesk
New Member.

Re: Launch action "delay" does not recognize process explore

Thank you for your reply, Craig.

Of course we may discuss about sense or nonsense of our intention.

What you explained for explorer.exe, simply is not true. The deskotp will load only, when the login script is fully finished. This is easy to check by a paused command line script. You will see everything start but explorer.exe. Only when login script is through, explorer will start (and be seen in the process list) and the desktop will build up. In contrary to that, all windows run registry key programs would not wait but start right away. So that is why explorer.exe was our choice.
Moreover, the login script run time is the only time to prevent (not fire proof) the user from interfering in update and installation processes, that might happen here in a controlled order. Due to that, a simple delay period would not do the job, as the needed time is unpredictible.

So you bend my question into a different direction, instead of telling, why explorer.exe is undetectable for the Zenworks agent.

However, you also offered a workaround, that resolves this problem. ZenNotifyIcon.exe does the job very well. We can only assume, that this EXE is started by the zenworks agent itself, after the desktop has been set up. We could not find it as a process called by Windows auto start routines.Anyways, it is working fine for that.

So thank you, Craig for this solution. This is what we needed to find.

regards
nat-admin
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.