<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: 8 Reasons NOT to Use Microsoft Forefront TMG&#8217;s Reporting</title>
	<atom:link href="http://www.webspy.com.au/blogs/index.php/8-reasons-not-to-use-microsoft-forefront-tmgs-reporting/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.webspy.com.au/blogs/index.php/8-reasons-not-to-use-microsoft-forefront-tmgs-reporting/</link>
	<description>For when WebSpyrians have something to say.</description>
	<lastBuildDate>Sat, 03 Dec 2011 07:24:09 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Scott</title>
		<link>http://www.webspy.com.au/blogs/index.php/8-reasons-not-to-use-microsoft-forefront-tmgs-reporting/comment-page-1/#comment-106</link>
		<dc:creator>Scott</dc:creator>
		<pubDate>Wed, 27 Oct 2010 02:47:02 +0000</pubDate>
		<guid isPermaLink="false">http://www.webspy.com.au/blogs/?p=1181#comment-106</guid>
		<description>Hi Jon. Thanks for your comment! 

The changes in SP1 is definitely something I&#039;ve been meaning to write about. I haven&#039;t had a chance to play with the user activity reporting included in SP1, but from what I understand, you need to enter the user you want to report on in the form of domain\username. The advantages of our software that I mention above still apply here, as you can simply get overviews on your &#039;top n&#039; users, without the need of entering their logged usernames. You can also run individual user reports in our software simply select the users you want to report on (displayed as FirstName LastName) rather than typing the full logged username including the &#039;domain\&#039; prefix.

