Here is some additional information about Formativ and Citrix:
Formativ itself does not have any operational conflicts with Windows Terminal Services (WTS) nor Citrix, apart from the inherent dependency on the GroupWise C3PO architecture. The GroupWise C3PO architecture uses the Windows HKEY_LOCAL_MACHINE registry hive to store user specific C3PO settings, which according to the Microsoft documentation, is not compatible with WTS (because all users inherit HKEY_LOCAL_MACHINE settings in a WTS/Citrix environment).
Even with this GroupWise design limitation, GroupWise/Formativ should still work within the Citrix environment. The only practical problem is likely to be if your users do not have the appropriate rights to write to the HKEY_LOCAL_MACHINE registry hive. This could be overcome by providing those rights to every user, or by installing a master GroupWise/Formativ configuration, including the applets, for a special user who does have the appropriate registry rights. Alternatively, it could also be possible to extend the registry by manually creating the required entries under the HKEY_LOCAL_MACHINE hive.
The Formativ warning message arises when, upon startup, it tests read/write access to the following registry key area:
HKEY_LOCAL_MACHINESOFTWARENovellGroupWise5.0C3PODataTypes
Read/write access to this area is required for registering GroupWise events and other client integrations which may be used by Formativ and Formativ applets. This is a standard GroupWise third party integration requirement. Read/write access is usually required beyond initial admin installation because applets dynamically register for the events at time of their first execution.
A GroupWise integration registry entry looks like:
HKEY_LOCAL_MACHINESOFTWARENovellGroupWise5.0C3PODataTypesGW.MESSAGE.MAILAdvansys.formativEventsGW#C#REPLY
and in this case, it indicates that an applet or C3PO has registered to be notified when a Mail message REPLY event is activated (a user replies to a mail message).
If Formativ cannot write to this area, applets cannot register for events or other client integrations (toolbars, menus).
Possible Solutions
OPTION (1) Modify ‘limited user’ profile security to allow additional registry access.
a) allow read/write access to ‘HKEY_LOCAL_MACHINESOFTWARE’ hive; or
b) allow read/write access to ‘HKEY_LOCAL_MACHINESOFTWARENovellGroupWise5.0C3PODataTypes’ hive.
OPTION (2) Create registry entries during initial admin installation.
i) Create HKEY_LOCAL_MACHINESOFTWARE entries during main Admin installation.
The admin install should create automatically:
HKEY_LOCAL_MACHINESOFTWAREAdvansys Corporationformativ1.0
The admin install should create automatically some settings in:
HKEY_LOCAL_MACHINESOFTWARENovellGroupWise5.0C3PODataTypes
For applet solutions, when in Admin mode, you would need to install EVERY applet which the limited user will need to run. This will ensure all the appropriate HKEY_LOCAL_MACHINESOFTWARENovellGroupWise5.0C3PODataTypes entries are written. You can then choose to replicate this registry key hive to other machines which need to run the same applets.
You will need to repeat step i) each time you add an applet which uses a GroupWise client event which is not already registered.