We operate a large SAV client base (>8000 machines) through a tiered Primary / Secondary server structure. One of our strategies for picking up disassociated clients is to periodically copy the GCR.DAT file from the local secondary server onto each of its clients.
With the adoption of v10.1.5.5001 on the secondary servers, this is resulting in a full scan on the client each time the GRC.DAT file is received. This did NOT occur on any previous version of SAV on the secondary servers. The behaviour is also INDEPENDENT of the verson of SAV running on the clients (ie. it affects v8, v9 and v10 clients)!
I have concluded, therefore, that this must be due to a setting within GRC.DAT itself. Has anyone any idea what this setting might be and how best to disable it? Remember that this did not occur on our previous secondary server platform of v10.0.4.4000.
With the adoption of v10.1.5.5001 on the secondary servers, this is resulting in a full scan on the client each time the GRC.DAT file is received. This did NOT occur on any previous version of SAV on the secondary servers. The behaviour is also INDEPENDENT of the verson of SAV running on the clients (ie. it affects v8, v9 and v10 clients)!
I have concluded, therefore, that this must be due to a setting within GRC.DAT itself. Has anyone any idea what this setting might be and how best to disable it? Remember that this did not occur on our previous secondary server platform of v10.0.4.4000.