[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 306
  • Last Modified:

Server 2003 Terminal Services Color Depth

My environment:

I am currently running a few 2003 servers using terminal services. At the moment I have it set to only run 8bit color whenever anyone connects to it. My users connect to the server using thin clients made by wyse. Thin clients arent join to AD and use a dumb down wyse os.

My Issue:
The 8 bit has been working very well. However some websites do not render properly because of the 8 bit being forced. I am looking for a way to script / create a policy that would allow me to give certain users permission to see 15 bit instead of 8 when they login on a thin client. I have only been able to see a GPO that applies on the computer side and not on the user side (which is what I would need).
0
RVOps
Asked:
RVOps
  • 3
  • 2
1 Solution
 
MinoDCCommented:
Create the GPO and then assign it to the specifed users

view here:
http://www.windowsnetworking.com/articles_tutorials/Group-Policy-Security-Filtering.html
0
 
RVOpsAuthor Commented:
Hey MinoDC,

Thank you for the article. My thinking pattern on how to deploy this, looks for be similar to that article. The main issue I am coming across in this route is the GPO is a computer policy and not found user the user configuration.

Computer Configuration --> Administrative Templates --> Windows Components --> Terminal Services --> Limit maximum color depth

0
 
MinoDCCommented:
Ok....try in thi way
Create a GPO to Computer level
Access to the PC domain, where the policy must be applied to 15bit.
Find the registry key:
 HKLM \ SOFTWARE \ Policies \ Microsoft \ Windows NT \ Terminal Services ---> = 15 ColorDepth
Use a registry export of the registry key and save it in a location on AD server
From GPO, go to User -> startup script doing something like "regedit / s myReg.reg" to import it
Apply Filter to the Security Policy


View the reg key parameter
0
 
RVOpsAuthor Commented:
I gave it a try even though I didnt think it would work. It still uses the computer registry instead of per user. I did however find a way to set the limit on the client side and created a script to do this.
0
 
RVOpsAuthor Commented:
Found out the solution self
0

Featured Post

Concerto's Cloud Advisory Services

Want to avoid the missteps to gaining all the benefits of the cloud? Learn more about the different assessment options from our Cloud Advisory team.

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now