Setting GroupWise Client as default mail Client in Windows Vista

  • 3217110
  • 19-Nov-2007
  • 27-Apr-2012

Environment

Products:
Novell GroupWise 7 Support Pack 2
Novell GroupWise 7 Support Pack 2 HotPatch 1a
Microsoft Windows Vista

Situation

Symptoms:
Setting GroupWise Client as default mail Client in Windows Vista
Making GroupWise the default mailto Client in Windows Vista
Unable to set GroupWise Client as the default Client in Windows Vista

Resolution

Corrective Actions:
1. While installing GroupWise on Windows Vista, make sure that Typical setup is selected or if Custom setup is selected, do not deselect "Internet Browser Mail Integration"
2. If Outlook is installed first and then GroupWise, GroupWise becomes the default mailto client and is the client that gets launched when File | Send To is selected from any application.
3. If GroupWise is installed first and then Outlook, Outlook becomes the default mailto client and is the client that gets launched when File | Send To is selected from any application. Please make the following registry changes after backing up the registry to make the GroupWise Client the default Client

HKLM\SOFTWARE\Clients\Calendar and change the Default Key to"GroupWise" without quotes
HKLM\SOFTWARE\Clients\Mail\ and change the Default Key to"GroupWise" without quotes
HKLM\SOFTWARE\Classes\mailto\DefaultIcon and change the Default Key to "C:\Novell\GroupWise\gwmailto.exe,0" without quotes
HKLM\SOFTWARE\Classes\mailto\shell\open\command and change the Default Key to "C:\Novell\GroupWise\gwmailto.exe /%1" without qutoes

It has been seen that changing the registry is the only method to make GroupWise Client the default Client if Outlook is installed after GroupWise Client.

GroupWise Client cannot be seen in Start | Control Panel | Programs | Default Programs | Set Default Programs. This has been fixed in the next release of GroupWise.
GroupWise Client can be seen in Start | Control Panel | Programs | Default Programs | Set program access and computer defaults | Custom but making any change here does not affect anything. This has been fixed in GroupWise 7 Support Pack 3