Discussion Locked

2 instances of novell application explor

0 helpful
9 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
We upgraded to Zenworks 2.0 from Zen 1.1 and now are getting 2 instances of application explorer running on the same client computers. It is network wide but not on all machines. we are running win 95 with novell client 3.1. Any suggestions on this or has anyone ran into it?

9 replies

by jeff1410

Look at where the App Exlorer is being run from. If you run it from the container login script is it in there twice? Is it a statement in the user login and container script?

by shanepj

we completely disabled scripts and it still runs for some people.

Thank you for the suggestion!

by golfkinguk

I had the same thing happen. It is getting called twice. In my case there were 2 instances in the login script. One was with a win9x variable, the other was with an NT variable. Both were running for any machine. Also check that it is not getting called via 2 group associations. My script reads:
REM ***** Added for ZENWORKS LAUNCHER 19.2.2000 - Ron King *****

IF MEMBER OF "NAL_USERS.GROUPS" THEN BEGIN

#Z:\NAL.EXE
END

Hope this helps.

Ron

by shanepj

this is not in the script at all as we disabled them and we still get it. Also any user can log onto the machine and we still get the problem

by shanepj

this is not in the script at all as we disabled them and we still get it. Also any user can log onto the machine and we still get the problem

Thank you for the suggestion!

by kharrison

I too have had this happen. In my case it was in two different login scripts, ie. in a individual and a container script. Also check profile login scripts. Do not assume that only one script is being executed. This can be especially confusing when profile scripts call other profile scripts.

by shanepj

this is not in the script at all as we disabled them and we still get it. Also any user can log onto the machine and we still get the problem

by shanepj

this is not in the script at all as we disabled them and we still get it. Also any user can log onto the machine and we still get the problem.

Thank you for the suggestion!

This discussion is closed to new replies.