This topic deserves its own blog article with a more in depth look at the features in SP1. I&#039;ll hopefully get to this very soon. Thanks for reminder!</description>
		<content:encoded><![CDATA[<p>Hi Jon. Thanks for your comment! </p>
<p>The changes in SP1 is definitely something I&#8217;ve been meaning to write about. I haven&#8217;t had a chance to play with the user activity reporting included in SP1, but from what I understand, you need to enter the user you want to report on in the form of domain\username. The advantages of our software that I mention above still apply here, as you can simply get overviews on your &#8216;top n&#8217; users, without the need of entering their logged usernames. You can also run individual user reports in our software simply select the users you want to report on (displayed as FirstName LastName) rather than typing the full logged username including the &#8216;domain\&#8217; prefix.</p>
<p>This topic deserves its own blog article with a more in depth look at the features in SP1. I&#8217;ll hopefully get to this very soon. Thanks for reminder!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jon Ruiz</title>
		<link>http://www.webspy.com.au/blogs/index.php/8-reasons-not-to-use-microsoft-forefront-tmgs-reporting/comment-page-1/#comment-105</link>
		<dc:creator>Jon Ruiz</dc:creator>
		<pubDate>Tue, 26 Oct 2010 09:32:57 +0000</pubDate>
		<guid isPermaLink="false">http://www.webspy.com.au/blogs/?p=1181#comment-105</guid>
		<description>Please update your blog to reflect the updates in Service Pack 1 and the Post SP1 updates.

http://blogs.technet.com/b/forefront/archive/2010/06/07/available-now-forefront-threat-management-gateway-2010-service-pack-1.aspx</description>
		<content:encoded><![CDATA[<p>Please update your blog to reflect the updates in Service Pack 1 and the Post SP1 updates.</p>
<p><a href="http://blogs.technet.com/b/forefront/archive/2010/06/07/available-now-forefront-threat-management-gateway-2010-service-pack-1.aspx" rel="nofollow">http://blogs.technet.com/b/forefront/archive/2010/06/07/available-now-forefront-threat-management-gateway-2010-service-pack-1.aspx</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Scott</title>
		<link>http://www.webspy.com.au/blogs/index.php/8-reasons-not-to-use-microsoft-forefront-tmgs-reporting/comment-page-1/#comment-80</link>
		<dc:creator>Scott</dc:creator>
		<pubDate>Thu, 10 Jun 2010 03:31:46 +0000</pubDate>
		<guid isPermaLink="false">http://www.webspy.com.au/blogs/?p=1181#comment-80</guid>
		<description>Hi Haseeb,

We recommend using WebSpy Vantage to report on your Micorosft TMG log files. For more details on how to do this, see:
&lt;a href=&quot;http://www.webspy.com/vendors/microsoft-ftmg/howto.aspx&quot; rel=&quot;nofollow&quot;&gt;http://www.webspy.com/vendors/microsoft-ftmg/howto.aspx&lt;/a&gt;

Cheers!
Scott.</description>
		<content:encoded><![CDATA[<p>Hi Haseeb,</p>
<p>We recommend using WebSpy Vantage to report on your Micorosft TMG log files. For more details on how to do this, see:<br />
<a href="http://www.webspy.com/vendors/microsoft-ftmg/howto.aspx" rel="nofollow">http://www.webspy.com/vendors/microsoft-ftmg/howto.aspx</a></p>
<p>Cheers!<br />
Scott.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Haseeb</title>
		<link>http://www.webspy.com.au/blogs/index.php/8-reasons-not-to-use-microsoft-forefront-tmgs-reporting/comment-page-1/#comment-79</link>
		<dc:creator>Haseeb</dc:creator>
		<pubDate>Wed, 09 Jun 2010 18:50:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.webspy.com.au/blogs/?p=1181#comment-79</guid>
		<description>Then what should be the alternative software???</description>
		<content:encoded><![CDATA[<p>Then what should be the alternative software???</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Scott</title>
		<link>http://www.webspy.com.au/blogs/index.php/8-reasons-not-to-use-microsoft-forefront-tmgs-reporting/comment-page-1/#comment-73</link>
		<dc:creator>Scott</dc:creator>
		<pubDate>Wed, 19 May 2010 05:58:19 +0000</pubDate>
		<guid isPermaLink="false">http://www.webspy.com.au/blogs/?p=1181#comment-73</guid>
		<description>Hi Bandhar,

Thanks for your comment, and I apologise it has taken me so long to respond. Yes, you’re absolutely correct in that TMG logs to SQL Server 2008, and like any database, this can be queried for relevant information as long as you have the tools and expertise (and time!) required to do so. You noted that you opened a support ticket with Microsoft and they pulled the required information for you which is a great testament to Microsoft’s support services. 

Unfortunately, this method of obtaining reports is unacceptable for many of our customers as they may not have a similar support agreement and/or do not want to rely on Microsoft each time they need a report.

There is also much more that goes into our reporting solutions beyond the first step of simply querying the SQL databases.

Our customers want to have access to regular usage reports on a daily, weekly or monthly basis. They also want to distribute those reports automatically to the correct people such as department managers or network administrators. Those reports should only contain information relevant to the person receiving the report. For example, department managers receive reports containing the people in their department, or network administrators receive a traffic report for the subnets they are responsible for. 

Our software also pulls information from Active Directory (or any LDAP server) to learn about the structure of your organization and the people within it. This information is used to improve the information in reports (for example, instead of displaying WEBSPY01\scottg, the report would simple say Scott Glew, or perhaps Development Department), and filter and distribute reports appropriately. 

All this is wrapped in a nice user interface to make it easy for administrators to customize and configure the complete reporting process.

Combine all this with the ability to report on any device (not just Microsoft TMG), masking usernames from certain reports to protect privacy, customizable keyword based categorization of URLs, IP DNS resolution, subnet grouping, file type grouping based on extensions, and... well you get the idea.

Cheers!
Scott</description>
		<content:encoded><![CDATA[<p>Hi Bandhar,</p>
<p>Thanks for your comment, and I apologise it has taken me so long to respond. Yes, you’re absolutely correct in that TMG logs to SQL Server 2008, and like any database, this can be queried for relevant information as long as you have the tools and expertise (and time!) required to do so. You noted that you opened a support ticket with Microsoft and they pulled the required information for you which is a great testament to Microsoft’s support services. </p>
<p>Unfortunately, this method of obtaining reports is unacceptable for many of our customers as they may not have a similar support agreement and/or do not want to rely on Microsoft each time they need a report.</p>
<p>There is also much more that goes into our reporting solutions beyond the first step of simply querying the SQL databases.</p>
<p>Our customers want to have access to regular usage reports on a daily, weekly or monthly basis. They also want to distribute those reports automatically to the correct people such as department managers or network administrators. Those reports should only contain information relevant to the person receiving the report. For example, department managers receive reports containing the people in their department, or network administrators receive a traffic report for the subnets they are responsible for. </p>
<p>Our software also pulls information from Active Directory (or any LDAP server) to learn about the structure of your organization and the people within it. This information is used to improve the information in reports (for example, instead of displaying WEBSPY01\scottg, the report would simple say Scott Glew, or perhaps Development Department), and filter and distribute reports appropriately. </p>
<p>All this is wrapped in a nice user interface to make it easy for administrators to customize and configure the complete reporting process.</p>
<p>Combine all this with the ability to report on any device (not just Microsoft TMG), masking usernames from certain reports to protect privacy, customizable keyword based categorization of URLs, IP DNS resolution, subnet grouping, file type grouping based on extensions, and&#8230; well you get the idea.</p>
<p>Cheers!<br />
Scott</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bandhar</title>
		<link>http://www.webspy.com.au/blogs/index.php/8-reasons-not-to-use-microsoft-forefront-tmgs-reporting/comment-page-1/#comment-70</link>
		<dc:creator>Bandhar</dc:creator>
		<pubDate>Mon, 12 Apr 2010 11:34:19 +0000</pubDate>
		<guid isPermaLink="false">http://www.webspy.com.au/blogs/?p=1181#comment-70</guid>
		<description>Scott, I think you are completely wrong what you have written above. I purchased TMG sometime back and was a bit worried after seeing your blogpost. I opened a Ticket with MS and they were able to pull all the information from SQL whatever i asked them.

In TMG they are using SQL Server 2008 and we need to create custom queries to pull information from SQL database. Its customizable and very informative.

It will be great if you will add this to your blog :).

Thanks,
Bandhar</description>
		<content:encoded><![CDATA[<p>Scott, I think you are completely wrong what you have written above. I purchased TMG sometime back and was a bit worried after seeing your blogpost. I opened a Ticket with MS and they were able to pull all the information from SQL whatever i asked them.</p>
<p>In TMG they are using SQL Server 2008 and we need to create custom queries to pull information from SQL database. Its customizable and very informative.</p>
<p>It will be great if you will add this to your blog <img src='http://www.webspy.com.au/blogs/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> .</p>
<p>Thanks,<br />
Bandhar</p>
]]></content:encoded>
	</item>
</channel>
</rss>

