Workaround to configure blacklists for proxies

In some cases, a proxy change has to be made and stay in place in one specific proxy; for example, for the collection of input-output KVGs.

If the configuration made on the primary should not be propagated to all proxies (an updinst.cfg for a file blacklist will keep it from propagating to app nodes), automate the replacement of the files in a psupdate-post plugin, so it remains there for the rest of the day and the next listing. It happens only on your test proxy:

Add in the instance's script\psupdate_post.cmd , for example, if the primary has agent\pstee.exe in place:

%echo off
for /f %%i in ('hostname') do if "%%i" neq "result-of-the-hostname-command" goto exit
ren ..\agent\agtesxi.exe ..\agent\agtesxi-orig.exe
ren ..\agent\pstee.exe ..\agent\agtesxi.exe
:exit

Be sure to change result-of-the-hostname-command to the proxy's hostname.

Always check such scripts first by running it as administrator and testing it does what is expected of it, in a test environment first.