I ran the above update with the /F option so that it would force a downgrade. But now when I try to update the DAT from either the VSE console or update my workstation from my ePO console, it doesn't update. It still has the old 9172 DAT. I'm concerned about this because it appears that these newer DAT files with the newly signed certs are going to break DAT updates in my environment....this is BAD. I have around 12K endpoints and breaking DAT updates would definitely be BAD.
Am I missing a step here to get the DAT updated on my device after forcing a downgrade? Please advise. Thanks!
FYI - I'm running VSE 8.8 P12 + Hotfix and ePO 5.10 CU3
@sgrechtman If you force a DAT downgrade/perform a rollback, then your endpoint will not be able to again update to the version of the DAT that you rolled back from. It will instead wait until the next day's DAT release to accept the upgrade. This is a fail-safe mechanism in place to prevent re-application of the "bad DAT" that necessitated the rollback. (The software assumes you rolled back to avoid an issue with the DAT it had upgraded to, and will prevent re-application so it doesn't automatically reinstate what was rolled back).
Does this make sense?
Was my reply helpful?
If this information was helpful in any way, or answered your question, will you please select "Accept as Solution" in my reply, or give kudos as appropriate, so together we can help other members?