29 06, 2012

Microsoft TMG SQL to Text Script

By | 2012-06-29T14:44:59+00:00 June 29th, 2012|How To, Microsoft Threat Management Gateway, Third Party, Uncategorized|0 Comments

Microsoft Forefront TMG logs activity to it’s internal SQL Express database. In addition to theextra steps you need to perform to access this database from a remote server, importing data into Vantage is much slower than importing from W3C Text logs. You can easily change the logging from SQL Express to W3C text logs in TMG’s [...]

29 06, 2012

Microsoft TMG SQL to Text Script

By | 2012-06-29T14:44:38+00:00 June 29th, 2012|How To, Microsoft Threat Management Gateway, Third Party, Tips and Best Practices, Uncategorized, Vantage, Web Browsing Analysis|0 Comments

Microsoft Forefront TMG logs activity to it's internal SQL Express database. In addition to the extra steps you need to perform to access this database from a remote server, importing data into Vantage is much slower than importing from W3C Text logs. You can easily change the logging from SQL Express to W3C text logs [...]

11 06, 2010

Accessing Microsoft Forefront TMG's Log Files (SQL Express)

By | 2010-06-11T06:54:59+00:00 June 11th, 2010|Firewall Analysis, How To, Loaders, Log File Analysis, Microsoft Threat Management Gateway, Uncategorized, Vantage, Web Browsing Analysis, WebSpy|1 Comment

If you need to analyze and report on Microsoft Forefront Threat Management Gateway log files, the most common stumbling block is enabling access to the default SQL Express databases that contains the firewall and web proxy log files. The log databases are stored in an SQL Express instance named MSFW. By default these databases cannot [...]

2 03, 2010

Vantage Update 2.2.0.27 – Fix for Microsoft FTMG SQL Import

By | 2010-03-02T15:58:13+00:00 March 2nd, 2010|Loaders, Log File Analysis, Microsoft ISA Server, Microsoft Threat Management Gateway, Software Updates, Uncategorized, Vantage, Web Module, WebSpy|0 Comments

Our support for Microsoft Forefront Threat Management Gateway is quite new and we’ve just fixed a couple of issues that we haven’t yet released as a public update yet. In particular, this update fixes the "specified cast invalid error" that occurs when importing the Web Proxy database logs.