<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Computer Support &#187; system uptime</title>
	<atom:link href="http://www.xiitec.com/blog/tag/system-uptime/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.xiitec.com/blog</link>
	<description></description>
	<lastBuildDate>Wed, 30 Dec 2009 08:40:28 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Viewing System Uptime</title>
		<link>http://www.xiitec.com/blog/2008/02/20/viewing-system-uptime/</link>
		<comments>http://www.xiitec.com/blog/2008/02/20/viewing-system-uptime/#comments</comments>
		<pubDate>Wed, 20 Feb 2008 21:37:12 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[System configuration]]></category>
		<category><![CDATA[system uptime]]></category>

		<guid isPermaLink="false">http://www.xiitec.com/blog/?p=153</guid>
		<description><![CDATA[In the early days of Windows NT 3.51 and 4.0, it wasn&#8217;t uncommon for servers to reboot or need to be rebooted on a regular basis. Applications were not as well behaved as they are today and the operating system wasn&#8217;t as stable. This changed with Windows 2000, when unexpected failures became much less common. [...]]]></description>
			<content:encoded><![CDATA[<p>In the early days of Windows NT 3.51 and 4.0, it wasn&#8217;t uncommon for servers to reboot or need to be rebooted on a regular basis. Applications were not as well behaved as they are today and the operating system wasn&#8217;t as stable. This changed with Windows 2000, when unexpected failures became much less common. But there were still a lot of hotfixes and patches to install on a regular basis, most of which required reboots. Hopefully Windows Server 2003 will continue the upward trend in availability and further reduce the number of reboots that are required.</p>
<p><span id="more-153"></span></p>
<p>It is a good idea to pay attention to the uptime on your servers to make sure their availability jives with what you think it should be. Perhaps a server rebooted due to a blue screen or even worse, because another administrator (or attacker!) did something they shouldn&#8217;t have. Looking at system uptime is the poor man&#8217;s availability monitor. You may even want to create a script that runs at system startup on your servers, which can serve as a notification mechanism anytime your servers reboot.</p>
<p><strong>Using a command-line interface</strong></p>
<p>All three of the following commands display the system uptime:</p>
<pre>&gt; psinfo \\<servername> | findstr Uptime
 &gt; srvinfo \\<servername> | findstr /c:"Up Time"
 &gt; systeminfo /s <servername> | findstr /c:"Up Time"</servername></servername></servername></pre>
<p><strong>Using VBScript</strong></p>
<pre>' This code prints system uptime for a host.
 ' ------ SCRIPT CONFIGURATION ------
 strComputer = "."   ' e.g., rallen-srv01
 ' ------ END CONFIGURATION ---------
 set objWMIDateTime = CreateObject("WbemScripting.SWbemDateTime")
 set objWMI = GetObject("winmgmts:\\" &amp; strComputer &amp; "\root\cimv2")
 set colOS = objWMI.InstancesOf("Win32_OperatingSystem")
 for each objOS in colOS
    objWMIDateTime.Value = objOS.LastBootUpTime
    Wscript.Echo "System Up Time: " &amp; objWMIDateTime.GetVarDate
 next</pre>
]]></content:encoded>
			<wfw:commentRss>http://www.xiitec.com/blog/2008/02/20/viewing-system-uptime/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

