Utility Manager (Windows key + U)

[PiqueABoo]

I'm struggling to google an effective way to turn this and the narrator bits off a) on logon desktop, b) for all but a specific group when logged on. Not least because utilman.exe runs as system.

 

I'm increasingly tempted to just map out the Windows key, but I don't want to. Does anyone know the perfect (centrally deployable) solution for this?

[Dom_]

Can't the windows + # hotkeys be disabled through GP? I'm sure I've seen that somewhere before....

[azrael78]

Not sure - we did the 'disable run' GP bit but when we did Windows + R - it let them still run stuff, so we've taken the route of disabling the windows key itself.

 

Peace.

 

Az

[PiqueABoo]

Best I can do so far is to use GPO to deny 'traverse folder/execute file' for utilman.exe

 

[Windows + R causes a "This operation has been cancelled..." for me so I must have taken that out with a GPO setting somewhere]

[Gatt]

There is a GP for the windows keys..

 

user config-> Admin Templates -> Windows Components -> Windows Explorer -> Turn Off Windows+X hotkeyss

[FreeWill]

If you have a Machine Group Policy you can fix this.

 

Create a new software restriction policy. Go to additional rules. Create a new path rule, the path being "C:\WINDOWS\system32\utilman.exe" and set to 'Disallowed'.

 

Apply the policy on a test machine to make sure it does what you need with no side effects, I'm 99% sure it does.Tthis also stops it running on the logon screen as it is applied at machine level.

 

We also had a problem a few months ago of students launching utilman at the logon screen, I believe this was the tried & tested fix.

[PiqueABoo]

If you have a Machine Group Policy you can fix this.

 

That's what I did but with NTFS ACEs instead.

 

The other one that's similarly annoying is the XP "Help and Support.." - I just disabled the service way back whenever, but why did it have to be service?

[sarchs]

If you have a Machine Group Policy you can fix this.

 

Create a new software restriction policy. Go to additional rules. Create a new path rule, the path being "C:\WINDOWS\system32\utilman.exe" and set to 'Disallowed'.

 

Apply the policy on a test machine to make sure it does what you need with no side effects, I'm 99% sure it does.Tthis also stops it running on the logon screen as it is applied at machine level.

 

We also had a problem a few months ago of students launching utilman at the logon screen, I believe this was the tried & tested fix.

 

I have tried making this policy but it makes no difference the utility manager loads up at the logon screen. I have googled this problem and cannot get it to work, any help or guidance would be greatfully received

[sarchs]

bump...

[Guest TheLibrarian]

This is a brute force all off solution and takes time to implement: Use nLite to remove the feature.