![]() ![]() If you recently applied changes to the configuration, verify that these changes are configured properly. Level: Error Event ID: 21177 Source: Microsoft Forefront TMG Web Proxy Description: The failed to reload its configuration. Level: Error Event ID: 14016 Source: Microsoft Forefront TMG Firewall Description: Forefront TMG failed to load the firewall policy configuration The Forefront TMG configuration agent is reverting the configuration back to the last known configuration. This could be due to a corrupt configuration. Level: Error Event ID: 21209 Source: Microsoft Forefront TMG Control Description: The Forefront TMG configuration agent was unable to upload the configuration to the forefornt TMG services. Under Monitoring | Alerts and in the Windows event logs (Application log), you may also see the following errors: In Monitoring | Configuration, you may also see an error about not having synchronized since 0. ![]() Another symptom you may notice is an empty Firewall policy screen. 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. When Forefront TMG has a corrupt configuration database, the backup and restore mechanism itself is broken and as such you need to fix this first before you can recover from backup. There is however a scenario where these backups cannot be restored to bail you out. We all know it is good practice to keep regular Forefront TMG configuration backups as they help you recover your deployment quickly and accurately in case of a failure or miss configuration.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |