We are currently experiencing an issue where if the switch.aud file in the centenn.ial directory of the client is replaced, and then the CentennialClientAgent service is stopped, the file reverts back to its previous state.
Resolving the problem
Our technical solution uses the scope.exe tool to create a switch.aud file which is then distributed to various servers.
Copy the new switch.aud to the centenn.ial/audit folder
Stop service CentennialClientAgent
Checked the switch.aud and it was exactly the same as the old file (basically the new contents had disappeared)
" The switch.aud file is designed to be a file to preserve settings whilst the Client is not running. The last thing the Client does when it stops is to write the file with the contents of memory. Therefore, the sequence in which they are doing this needs to be changed for it to work:
1) stop the Client Agent service
2) copy the new switch.aud to c:\centenn.ial\audit
3) restart the Client Agent
In this case, the new switch.aud will not be overwritten. Obviously, they will need to be sure that the client Agent service has shut down completely before copying in the file.
Note: there are a few additional points that need to be raised as the Client Agent was not designed to run with 'manual intervention' in this way
the switch.aud file must be well-formed XML. If it is not, it may cause unpredictable behavior
the switch.aud permissions should not be altered
if community strings are changed in the client.xml on the installation, the Clients will delete their switch.aud files in order to rediscover switches with the new community strings.
the clients will still need a network route to the switches listed in the switch.aud file, the correct SNMP community strings and no other restrictions on their access to read the switch SNMP data.
the clients will interrogate the switches only when they receive a request to perform a location audit."