- play_arrow WinCollect 10 Overview
- play_arrow Installing WinCollect 10
- play_arrow Installing WinCollect 10
- Hardware and software requirements for the WinCollect 10 host
- Upgrading WinCollect 10 agents
- Installing WinCollect 10 using the GUI Quick installation
- Installing WinCollect 10 using the command line
- Installing WinCollect 10 using the Advanced installer
- WinCollect 10 Command line installation advanced examples
- WinCollect 10 installation script examples
- play_arrow Uninstalling WinCollect 10
- play_arrow WinCollect 10 Stand-alone Console
- play_arrow WinCollect 10 stand-alone console
- play_arrow WinCollect 10 stand-alone configuration
- play_arrow Agent settings
- Service status
- Log Viewer
- Top Sources
- Applying pending changes
- play_arrow Create a source in the Source wizard
- play_arrow WinCollect Sources
- play_arrow WinCollect Sources
- play_arrow Advanced Settings
- play_arrow Advanced settings
- Agent advanced settings
- play_arrow Source advanced settings
- Microsoft Windows events advanced settings
- EVTX Forwarder advanced settings
- Common file-based plugin advanced settings
- File Forwarder advanced settings
- Microsoft DHCP Server advanced settings
- Microsoft DNS Debug advanced settings
- Microsoft Exchange Server advanced settings
- Microsoft Forefront TMG advanced settings
- Microsoft IIS advanced settings
- Microsoft NPS advanced settings
- Microsoft SQL Server advanced settings
- System advanced settings
- play_arrow The WinCollect 10 Statistics File
- play_arrow WinCollect Terminology
ON THIS PAGE
Agent configuration update script use cases
You can change the agent configuration without making manual or scripted edits to the AgentConfig.xml file by using update scripts.
When you copy an update script to the WinCollect patch directory, the Agent performs the actions that are described in your script.
Update script actions
Update scripts can include the following actions:
<?xml version="1.0" encoding="UTF-8" standalone="yes"?> <WinCollectScript version="10.0"> </WinCollectScript>
<?xml version="1.0" encoding="UTF-8" standalone="yes"?> <WinCollectScript version="10.0"> </WinCollectScript>
<?xml version="1.0" encoding="UTF-8" standalone="yes"?> <WinCollectScript version="10.0"> </WinCollectScript>
The agent creates a new configuration in the patch folder and validates the new configuration. When the validation is successful, the old agent configuration is backed up. The agent moves the update script, the old AgentConfig.xml file, and the new AgentConfig.xml file into a backup folder (patch_xxxx) and puts the new agent configuration into operation.
Several sample update scripts are installed with WinCollect 10. They are stored in the \IBM\WinCollect\samples directory.
Examples
These scripts are examples only. All agent configuration service modules are supported so that you can create your own scripts.
Update script file names must begin with update_. All other file names are ignored.
<?xml version="1.0" encoding="UTF-8" standalone="yes"?> <WinCollectScript version="10.0"> <AddTo objPath="LocalSources(Name=Local)" > <Source Name="Security XPath" > <Parameter name="Query"> <QueryList> <Query Id="1" Path="Security"> <Select Path="Security">*[System[(Level=1 or Level=2 or Level=3) and (EventID=1 or EventID=3 or (EventID >= 5 and EventID <= 100) or (EventID >= 200 and EventID <= 500) )]]</Select> </Query> </QueryList> </Parameter> </Source> </AddTo> </WinCollectScript>
<?xml version="1.0" encoding="UTF-8" standalone="yes"?> <WinCollectScript version="10.0"> <Delete objPath="LocalSources(Name=Local)/Source(Name=Security)" /> </WinCollectScript>
<?xml version="1.0" encoding="utf-8" standalone="yes"?> <WinCollectScript version="10.0"> <Update objPath="SystemSettings" setParam="Console.Port" value="3333" descr="Changing the Config Console's port to 3333" /> </WinCollectScript>
The following use cases are examples of how you can use update scripts to change agent configurations: