
Make sure "Authenticated Users" is selected in the list, then enable the "Remote Enable" checkbox and click OK, then OK again.
Expand "Root," then select "CIMV2" and click the "Security" button. Right-click "WMI Control (Local)" and choose "Properties". Open the WMI Control MMC snap-in (Start > Run > wmimgmt.msc). Make sure "Authenticated Users" is selected in the list, then enable the "Remote Activation" checkbox and click OK, then OK again. Click the "Add" button, type in "Authenticated Users" and click OK. On the COM Security tab, click the "Edit Limits" button in the "Launch and Activation Permissions" section. Expand "Component Services" > "Computers," then right-click "My Computer" and choose "Properties". Open the Component Services MMC snap-in (Start > Run > dcomcnfg). Add the user account that you're connecting with to the "Administrators" and "Event Log Viewers" security groups. Make sure you've already verified the settings in "General Requirements for Remote Event Logs" section above. If you're connecting to a remote Windows 8 machine to view the Windows Event Logs or Event Channels, you'll need to perform some additional configuration steps on the remote Windows 8 machine. Note: If you're connecting to a Windows 8 machine, you'll need to do some additional configuration on the Windows 8 machine. More information on this restriction can be found in the "Handling Remote Connections Under UAC" section of the following MSDN article: (v=vs.85).aspx For remote servers that are on a domain and have UAC enabled, make sure the credentials you specify in LogFusion are for a domain user that is a member of the local Administrators group on the remote server. If the remote server is not on a domain, and UAC is enabled on the remote server, the WMI call will fail. Note: LogFusion uses WMI to connect to the remote server. Make sure you're specifying the credentials of an account that have permissions to open the Event Logs on the remote server. Make sure the Remote Registry service is started on the remote server.
Make sure Remote Management is allowed through the Windows Firewall on the remote server.If LogFusion fails to connect to a remote server's event logs, make sure to check the following: General Requirements for Remote Event Logs