Very slow "launch executable" compared to shortcut

Question

In a Zenworks 11.2.3 environment with all Win7 workstations:
In trying to debug a Lotus Notes upgrade package, we separated out the program
launch itself. The launch, a single action, is very simple: Launch Executable
that has the command line "c:\program files\IBM\Lotus\Notes\notes.exe" with the
working directory set as "c:\programs files\IBM\Lotus\Notes" on 32-bit Win7.
The working folder and command line contain "C:\program files (X86)" (etc.)
instead, on 64-bit Win7 stations.
In both cases, the launch action is very slow, and sometimes hangs the Notes
client for a very long time (more than a few minutes).
If I create a shortcut on the desktop with exactly the same for command line
and working directory, it launches vastly quicker -- no more than a few seconds
to fully open.
The environment is one where management wants to launch only out of the NAL
(Zenworks window) and not from a shortcut on the desktop. But the performance
issues are very apparent.
Why is it so much faster to launch from the desktop shortcut than via Zenworks?
What can I look for to pinpoint the source of the slowness, and is there
anything else that I can do other than putting a direct program shortcut on the
desktop? Is this a known issue?
Thanks.
-- DE

Answer 1

It is possible that a "Search" (or Plural) are taking place and hitting
the network.
Not quite sure why F: is getting appended, but it could impact things.
On 3/14/2014 1:50 PM, DE wrote:
> The only difference in the paths (and odd enough as it is) is that the
> one run from CMD.exe directly has "F:" appended to the end; F: is (I
> didn't set this up) set to SYS:\PUBLIC on a Novell server. Whether
> there's anything in that location that would interefere, well, I haven't
> been able to fully investigate yet. But if anything, I would've
> expected just the opposite.
>
> Thanks. I am trying to put more definition around the issue before I go
> further with questions.
>
> -- DE
>
>
> Craig Wilson wrote:
>> Create a Bundle that run CMD.exe as the logged on user.
>> From THAT cmd.exe bundle's command-line session, just type "path".
>>
>> Then from a Std CMD.exe session, type "path".
>> Do they look the same?
>>
>> Echo the results of "set" to a file from both.
>> Do they match?
>>
>> On 3/11/2014 9:04 PM, DE wrote:
>>> In a Zenworks 11.2.3 environment with all Win7 workstations:
>>>
>>> In trying to debug a Lotus Notes upgrade package, we separated out the
>>> program launch itself. The launch, a single action, is very simple:
>>> Launch Executable that has the command line "c:\program
>>> files\IBM\Lotus\Notes\notes.exe" with the working directory set as
>>> "c:\programs files\IBM\Lotus\Notes" on 32-bit Win7. The working folder
>>> and command line contain "C:\program files (X86)" (etc.) instead, on
>>> 64-bit Win7 stations.
>>>
>>> In both cases, the launch action is very slow, and sometimes hangs the
>>> Notes client for a very long time (more than a few minutes).
>>>
>>> If I create a shortcut on the desktop with exactly the same for command
>>> line and working directory, it launches vastly quicker -- no more than a
>>> few seconds to fully open.
>>>
>>> The environment is one where management wants to launch only out of the
>>> NAL (Zenworks window) and not from a shortcut on the desktop. But the
>>> performance issues are very apparent.
>>>
>>> Why is it so much faster to launch from the desktop shortcut than via
>>> Zenworks? What can I look for to pinpoint the source of the slowness,
>>> and is there anything else that I can do other than putting a direct
>>> program shortcut on the desktop? Is this a known issue?
>>>
>>> Thanks.
>>>
>>> -- DE
>>
>>
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.