<?xml version="1.0" encoding="UTF-8"?><rss version="0.92">
<channel>
	<title>Overseer Network Monitor Weblog</title>
	<link>http://www.overseer-network-monitor.com/weblog</link>
	<description>A weblog by the author of Overseer Network Monitor</description>
	<lastBuildDate>Tue, 10 Apr 2012 17:04:56 +0000</lastBuildDate>
	<docs>http://backend.userland.com/rss092</docs>
	<language>en</language>
	<!-- generator="WordPress/3.3.1" -->

	<item>
		<title>Overseer 4.1.47 has been released</title>
		<description><![CDATA[Overseer 4.1.47 has now been released. This includes a few bug fixes for intermittent problems that a couple users have experienced. I also made a change in the database library that should increase the performance of the database&#8211; which may be most noticeable on slower machines. Lastly, I added a quick usability enhancement to not always auto-expand [...]]]></description>
		<link>http://www.overseer-network-monitor.com/weblog/2012/04/10/overseer-4-1-47-has-been-released/</link>
			</item>
	<item>
		<title>Overseer resource dependencies</title>
		<description><![CDATA[I&#8217;ve recently had a couple customers ask me about dependencies. This is a relatively new feature in Overseer, so some of our existing customers don&#8217;t even know exactly how to use them. They are rather hidden, but will become more visible in the next major version of Overseer. While hidden, resource dependencies can be very [...]]]></description>
		<link>http://www.overseer-network-monitor.com/weblog/2012/04/03/overseer-resource-dependencies/</link>
			</item>
	<item>
		<title>Overseer 4.1.46 has been released</title>
		<description><![CDATA[The newest version of Overseer Network Monitor, 4.1.46 has been released. This minor build simply fixes the license key issue in 4.1.42.]]></description>
		<link>http://www.overseer-network-monitor.com/weblog/2012/03/27/overseer-4-1-46-has-been-released/</link>
			</item>
	<item>
		<title>How to prevent &#8216;false&#8217; notifications</title>
		<description><![CDATA[Sometimes Overseer customers will Email me and tell me that Overseer notifies them that their server is down, yet they login and everything is fine. This is something that will occur from time to time&#8211; Overseer detects a failure, but this may be caused by a network hiccup(particularly over WAN connections), or occasionally an OS issue. The [...]]]></description>
		<link>http://www.overseer-network-monitor.com/weblog/2012/03/15/how-to-prevent-false-notifications/</link>
			</item>
	<item>
		<title>Known issue: Licensing information &#8216;lost&#8217;</title>
		<description><![CDATA[It has recently come to our attention that customers upgrading from previous versions of 4.1 to 4.1.41 or higher are experiencing issues with their licensing information(registered name and license key) &#8216;disappearing&#8217;. We have tracked this down to a change that has caused Overseer to look at a slightly different registry key(where this information is stored). [...]]]></description>
		<link>http://www.overseer-network-monitor.com/weblog/2012/01/06/known-issue-licensing-information-lost/</link>
			</item>
	<item>
		<title>Windows XP error: Logon failure: unknown user name or bad password</title>
		<description><![CDATA[Occasionally with Overseer, a Windows XP system is configured in such a way that accessing it with valid login credentials will throw the error &#8220;Logon failure: unknown user name or bad password&#8221;. This is particularly frustrating when you KNOW it&#8217;s the correct user and password, and sometimes it&#8217;s even a local account&#8211; which is particularly [...]]]></description>
		<link>http://www.overseer-network-monitor.com/weblog/2011/11/10/windows-xp-error-logon-failure-unknown-user-name-or-bad-password/</link>
			</item>
	<item>
		<title>Overseer 4.1.42 has been released</title>
		<description><![CDATA[I have just released Overseer 4.1.42. This is a small release that fixes a bug that I was just made aware of. The bug involved a red X on the resource selection screen in the Resource Discovery Wizard. Oddly enough, this bug was created when I upgraded the GUI library I use for Overseer, DevExpress. [...]]]></description>
		<link>http://www.overseer-network-monitor.com/weblog/2011/10/05/overseer-4-1-42-has-been-released/</link>
			</item>
	<item>
		<title>How to compact an Overseer 4.1 database</title>
		<description><![CDATA[Overseer generally maintains its own database and doesn&#8217;t bloat significantly larger than it needs to be to hold your data. However, in some limited situations, it may be beneficial to compact the database if it gets quite large for some reason. This function should be built into Overseer at a future time, but for now [...]]]></description>
		<link>http://www.overseer-network-monitor.com/weblog/2011/09/23/how-to-compact-an-overseer-4-1-database/</link>
			</item>
	<item>
		<title>Overseer 4.1.41 has been released</title>
		<description><![CDATA[Overseer 4.1.41 has been released. This is primarily for a bug fix that only affects those using EM1 environmental monitors, and monitoring relative humidity with that monitor. As a side note, I plan on adding support for an inexpensive USB temperature monitoring device soon. These devices will be available for sale on our website at [...]]]></description>
		<link>http://www.overseer-network-monitor.com/weblog/2011/08/17/overseer-4-1-41-has-been-released/</link>
			</item>
	<item>
		<title>Referring to computers by multiple names can cause issues</title>
		<description><![CDATA[Overseer Network Monitor is designed to monitor multiple resources on multiple computers from one location. To do this, the user must enter in the appropriate credentials for these computers(usually the domain administrator account). When Overseer checks the resources, it impersonates this user so it has adequate privileges to perform this monitoring. This generally works quite well, but [...]]]></description>
		<link>http://www.overseer-network-monitor.com/weblog/2011/08/09/referring-to-computers-by-multiple-names-can-cause-issues/</link>
			</item>
</channel>
</rss>

