Sometimes on some machines for reasons unknown, when users exit GW the process keeps running and you need to kill the process or reboot the machine before you can start GW up again. How can this be fixed without a reboot or killing the process?
Are you up to date on the version of the GW client?
Have you scanned the PC for malware (use MalwareBytes Anti-Malware)
Have you tried it in Safe Mode with Networking? If it closes fine there, look at all the processes running when in regular mode with Autoruns and reduce things not needed to see if one of them is helping to hold GW open.
There is no malware on that machine that I have detected.
I have not started GW in Safe Mode.
I am not using the client to access a restore point via file.
I also do not know when and what updates/patches the networking people are sending out to machines until after the fact. I got no notice this week that they had sent anything out.
You are fighting a losing battle trying to save GW. Everyone wants Microsoft Outlook on the client side and they sort of imply Exchange on the back-end as a de facto standard. Novell should just give up on Groupwise now and avoid the rush later.
Note I DIDN'T say that the M$ product was BETTER. It's just got that 800 pound gorilla thing going for it.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.