Marc Jacobs
asked on
Allow terminal services users to run program as administrator
Hi
I'm trying to resolve a problem with running Sage 2009 and 2010 in terminal services mode on Windows Server 2008. Users log on via remote desktop connection, and we have a group policy set up to load the software and a seperate logon script that runs in order to copy a file to a working directory to point the program at the correct data set.
I'm getting an intermittent error which Sage informs me is because I need to allow users to run Sage with administrative privileges. They advise I do this by ticking the "run this program as an administrator" tickbox in the compatibility tab when going to the properties on the .exe file, and to do this as well in the settings for all users.
The problem I'm getting is that as soon as I tick the box for all users, then try to log on as a user, the system gets to the point where Sage should load, then it instantly logs me off without any further input. I desperately need to get this working, does anyone know why this would happen? Is it something in the group policy or local policy settings that's causing the instant logoff?
Thanks
Sam
Teknite
I'm trying to resolve a problem with running Sage 2009 and 2010 in terminal services mode on Windows Server 2008. Users log on via remote desktop connection, and we have a group policy set up to load the software and a seperate logon script that runs in order to copy a file to a working directory to point the program at the correct data set.
I'm getting an intermittent error which Sage informs me is because I need to allow users to run Sage with administrative privileges. They advise I do this by ticking the "run this program as an administrator" tickbox in the compatibility tab when going to the properties on the .exe file, and to do this as well in the settings for all users.
The problem I'm getting is that as soon as I tick the box for all users, then try to log on as a user, the system gets to the point where Sage should load, then it instantly logs me off without any further input. I desperately need to get this working, does anyone know why this would happen? Is it something in the group policy or local policy settings that's causing the instant logoff?
Thanks
Sam
Teknite
ASKER
Hi
Thanks for the response! I've run process monitor but I'm not sure what I'm looking for in the output. I've filtered by the test user I'm logging on with and get pages of output, the only "unsuccesful" report in it is detailed below:
Date & Time: 17/12/2009 16:46:35
Event Class: File System
Operation: CreateFile
Result: UNSUCCESSFUL
Path: \Device\RdpDr\;:5\tsclient \Z
TID: 4772
Duration: 0.0022122
Desired Access: Read Attributes
Disposition: Open
Options: Open Reparse Point
Attributes: n/a
ShareMode: Read, Write, Delete
AllocationSize: n/a
I'm not sure what this means however. I've also tried filtering by the application I'm running in terminal services mode, and this only comes up with a few items, none of which are unsuccessful. My next plan is to test with Notepad to see if the same thing happens, as I really need to know whether it's a Sage problem or a Windows problem.
Thanks for the response! I've run process monitor but I'm not sure what I'm looking for in the output. I've filtered by the test user I'm logging on with and get pages of output, the only "unsuccesful" report in it is detailed below:
Date & Time: 17/12/2009 16:46:35
Event Class: File System
Operation: CreateFile
Result: UNSUCCESSFUL
Path: \Device\RdpDr\;:5\tsclient
TID: 4772
Duration: 0.0022122
Desired Access: Read Attributes
Disposition: Open
Options: Open Reparse Point
Attributes: n/a
ShareMode: Read, Write, Delete
AllocationSize: n/a
I'm not sure what this means however. I've also tried filtering by the application I'm running in terminal services mode, and this only comes up with a few items, none of which are unsuccessful. My next plan is to test with Notepad to see if the same thing happens, as I really need to know whether it's a Sage problem or a Windows problem.
ASKER
Edit to above: I can't test with notepad, as there is no run as administrator option. Any other suggestions for testing this?
What you need to look for with process monitor is "access denied" messages, like I show on the guide. Do you see any of these at the time the application throws an error to the user?
Cláudio Rodrigues
Citrix CTP
Cláudio Rodrigues
Citrix CTP
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Problem solved by turning off user account control on the server.
Cláudio Rodrigues
Citrix CTP