When Forefront TMG has a corrupt configuration database, and as such you need to fix this first before you can recover from backup.
In the cases of corrupt configuration that I have seen, Forefront TMG generally keeps working as per normal, but you do not have any ability to change anything.
Forefront TMG stores it configuration in an Active Directory Lightweight Directory Services (AD-LDS) database.
It is possible to restart the individual services, but a full reboot is recommended.
If you have the same symptoms, check the alert detail and see if the object is the same or a different one. If everything is working again, take the time to restore your last backup and overwrite the existing configuration.
The procedure that follows involves editing the registry and manually editing the AD-LDS database.
This should not be done unless all the actions are understood and the risk of further damage has been negated. It is also strongly advised that once the config is loading up, to restore from a last known good backup.
For more information on this, see my previous article – Forefront TMG Configuration Backup Scripts For Standalone and Enterprise Arrays Based in Cape Town, South Africa he is an IT Professional working in various environments building, testing and maintaining systems for a large national retail chain.
An IT professional since 1996 Etienne has worked in various environments and is certified by Comptia, Dell and Microsoft.This database is a file located on the TMG server and there are also registry references to the directory.From past experience it is usually a single entity that has become corrupt.In antivirus jargon, this is this is know as a the signature library (or signature file).If your signature file is not up to date, then it is possible that new viruses can slip through since the antivirus software is not aware of the new pests' existence.Delete the policy object in ADSI Edit (CN=Delete the GUID key entry from the registry using Regedit.