New
#20
That policy is set to "Not Configured" by default to not be disabled, so it may have been an accidental click or something deployed with it set.Hi Brink and thanks for the speedy reply.
I'm that guy as well. Let me explore this avenue and thank you. I actually remoted into those 8.1 machines and the setting is grayed out there as well. So I gave you some bad info, I apologize.
I don't set group policy on local machines so it will have to be at the domain level on the server. Although I can't imagine why I would set that policy so maybe it was a wild click in the middle of the night setting up the server four or so years ago?? I guess I'll find out soon enough.
Yes, that policy is enabled in the Default Domain Policy, but I don't know why. I went through all the policies and specifically remember why I set most of the policies. I also see in Details that the policy was created on 7/26/2015, when I set it up. It also says it was modified on 6/11/19. I'll admit I could forget something I did 4.5 years ago, but I'm fairly sure that I'd remember something I did to a Default Domain Policy 6 months ago.
Is there a possibility this change was part of an update or patch for a vulnerability? 'Do not allow taskbars on more than one display' AND 'Prevent users from moving taskbar to another screen dock location' are enabled. I don't know why I would have enabled those......unless it happened in the middle of the night.
Thanks again and regards,
Jackrabbit13