We have 6 citrix servers. Users who are part of the Domain Users can only run VB code on 3 out of the 6 servers. According the Microsoft, we are to modify the permissions on the entire HKCR\CLSID to full control in order to run VB code or open up the vb editor within Great Plains. Once we do this on the 3 servers where it is not working, the VB code then does run, but why do the other 3 work (ie permissions on the same key on the other 3 servers are read/execute only?
I also have other issues where some users receive the error "Cannot get printer context" when they print something. If they go to file > print setup and click okay (ie the default printer is there as default), they can print until they log out. All the dex.ini files have same permissions and we do not use Named Printers, nor do we want to set it up. It seems that every printer name appears in each of the local dex.ini file, so everytime a user accesses Great Plains via citrix it adds a line in there (as each users' printer name is unique ie client\computername\printersharename).
Is anyone else having multiple issues around security in citrix? All other applications run fine in this evironment. We shouldn't have to manually mess with local security permissions to have the application run. They were all installed via add/remove programs.
I also have other issues where some users receive the error "Cannot get printer context" when they print something. If they go to file > print setup and click okay (ie the default printer is there as default), they can print until they log out. All the dex.ini files have same permissions and we do not use Named Printers, nor do we want to set it up. It seems that every printer name appears in each of the local dex.ini file, so everytime a user accesses Great Plains via citrix it adds a line in there (as each users' printer name is unique ie client\computername\printersharename).
Is anyone else having multiple issues around security in citrix? All other applications run fine in this evironment. We shouldn't have to manually mess with local security permissions to have the application run. They were all installed via add/remove programs.