The system cannot access one or more event logs because of insufficient rights
Configuration refresh message. The system cannot access one or more event logs because of insufficient rights, file corruption, or other reasons. For more information, see the Operation channel in the ServerManager-ManagementProvider error log on the target server.
Problem occurred on Server 2012 servers that have been upgraded to Server 2012R2 servers. Servers are also clustered.
Following the event logs leads to a few registry keys. You can eliminate the messages by:
1. Export the following registry keys (for safety)
Access to drivers on Windows Update was blocked by policy EventID:122 errors appearing on Windows
Server 2012 Hyper-V host.
“Device Setup Manager” service. There is a scheduled task that runs each night
in “Microsoft | Windows | Device Setup” called “Metadata Refresh”. When that task runs it causes the “Device
Setup Manager” service to start, and that’s what is causing the messages. If you look in the Event Viewer under
“Application and Services Logs | Microsoft | Windows | DeviceSetupManager |
Admin” and filter on Event ID 122 then you can see the entries.
The “policy” that is causing the block is actually the Device Installation
Use the search in the
Control Panel window and look for “device installation” When that window
opens, you will see the settings that define the “policy” If you change the
setting to “Always install the best driver software from Windows Update.” then
the Event ID 122 errors will go away. If you *also* select
the “Automatically get the device app…
root\cimv2\TerminalServices namespace is marked with the RequiresEncryption flag
Published App on one server, gateway running on another server.
Unable to refresh applications, icons missing in RDWeb
Other servers able to publish applications
Gateway server is correctly added to web applications on the Published App server
Event log showing Event 5605 errors:
"The root\cimv2\TerminalServices namespace is marked with the RequiresEncryption flag. Access to this namespace might be denied if the script or application does not have the appropriate authentication level. Change the authentication level to Pkt_Privacy and run the script or application again."
Unable to restart application server due to user activity
Add the Gateway server account to the Local Administrators Group on the Application server.
A temporary fix but gets the apps published again.
Review WMI errors after reboot