This documentation supports the 20.08 version of BMC Discovery.

To view an earlier version of the product, select the version from the Product version menu.


The tw_terminate_winproxy utility enables you to send a request to the Windows proxy to terminate operation. To use the utility, type the following command at the $TIDEWAY/bin/ directory:

tw_terminate_winproxy [options] 

where options are any of the options described in the following table and the common command line options described in Using command line utilities.


You must have the discovery/kslave/write permission to use the utility.

Command Line Option


--proxy-name proxyname

(Required) Specifies the name of the Active Directory, Workgroup or Credential Windows proxy that you are logging into

--username username

(Required) Specifies the name of the BMC Discovery user. If no name is specified, BMC Discovery uses the default, system.


User example

In the following example, you must have the discovery/kslave/write permission to use the utility.

Stopping a running credential Windows proxy

$TIDEWAY/bin/tw_terminate_winproxy --proxy-name my_proxy

When the utility successfully sends a terminate request to a Windows proxy, an audit event is logged. The audit event, named windows_proxy_process_terminate, contains the name of the Windows proxy that the terminate request is sent to.


If a Windows proxy is not running as either the Local System account or as a member of the Administrators group, tw_terminate_winproxy will fail to stop the Windows proxy. The following error is logged in the Windows proxy log file:
ERROR: Failed to terminate slave service: [(5, 'OpenSCManager', 'Access is denied.')]

To work around this issue, allow the user that the Windows proxy is running to stop the Windows proxy service. This is documented on the Microsoft Support Site.

For more information about Windows proxy configuration, see Additional Windows proxy configuration.

Was this page helpful? Yes No Submitting... Thank you