Moved from Community Help to ePO for better handling.
check which version of VSE you have selected to show in the DAT column.
As the DAT wont be visible in the ePO if the VSE installed in client machine is different from the version selected in the ePO.
Also check the product status in the ePO for particular machines to see the DAT version which they are having.
u r right but if it is column selection issue then it should come under complaint systems but it is showing non-complaint.
You see the blank column in Non complaint systems also ?
Run VSE: Current DAT Adoption query and see why the systems are non complaint.
If the machines are not updating we see the DAT version as 1111 which will be installed during the first time of installation.
Yes it is showing blank in non-complaint systems.
ok then guide me how run current DAT Adoption query.
check whether you have VSE installed in the first place.
To run the query goto Menu| Reporting | Queries & Reporting | McAfee Groups | VirusScan Enterprise > VSE: Current DAT Adoption
We have this issue as well.
Running ePO 5.3, VSE 8.8
The ePO via whatever query you choose to run is showing a large number of blank DAT version and blank engine version like the example above.
We went to an endpoint and brought up the about VirusScan Enterprise, which shows engine and version up to date.
This is an issue because without manually logging on to over 500 desktops we don't know whether we are protected and the DAT version is up to date.
How many other people have logged a case with support about this, and is there a resolution?
Systems that have DATs that show 1111 most often failed to install VSE properly.
We have to manually run the SetupVSE.exe on these reported machines to correct the failed installs at my company.
We have 3 of those (instances reporting 1111).
An interesting point, we've also found that during DLP policy updates when we force endpoint wakeups, the number of reported blank DAT version rises sharply 300-400