BrianTX, the checking of the product version is easy. So is the checking of the engine and DAT versions. But we deploy the updates via SMS to 20% of the client computers per day. That means that at every logon, any one computer could have a couple different versions of DAT files which would be valid in our business model.
Most of the code that I posted was to limit WAN traffic, to limit impact on the script performance, and to limit any false reports of non-compliant computers. You see I track the count of logon script executions where the client is non-compliant and only report (write file across global wan) every 25 logons. The first report is after the fifth logon. This eliminates false reports where computers were just built. Then it does not report again until 20 more logons occur. This gives the local support teams time to take action. If the coomputer is not correct by then, it is again logged.
[ 01 May 2002, 18:36: Message edited by: Howard Bullock ]
