X
xrees
Guest
This was a good one.
The Terminal Server OU was put in a LOCKED DOWN state, before we came
on site.
Users could barely do anything from the Start Menu.
Which for most cases is a good thing.
Unfortunately, one of things they couldn't do was set their DEFAULT
PRINTER. When they tried to right-click on a printer to set it to
default, the context menu would NOT appear.
Ouch.
So after hunting the Internet for every possible fix for why Terminal
Server Clients couldn't set their DEFAULT PRINTER, the answer actually
lay in something deeper (and simpler) than that. They actually
couldn't RIGHT CLICK on anything.
So after browsing thru the LOCKDOWN policy for the OU, I found the
following entry:
User Configuration\Administrative Templates\Windows Components\Windows
Explorer\Remove Windows Explorer's Default Context Menu - Enabled
Disabled it, giving the users the ability to RIGHT-CLICK on things.
Including being able to set the DEFAULT PRINTER.
LMK
The Terminal Server OU was put in a LOCKED DOWN state, before we came
on site.
Users could barely do anything from the Start Menu.
Which for most cases is a good thing.
Unfortunately, one of things they couldn't do was set their DEFAULT
PRINTER. When they tried to right-click on a printer to set it to
default, the context menu would NOT appear.
Ouch.
So after hunting the Internet for every possible fix for why Terminal
Server Clients couldn't set their DEFAULT PRINTER, the answer actually
lay in something deeper (and simpler) than that. They actually
couldn't RIGHT CLICK on anything.
So after browsing thru the LOCKDOWN policy for the OU, I found the
following entry:
User Configuration\Administrative Templates\Windows Components\Windows
Explorer\Remove Windows Explorer's Default Context Menu - Enabled
Disabled it, giving the users the ability to RIGHT-CLICK on things.
Including being able to set the DEFAULT PRINTER.
LMK