Group Policy 'Desktop' lockdown impacts Classic Start Menu
Start menu and Windows enhancement software
Brought to you by:
ibeltchev
Menu
▾
▴
#186 Group Policy 'Desktop' lockdown impacts Classic Start Menu
We run in a Terminal servier environment and have the following GPO setting in place to prevent users from changing their desktop settings:
User Configuration\Administrative Templates\Desktop\Hide and disable all items on the desktop - Enabled
With this setting in place we have found that the Classic Start Menu does not function as expected when users left click on the desktop after expanding the Start Menu. We would expected the Classic Start Menu to minimise back to the start button, but after a single left click on the desktop nothing happens. Also if the user left clicks twice, the Classic Start Menu does minimise, but the standard Windows Start menu is left in it's place. This of course will lead to some confussion for the users.
When we remove the GPO setting, the Classic Start Menu functions as expected.
Hope this description is clear enough to follow - please let me know if you need anything further.
Cheers,,.
As we established in the other discussion, this is not related to Classic Shell. Uninstall it and you'll see that the default start menu behaves the same way.
This GPO makes the Desktop ignore single clicks, and makes double clicks open the start menu. Why? I don't know. There is nothing I can do about this because the Desktop is a protected window. It is implemented by the CSRSS process.
Also if the users double click at any time on the Desktop, the Standard Windows Start Menu appears.
OK thanks for the responce....
BTW, looks like this behavior has been there since at least Windows XP.
I have managed to get around this issue by removing the GPO setting and using other GPO settings and registry permissions to lockdown the user access to the Desktop.