- play_arrow What's New in WinCollect
- play_arrow WinCollect Overview
- play_arrow Installation Prerequisites for WinCollect
- play_arrow WinCollect installations
- WinCollect installations
- Installing and Upgrading the WinCollect Application on JSA Appliances
- Creating an Authentication Token for WinCollect Agents
- Adding Multiple Destinations to WinCollect Agents
- Migrating WinCollect Agents After a JSA Hardware Upgrade
- Stand-alone WinCollect Installations
- WinCollect Configuration Console Overview
- Installing the Configuration Console
- Silently Installing, Upgrading, and Uninstalling WinCollect Software
- Setting an XPath Parameter During Automated Installation
- Migrating from Adaptive Log Exporter to WinCollect
- Installing the WinCollect Agent on a Windows Host
- Installing a WinCollect Agent from the Command Prompt
- Uninstalling a WinCollect Agent from the Command Prompt
- Uninstalling a WinCollect Agent from the Control Panel
- play_arrow Configuring WinCollect Agents After Installation
- Configuring WinCollect Agents After Installation
- Manually Adding a WinCollect Agent
- Deleting a WinCollect Agent
- WinCollect Destinations
- Adding Custom Entries to WinCollect Status Messages
- Forwarding Events Identifier
- Configuring Stand-alone WinCollect Agents with the Configuration Console
- Creating a WinCollect Credential
- Adding a Destination to the WinCollect Configuration Console
- Configuring a Destination with TLS in the WinCollect Configuration Console
- Adding a Device to the WinCollect Configuration Console
- Sending Encrypted Events to JSA
- Increasing UDP Payload Size
- Include Milliseconds in Event Log Timestamp
- Collecting Local Windows Logs
- Collecting Remote Windows Logs
- Changing configuration with Templates in a Stand-alone Deployment
- Configuration Options for Systems with Restricted Policies for Domain Controller Credentials
- play_arrow Troubleshooting WinCollect Deployment Issues
- Troubleshooting WinCollect Deployment Issues
- Common Problems
- Replacing the Default Certificate in JSA Generates Invalid PEM Errors
- The Statistics Subsystem
- Event ID 1003 Splits the Message in JSA
- WinCollect Files are Not Restored During a Configuration Restore
- Windows 10 (1803) Cannot Read the Security Bookmark File
- Resolving Log Source Error After WinCollect Update
- WinCollect Log File
Microsoft Exchange Server Log Source Configuration Options
Use this reference information to configure the WinCollect plug-in for Microsoft Exchange Server.
Supported versions
WinCollect supports the following versions of Microsoft Exchange :
Microsoft Exchange 2003
Microsoft Exchange 2007
Microsoft Exchange 2010
Microsoft Exchange 2013
Microsoft Exchange 2016
Microsoft Exchange 2019
Parameter | Description |
|---|---|
Log Source Type | Microsoft Exchange Server |
Protocol Configuration | WinCollect Microsoft Exchange |
Local System | The WinCollect agent must be installed on the Microsoft Exchange Server. The log source uses local system credentials to collect and forward events to the JSA. |
Ensure that the firewalls that are located between the Exchange Server and the remote host allow traffic on the following ports:
TCP port 135 for Microsoft Endpoint Mapper.
UDP port 137 for NetBIOS name service.
UDP port 138 for NetBIOS datagram service.
TCP port 139 for NetBIOS session service.
TCP port 445 for Microsoft Directory Services to transfer files across a Windows share.
For more information about Microsoft Exchange log source configuration, see the Configuring DSMs Guide.
The Exchange Server OWA event logs that are monitored by WinCollect are defined by the directory path that you specify in your WinCollect Exchange Server log source. Microsoft Exchange writes to two directories: W3SVC1 and W3SVC2. The Microsoft Exchange plug-in monitors all recursive files under the C:\inetpub\logs\LogFiles\ directory.
Collection type | Root log directory |
|---|---|
Local | C:\inetpub\logs\LogFiles\W3SVC1 |
Remote | \\<Exchange_Server_IP address>\c$\inetpub\logs\LogFiles\W3SVC1 |
The Exchange Server Message Tracking event logs that are monitored by WinCollect are defined by the directory path that you specify in your WinCollect Exchange Server log source.
Collection type | Root log directory |
|---|---|
Local | C:\Program Files\Microsoft\Exchange Server\V15\TransportRoles\Logs\MessageTracking |
Remote | \\<Exchange_Server_IP address>\C$ \Program Files\Microsoft\Exchange Server\V15\TransportRoles\Logs\MessageTracking |
Collection type | Root log directory |
|---|---|
Local | C:\Program Files\Microsoft\Exchange Server\V15\TransportRoles\Logs\Hub\ProtocolLog |
Remote | \\<Exchange_Server_IP address>\C$ \Program Files\Microsoft\Exchange Server\V15\TransportRoles\Logs\Hub \ProtocolLog |
