Integrity client Author = masteradmin ???

[diago]

Does anyone know how to remove or hide the author field in the Integrity client. By default it shows up as masteradmin and displays this to clients, which is absolutely insane. A collegue suggested creating an account, create and deploy the policy, then delete the account you used. Does any one else have any suggestions?

[CSING]

Deploy the Integrity agent package with system Tray icon unchecked. Then you will be super stealthy.

[unclerichard]

<grin>.... That is just too cruel. If this is disabled though, is there a registry key or environment variable that stores the currently active policy? We have had a few instances where, despite the last connect date/time being updated on the server, the disconnected policy was still active !!

Speaking of which, I am looking forward to the beaconing system that is mooted for version 7.

Unc

[CSING]

The policy is not saved in the registry or an environment variable. The downloaded policy is stored in the Internet logs directory and then saved in the appropriately named rdb datastore. So the best way to determine the policy would be the server reports.

Regarding the issue you mentioned: I understand that you mean that the Reports indicate a different active policy than the endpoint. Specifically Reports indicate a corperate policy and the endpoint in reality is Disconnected. It is good to remember that Reporting data is not Real-time. Data for Reporting about endpoints is not sent with syncs or heartbeats. It is sent by loguploads. Depending on your logupload setting your Report data will be skewed. Also when a endpoint is disconnected from the Server data cannot be uploaded to the server.

[unclerichard]

We had another of these today but the common factor has been the client version of 6.5.063.166. Despite the client being visible in the endpoints monitor on the server and with the date incrementing, the client and the server were in agreement that the disconnected policy was active. Fortunately, our d/c policy allowed a client upgrade to v199. With the new 'reset' feature, we should be able to brief our field support to do this. (nice one CP).

Unc