000021701 - How to use ctagent_reconfig.exe and ctagent_configtest.exe programs on Microsoft Internet Information Server (IIS) 6.0

Document created by RSA Customer Support Employee on Jun 16, 2016Last modified by RSA Customer Support Employee on Apr 21, 2017
Version 2Show Document
  • View in full screen mode

Article Content

Article Number000021701
Applies ToRSA ClearTrust Agent 4.5 for Microsoft IIS
Microsoft Windows Server 2003
Microsoft Internet Information Server (IIS) 6.0
ctagent_reconfig.exe
ctagent_configtest.exe
IssueHow to use ctagent_reconfig.exe and ctagent_configtest.exe programs on Microsoft Internet Information Server (IIS) 6.0
Changes to the webagent.conf file came into effect without explicitly restarting the IIS 6.0 web server.
ResolutionRSA Security continues to provide and support the configtest and reconfig tool with RSA ClearTrust Agent 4.5 for Microsoft IIS. However, due to the completely different way that IIS 6.0 works, its utility is questionable. In IIS 6.0, the ClearTrust Agent runs as a task in the IIS "Worker Process". IIS manages Worker Processes itself, and starts and stops these tasks on its own. These process can be routinely started, stopped, and restarted on a scheduled or demand basis, and, in fact, IIS may start up multiple instances of the Agent depending on configuration and Web server load. In this manner the ClearTrust Agent will actually may actually be "restarted" at any time.

This new behavior has an operational effect that should be considered when making any changes to the webagent.conf file. In the ClearTrust Agent for IIS 5.0, changes to the webagent.conf file only came into effect when the Web server was restarted (hence, a place for the reconfig and configtest utilities). When deployed on IIS 6.0, it is possible (depending on how IIS 6.0 is configured) for any changes made to the webagent.conf file to come into effect at any time even before a specific request has been made to restart the Web server using either the services or IIS restart commands. This change to the way the IIS Web server works obviously necessitates that careful planning is made when implementing scheduled updates to the webagent.conf file settings.
WorkaroundMade changes to the webagent.conf file.
Legacy Article IDa24393

Attachments

    Outcomes