Conflicts between ZENworks and GroupWise Notify
Novell Cool Solutions: Tip
Digg This -
Posted: 13 Jun 2001
Current version: ZENworks for Desktops 3
We posted this Q&A recently, and Jean-Paul Otto of the Netherlands sent us his own solution. Check it out, and if you have any other ideas, please let us know.
MS wrote: At a customer using NSBS 5.1 using GW5.5 (with SP4 applied) we very frequently have the problem that at startup time (after login) when the ZENworks Application Explorer is loading AND Groupwise Notify is loading, that one or the other will lock up. Sometimes you can kill the locked application and continue operating normally. Sometimes you can't and you have to reboot. On three stations that had this problem the most, we removed the Application Explorer from their login script and forced them to manually launch the Application Explorer (by creating an shortcut on their desktop for it.)
This eliminates the problem but is a royal pain in the b-tt. How can I fix it?
One expert we checked with had this problem too and he put GW Notify to start as an application within the Application explorer. He also numbered any start-up apps so that they ran individually in order so as to reduce conflicts.
We fix the problem for our customers by starting up NAL or NALEXPLD with a timed delay of 10 seconds by using the "/time 10" commandline parameter.
This gives the system the time to autostart all other programs before ZEN is loaded. For us it fixes the Notify problem and a lot of other startup hangs and conflicts.
If you have any questions you may contact Jean-Paul at email@example.com
Novell Cool Solutions (corporate web communities) are produced by WebWise Solutions. www.webwiseone.com