|
|
|||
|
|||
|
We recently upgraded our server with the terminal server role. We uninstalled CommitCRM then installed it again in TS install mode.
It runs when logged in as admin on the server, but not as a regular rdc user. Anything special we have to do? We already have the sql upgrade. |
|
|
|||
|
|||
|
Normally there's nothing special you need to do. Once you have SQL installed it should all work, just like it does when you log in over Terminal Services session as an Admin. The fact that it does not work as a standard domain user may indicate that this has to do something with privileges. Please verify that all users have full access rights to the entire RangerMSP folder tree. Also, please let us know exactly what does not work with a standard user - an error message or just the prompt that SQL is required for TS, etc.
|
|
|
|||
|
|||
|
There is something awry.
CommitCRM just blinks when you click on it. It never opens. The CommitCRM folder on the server has sharing:everyone full and under security:everyone full (just to test) Neither makes a difference. Is there some soft of error logging to see from the client side(on the desktop) It works for admin users so there has to be a way to get it to work for regular users. |
|
|
|||
|
|||
|
We just sent you an email. In short - it has to be related to privileges because it runs well for a domain admin user. RangerMSP client is not really installed on each PC, all you have is a shortcut to a file on the server, that's it. So we have not local settings for RangerMSP client to run and as it runs for admins it is all about privileges/policies.
|
|
|
|||
|
|||
|
As suspected it was privileges. The top level access was not fully replicating down to the sub-folders.
Removed inherit permissions and re-checkered for sub-folders seem to have fixed the issue. We'll know for sure monday once all the staff starting use the system again. |
