Lindows
asked on
Event collector in 2008
I'm trying to get the event collector to work on 2008 so that the source computers 2008/2003/Xp/Windows 7 can forward logs to it.
I've created a GPO with the following settings and linked it to the OU that contains the source computers.
Windows Components/Event Forwardings:
Configure the server address, refresh interval, and issuer certificate authority of a target Subscription Manager = Enabled
SubscriptionManagers = server=Entered the fqdn of the collector server
Windows Components/Windows Remote Management (WinRM)/WinRM Service
Allow automatic configuration of listeners = Enabled
IPv4 filter: *
IPv6 filter: *
And on the collector server, didn't apply the above GPO but configured the following:
1. winrm qc -q
2. wecutil qc /q and configured the settings with the source initiated option.
Subscription:
Subscription Name: Event test
Destination Log > Forwarded Events.
Source Computer Initiated > Select Computer Groups > Add Domain Computers > added the group “SourceComputers” that contains the source computers.
Events to Collect :
Logged: Any time
Event level > Critical, Error, and Warning.
By log> Event logs > Application,Security,Syste
Rest, left at the default.
Advanced Subscription Settings > Normal > HTTP
However, I'm not seeing any forwarded events on the collector server although the subscription says it's active.
Is running "winrm qc -q" necessary on all the source computers as well?
Doesn't the GPO Windows Components/Windows Remote Management (WinRM)/WinRM Services do this?
And for 2003 and XP clients:
Install WS-Management v1.1 and use winrm quickconfig on the source 2003/XP computers? The GPO wouldn’t work on 2003/XP right?
I've created a GPO with the following settings and linked it to the OU that contains the source computers.
Windows Components/Event Forwardings:
Configure the server address, refresh interval, and issuer certificate authority of a target Subscription Manager = Enabled
SubscriptionManagers = server=Entered the fqdn of the collector server
Windows Components/Windows Remote Management (WinRM)/WinRM Service
Allow automatic configuration of listeners = Enabled
IPv4 filter: *
IPv6 filter: *
And on the collector server, didn't apply the above GPO but configured the following:
1. winrm qc -q
2. wecutil qc /q and configured the settings with the source initiated option.
Subscription:
Subscription Name: Event test
Destination Log > Forwarded Events.
Source Computer Initiated > Select Computer Groups > Add Domain Computers > added the group “SourceComputers” that contains the source computers.
Events to Collect :
Logged: Any time
Event level > Critical, Error, and Warning.
By log> Event logs > Application,Security,Syste
Rest, left at the default.
Advanced Subscription Settings > Normal > HTTP
However, I'm not seeing any forwarded events on the collector server although the subscription says it's active.
Is running "winrm qc -q" necessary on all the source computers as well?
Doesn't the GPO Windows Components/Windows Remote Management (WinRM)/WinRM Services do this?
And for 2003 and XP clients:
Install WS-Management v1.1 and use winrm quickconfig on the source 2003/XP computers? The GPO wouldn’t work on 2003/XP right?
Matthias Abt
Do you add the Computer Account from the Collector to the "event sender" in local administration Group?
Ups, sorry, must be the Group EventlogReader on server 2008.
ASKER
Hello abt-it,
Yes, I've added the collector server computer object to the local administrators group and also to the eventlogreaders group on the source computer.
The setup is a source initated method where the clients forward the logs to the collector.
I checked the ports and on the collector, it looks like it's using port 80 and is open and on the source, port 5985 is open.
So far, zero logs have been forwarded.
Yes, I've added the collector server computer object to the local administrators group and also to the eventlogreaders group on the source computer.
The setup is a source initated method where the clients forward the logs to the collector.
I checked the ports and on the collector, it looks like it's using port 80 and is open and on the source, port 5985 is open.
So far, zero logs have been forwarded.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.