|
|
Question : Problem: Managing Terminal Service via Group Policy Issue
|
|
I am having some issues getting a program to properly start running that I have defined in a group policy.
If I set the same program on the users Terminal Service Profile setting the program starts as planned. But if I set it in Group Policy it does not.
I have made sure I do not have any settings which would overide the program starting and have read many detailed articles on the subject.
It seems very odd but maybe I am missing something obvious.
I do not have al lot of TS experience but generally know my ay around a network.
This is a small domain with about 25 users accesing the TS. Some of them access it via a WEB PAGE set up to point to the server while others use Remote Desktop. I am NOT on the same domain when I connect to Terminal services.
Is there a delay with getting a GPO to take effect for users not on the domain?
Thanks for the assistance
|
Answer : Problem: Managing Terminal Service via Group Policy Issue
|
|
Can you make a more obvious setting within the GPO (Desktop Wallpaper or something) to confirm the GPO is applying?
I have tested the timeouts and they were taking effect.
Can a local or Web Policy ever take precedence over a GPO? I always thought that a GPO was the end all highest priority.
|
|
|