<?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>A Technical Journey &#187; Windows</title>
	<atom:link href="http://www.technicaljourney.com/category/windows/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.technicaljourney.com</link>
	<description>www.technicaljourney.com - Web Blog Of Paul McSharry, Technical Consultant &#38; Trainer.</description>
	<lastBuildDate>Thu, 12 Aug 2010 12:02:36 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
		<item>
		<title>Install VMware vCentre On 64 Bit Windows Server</title>
		<link>http://www.technicaljourney.com/2010/07/install-vcentre-64-bit/</link>
		<comments>http://www.technicaljourney.com/2010/07/install-vcentre-64-bit/#comments</comments>
		<pubDate>Sun, 18 Jul 2010 21:40:15 +0000</pubDate>
		<dc:creator>Paul McSharry</dc:creator>
				<category><![CDATA[Vmware]]></category>
		<category><![CDATA[Windows]]></category>

		<guid isPermaLink="false">http://www.technicaljourney.com/?p=199</guid>
		<description><![CDATA[The vCentre server role is a critical component of a vSphere deployment.   The role requires a database  such as SQL or Oracle.   To install the vCentre a 32 bit ODBC connection is required.  When installing the role on a 64 bit server OS (ie Windows 2008 R2),  the installer will fail giving the error shown in [...]]]></description>
			<content:encoded><![CDATA[<p>The vCentre server role is a critical component of a vSphere deployment.   The role requires a database  such as SQL or Oracle.  </p>
<p>To install the vCentre a 32 bit ODBC connection is required.  When installing the role on a 64 bit server OS (ie Windows 2008 R2),  the installer will fail giving the error shown in the screenshot below.</p>
<p><a href="http://www.technicaljourney.com/wp-content/uploads/2010/07/32bit_required.jpg"><img class="size-medium wp-image-200 alignleft" title="32bit_required" src="http://www.technicaljourney.com/wp-content/uploads/2010/07/32bit_required-300x103.jpg" alt="" width="300" height="103" /></a></p>
<p>To configure a 32 BIT Odbc connection on a 64 Bit version of windows use the following;</p>
<p><em>Start &gt; Run<br />
%systemdrive%\Windows\SysWoW64\Odbcad32.exe<br />
Click ok<br />
Select System DSN  and complete the wizard in the normal manner</em>.</p>
<p>Please note that a 32 Bit odbc connection will not be dispayed in the default 64 bit odbc data source administrator manager.  Use odbcad32.exe  to view the settings.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.technicaljourney.com/2010/07/install-vcentre-64-bit/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Checked Builds Of Windows 2008 BSOD STOP: 0x0000008E Error With Vmware</title>
		<link>http://www.technicaljourney.com/2010/04/checked-builds-of-windows-2008-bsod-stop-0x0000008e-error-with-vmware/</link>
		<comments>http://www.technicaljourney.com/2010/04/checked-builds-of-windows-2008-bsod-stop-0x0000008e-error-with-vmware/#comments</comments>
		<pubDate>Sat, 03 Apr 2010 20:01:46 +0000</pubDate>
		<dc:creator>Paul McSharry</dc:creator>
				<category><![CDATA[Vmware]]></category>
		<category><![CDATA[Windows]]></category>

		<guid isPermaLink="false">http://www.technicaljourney.com/?p=142</guid>
		<description><![CDATA[When creating a Vmware Virtual Machine guest,  running a  Windows Server 2008 checked build from sources such as technet, or MSDN, a blue screen of death may occur ( ie  STOP:0x0000008E). This is caused by the windows HAL being violated within the Virtual Machine.  A fix for this issue is to  add the below line [...]]]></description>
			<content:encoded><![CDATA[<p>When creating a Vmware Virtual Machine guest,  running a  Windows Server 2008 checked build from sources such as technet, or MSDN, a blue screen of death may occur ( ie  STOP:0x0000008E).</p>
<p>This is caused by the windows HAL being violated within the Virtual Machine. </p>
<p>A fix for this issue is to  add the below line to the virtual machine&#8217;s configuration (.vmx file).</p>
<p><strong>piix4pm.smooth_acpi_timer = TRUE</strong></p>
]]></content:encoded>
			<wfw:commentRss>http://www.technicaljourney.com/2010/04/checked-builds-of-windows-2008-bsod-stop-0x0000008e-error-with-vmware/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>PowerShell &#8211; Clean Up Script &#8211; Files older than X number of days</title>
		<link>http://www.technicaljourney.com/2010/03/powershell-clean-up-script-files-older-than-x-number-of-days/</link>
		<comments>http://www.technicaljourney.com/2010/03/powershell-clean-up-script-files-older-than-x-number-of-days/#comments</comments>
		<pubDate>Thu, 04 Mar 2010 22:43:41 +0000</pubDate>
		<dc:creator>Paul McSharry</dc:creator>
				<category><![CDATA[Powershell]]></category>
		<category><![CDATA[Windows]]></category>

		<guid isPermaLink="false">http://www.technicaljourney.com/?p=69</guid>
		<description><![CDATA[I have been working with development teams for many years.  One of the most common requests, especially with development and test servers is to automate the deleting of  old log or temp file folders.  Most of the time these files contain debug information, and do not need archiving, but tend to fill the drives to capacity if not maintained.   To [...]]]></description>
			<content:encoded><![CDATA[<p>I have been working with development teams for many years.  One of the most common requests, especially with development and test servers is to automate the deleting of  old log or temp file folders.  Most of the time these files contain debug information, and do not need archiving, but tend to fill the drives to capacity if not maintained.  </p>
<p>To Solve this issue,  the following clean up powershell script is useful;</p>
<blockquote><p>#powershell clean up script based on file write time</p>
<p>gci &#8220;e:\temp\*.*”|? {$_.lastwritetime -lt (get-date).adddays(-1)} |</p></blockquote>
<blockquote><p>remove-item</p></blockquote>
<p>To run this script,   set the powershell  execution policy to RemoteSigned (run the command <em>set-</em><em>ExecutionPolicy RemoteSigned ) </em>and save the powershell  script  in a .ps1 file.</p>
<p>To configure the script, change the directory path (e:\temp\*.* in this example)  and the number of days required (-1).</p>
<p>To test the script add –whatif  after the “remote-item” cmdlet.  This will show the files that would be deleted and no data will be lost if errors exist.</p>
<p>Once tested, to schedule it  create a batch file with the following   (change the powershell file location).</p>
<blockquote><p>powershell -command &#8220;&amp; &#8216;c:\delete.ps1&#8242; &#8220;</p></blockquote>
<p>You can now schedule the script with the Windows task scheduler (point to the batchfile).</p>
]]></content:encoded>
			<wfw:commentRss>http://www.technicaljourney.com/2010/03/powershell-clean-up-script-files-older-than-x-number-of-days/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Check Exchange 2007 Server Edition Level</title>
		<link>http://www.technicaljourney.com/2010/02/check-exchange-2007-server-edition-level/</link>
		<comments>http://www.technicaljourney.com/2010/02/check-exchange-2007-server-edition-level/#comments</comments>
		<pubDate>Fri, 05 Feb 2010 15:34:42 +0000</pubDate>
		<dc:creator>Paul McSharry</dc:creator>
				<category><![CDATA[Exchange 2007]]></category>
		<category><![CDATA[Powershell]]></category>
		<category><![CDATA[Windows]]></category>

		<guid isPermaLink="false">http://www.technicaljourney.com/?p=65</guid>
		<description><![CDATA[To confirm the Exchange 2007 server edition (ie standard or enterprise),  run the following powershell one-liner  from the Exchange Management shell Get-ExchangeServer &#124; fl name,edition,admindisplayversion As the example output shows below,  each exchange server in the organisation will be listed with name, edition, and build/patch level. Name                : [...]]]></description>
			<content:encoded><![CDATA[<p>To confirm the Exchange 2007 server edition (ie standard or enterprise),  run the following powershell one-liner  from the Exchange Management shell</p>
<blockquote>
<p style="text-align: center;"><em>Get-ExchangeServer | fl name,edition,admindisplayversion</em></p>
</blockquote>
<p style="text-align: left;"><em><span style="font-style: normal;">As the example output shows below,  each exchange server in the organisation will be listed with name, edition, and build/patch level.</span></em></p>
<div id="_mcePaste">Name                : Mail1</div>
<div id="_mcePaste">Edition             : Enterprise</div>
<div id="_mcePaste">AdminDisplayVersion : Version 6.5 (Build 7638.2: Service Pack 2)</div>
<div id="_mcePaste">Name                : Mail2</div>
<div id="_mcePaste">Edition             : Enterprise</div>
<div id="_mcePaste">AdminDisplayVersion : Version 8.1 (Build 240.6)</div>
<div>Name                : Mail3</div>
<div id="_mcePaste">Edition             : Enterprise</div>
<div id="_mcePaste">AdminDisplayVersion : Version 8.1 (Build 240.6)</div>
<div>Name                : Mail4</div>
<div id="_mcePaste">Edition             : Enterprise</div>
<div id="_mcePaste">AdminDisplayVersion : Version 8.1 (Build 240.6)</div>
]]></content:encoded>
			<wfw:commentRss>http://www.technicaljourney.com/2010/02/check-exchange-2007-server-edition-level/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Sync Windows  Server To Centralised Time Sources</title>
		<link>http://www.technicaljourney.com/2010/02/sync-windows-ntp/</link>
		<comments>http://www.technicaljourney.com/2010/02/sync-windows-ntp/#comments</comments>
		<pubDate>Tue, 02 Feb 2010 10:33:59 +0000</pubDate>
		<dc:creator>Paul McSharry</dc:creator>
				<category><![CDATA[Ports]]></category>
		<category><![CDATA[Windows]]></category>

		<guid isPermaLink="false">http://www.technicaljourney.com/?p=60</guid>
		<description><![CDATA[It is a common requirement for all servers in a solution, to have the same system time.  This can be achieved using NTP service. To synchronise a client machine with a time source or list of time sources (10.10.10.1, 10.10.10.2, 10.10.10.3), go to command line w32tm /configure /manualpeerlist: &#8220;10.10.10.1,0&#215;1, 10.10.10.2,ox1 ,10.10.10.3,0&#215;1 &#8221; /update net stop w32time net start [...]]]></description>
			<content:encoded><![CDATA[<p>It is a common requirement for all servers in a solution, to have the same system time.  This can be achieved using NTP service.</p>
<p>To synchronise a client machine with a time source or list of time sources (10.10.10.1, 10.10.10.2, 10.10.10.3),</p>
<p>go to command line</p>
<blockquote><p><em>w32tm /configure /manualpeerlist: &#8220;10.10.10.1,0&#215;1, 10.10.10.2,ox1 ,10.10.10.3,0&#215;1 &#8221; /update</em></p>
<p><em>net stop w32time</em></p>
<p><em>net start w32time</em></p></blockquote>
<p><em>To check time between source</em></p>
<blockquote><p><em>w32tm /stripchart /computer:10.10.10.1</em></p></blockquote>
<p><em>Note:  UDP port 123 for NTP is required.</em></p>
]]></content:encoded>
			<wfw:commentRss>http://www.technicaljourney.com/2010/02/sync-windows-ntp/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Extend Windows 7 &amp; Windows 2008 Grace Period.</title>
		<link>http://www.technicaljourney.com/2010/01/extend-windows-7-2008-grace-period/</link>
		<comments>http://www.technicaljourney.com/2010/01/extend-windows-7-2008-grace-period/#comments</comments>
		<pubDate>Mon, 04 Jan 2010 16:49:40 +0000</pubDate>
		<dc:creator>Paul McSharry</dc:creator>
				<category><![CDATA[Active Directory]]></category>
		<category><![CDATA[Windows]]></category>

		<guid isPermaLink="false">http://www.technicaljourney.com/?p=54</guid>
		<description><![CDATA[On Installation Windows 7 requires licence activation. By default the grace period to do this is 30 days. If for legitimate reasons this needs to be extended, it is possible to reset this a maximum  of 3 times.  Resulting in a total 120 days grace period. This option is activated by running a command prompt [...]]]></description>
			<content:encoded><![CDATA[<p>On Installation Windows 7 requires licence activation. By default the grace period to do this is 30 days.</p>
<p>If for legitimate reasons this needs to be extended, it is possible to reset this a maximum  of 3 times.  Resulting in a total 120 days grace period.</p>
<p>This option is activated by running a command prompt session in administrator mode and entering the following;</p>
<blockquote><p>slmgr.vbs -rearm</p></blockquote>
<p>A message box will be displayed and the machine will need to be restarted.</p>
<p>This is a Microsoft supported option, and does not violate the EULA<br />
This also applies to windows vista.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.technicaljourney.com/2010/01/extend-windows-7-2008-grace-period/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>The date windows was installed.</title>
		<link>http://www.technicaljourney.com/2009/12/the-date-windows-was-installed/</link>
		<comments>http://www.technicaljourney.com/2009/12/the-date-windows-was-installed/#comments</comments>
		<pubDate>Mon, 14 Dec 2009 17:16:06 +0000</pubDate>
		<dc:creator>Paul McSharry</dc:creator>
				<category><![CDATA[Active Directory]]></category>
		<category><![CDATA[Windows]]></category>

		<guid isPermaLink="false">http://www.technicaljourney.com/?p=26</guid>
		<description><![CDATA[On many occasions it is useful to know the date a windows machine was created/installed. This useful oneliner solves the issue From the CMD prompt run systeminfo &#124; find /i &#8220;install date&#8221; Example output Original Install Date: 28/11/2009, 11:17:44  ]]></description>
			<content:encoded><![CDATA[<p>On many occasions it is useful to know the date a windows machine was created/installed.</p>
<p>This useful oneliner solves the issue</p>
<p>From the CMD prompt run</p>
<blockquote>
<p style="text-align: center;">systeminfo | find /i &#8220;install date&#8221;</p>
</blockquote>
<p style="text-align: left;">Example output</p>
<p style="text-align: left;">Original Install Date: 28/11/2009, 11:17:44</p>
<p style="text-align: center;"> </p>
]]></content:encoded>
			<wfw:commentRss>http://www.technicaljourney.com/2009/12/the-date-windows-was-installed/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
