Preventing GroupWise from trying to startup when Disconnected
Novell Cool Solutions: Tip
By Tommy Mikkelsen
Digg This -
Posted: 14 Mar 2001
Current Version: GroupWise 5.5 EP
We recently ran the following Q&A, and Tommy has provided another couple of ideas to solve this problem:
S. wrote: I'm running GroupWise 5.5.4 (client). What I'm looking for are some suggestions for how I can set up GroupWise on my laptop PCs, so that when they are off the network, if GroupWise is in the startup, it won't spin forever and try to start up. I usually end up doing ctrl+alt+delete to stop it from trying to start. Any thoughts?
We checked with our experts, and it seems there are several ways, but the third one is the one we'd suggest.
- You could use Windows Profiles and generate two Start up folders.
- You can edit the autoexec.bat file and create a batch file that would ask Are you connected to the network? And if they answer Yes, then copy Notify or GroupWise to the startup folder, or else delete it from the startup folder.
- But the easiest thing to do is to add the /@u-? switch at the end of target line in that shortcut. This will ask who wants to log in and you can click on Cancel if you are not connected to the network. It will also let you select GroupWise remote if you'd rather. But best of all it stops waiting and waiting and waiting for it to find the network.
Instead of putting Notify and/or GroupWise in the startup-folder, do the following:
- Add a Forced Run ZEN-App that launches the two products. This way, they'll only start when the user is authenticated to the "One Net".
- One could make a Run Once ZEN-App, that adds an icon on the desktop named "GroupWise Remote", with the parameters "/ps-path to remote location".
If you have any questions you may contact Tommy at firstname.lastname@example.org
Novell Cool Solutions (corporate web communities) are produced by WebWise Solutions. www.webwiseone.com