How do you log OUT of Groupwise? It used to be that I would close the
window, close notify and then the next time I ran GroupWise, the login
prompt would come.
Since the company upgraded to GW7, I don't get that anymore. I close
Notify, I close the window -- and when I reload it's there. It's my
account again.
I've tried killing the process with taskmanager, and I've even tried
using the system command taskkill.exe with the /t toggle which kills
any child process created by grpwise.exe.
I don't want to have to reboot the terminal every time someone wants
to log into their email account.
Please help!
try this:
In the GroupWise Client go to Tools -> Options -> Security
Set a password if not done yet
and/or
Disable "Use single sign-on" and "No password required with eDirectory"
If you close the GroupWise Client AND Notify, GroupWise will ask for the
password given above when you'll start it.
To start the GroupWise Client with different user names during the same user
is logged in, you have to modify the link to
"C:\Novell\GroupWise\grpwise.exe /@u-?", then you will be asked for the
username and password.
Hope that helps?!
Greets
Klaus
"ebrian" <ebr...@gmail.com> schrieb im Newsbeitrag
news:96326520-9360-4a51...@p59g2000hsd.googlegroups.com...
Sorry I never responded.. I only checked this today. This year has
absolutely blown by hasn't it?
Anyway -- I don't seem to have that option.
The trouble I was having was that when I didn't shut off my computer
every night (at work), for some reason the groupwise client would
start making multiple connections to the server some time around 4am.
We couldn't figure out why.
For me, I like to just lock my computer before I leave for the day,
and sometimes I would forget to shut down Groupwise and this multiple
connections thing would pop up and someone from the administration
office would eventually be called in the middle of the night and be
really really angry at me the following day. So I tried to set up a
taskkill for grpwise.exe, hoping that it woudl properly shut down and
then I wouldn't need to log off every night.
Unfortunately when I did this, I had the problem of it not properly
logging off, and thus the error would still occur even though all the
grpwise tasks were killed.
I'm still looking for a solution to this.