<?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 for Geoff @ UVM</title>
	<atom:link href="http://gcd.w3.uvm.edu/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://gcd.w3.uvm.edu</link>
	<description>Adventures in System Administration</description>
	<lastBuildDate>Thu, 14 Jun 2012 19:55:51 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.5.1</generator>
	<item>
		<title>Comment on Event data mining with PowerShell by Geoff @ UVM - Custom event log queries</title>
		<link>http://gcd.w3.uvm.edu/2010/11/event-data-mining-with-powershell/comment-page-1/#comment-1028</link>
		<dc:creator>Geoff @ UVM - Custom event log queries</dc:creator>
		<pubDate>Thu, 14 Jun 2012 19:55:51 +0000</pubDate>
		<guid isPermaLink="false">https://www.uvm.edu/~gcd/?p=340#comment-1028</guid>
		<description><![CDATA[[...] can save use the query XML with PowerShell’s Get-WinEvent commandlet’s -filterXML parameter [See an example]. You can also use the Save Filter to Custom View option to make this view [...]]]></description>
		<content:encoded><![CDATA[<p>[...] can save use the query XML with PowerShell’s Get-WinEvent commandlet’s -filterXML parameter [See an example]. You can also use the Save Filter to Custom View option to make this view [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Troubleshooting Office 2010 &amp; 2013 Activation by Geoff</title>
		<link>http://gcd.w3.uvm.edu/2010/12/troubleshooting-office-2010-activation/comment-page-1/#comment-960</link>
		<dc:creator>Geoff</dc:creator>
		<pubDate>Wed, 24 Aug 2011 16:07:56 +0000</pubDate>
		<guid isPermaLink="false">https://www.uvm.edu/~gcd/?p=380#comment-960</guid>
		<description><![CDATA[I&#039;m glad you found it useful.]]></description>
		<content:encoded><![CDATA[<p>I&#8217;m glad you found it useful.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Troubleshooting Office 2010 &amp; 2013 Activation by Kelvin Chu</title>
		<link>http://gcd.w3.uvm.edu/2010/12/troubleshooting-office-2010-activation/comment-page-1/#comment-959</link>
		<dc:creator>Kelvin Chu</dc:creator>
		<pubDate>Wed, 24 Aug 2011 15:47:54 +0000</pubDate>
		<guid isPermaLink="false">https://www.uvm.edu/~gcd/?p=380#comment-959</guid>
		<description><![CDATA[Thank you for writing this.  

Extremely useful.]]></description>
		<content:encoded><![CDATA[<p>Thank you for writing this.  </p>
<p>Extremely useful.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Troubleshooting Office 2010 &amp; 2013 Activation by Microsoft Office Troubleshooting &#183; Geoff @ UVM</title>
		<link>http://gcd.w3.uvm.edu/2010/12/troubleshooting-office-2010-activation/comment-page-1/#comment-938</link>
		<dc:creator>Microsoft Office Troubleshooting &#183; Geoff @ UVM</dc:creator>
		<pubDate>Fri, 10 Dec 2010 14:21:40 +0000</pubDate>
		<guid isPermaLink="false">https://www.uvm.edu/~gcd/?p=380#comment-938</guid>
		<description><![CDATA[[...] strategies for troubleshooting problems with Microsoft Office. I spent some time addressing the activation issues relating specifically Office 2010, which I wrote up in a separate [...]]]></description>
		<content:encoded><![CDATA[<p>[...] strategies for troubleshooting problems with Microsoft Office. I spent some time addressing the activation issues relating specifically Office 2010, which I wrote up in a separate [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on 2008 R2 DCDIAG errors with NIC teaming by srehfuss</title>
		<link>http://gcd.w3.uvm.edu/2010/05/2008-r2-dcdiag-errors-with-nic-teaming/comment-page-1/#comment-937</link>
		<dc:creator>srehfuss</dc:creator>
		<pubDate>Sun, 05 Dec 2010 07:30:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.uvm.edu/~gcd/2010/05/2008-r2-dcdiag-errors-with-nic-teaming/#comment-937</guid>
		<description><![CDATA[Thanks Geoff. I spent a long time trying to figure out the same problem. My VM 2008 R2 domain controllers were perfectly fine when joining my native 2003 domain but the hardware (HP DL360 G6 w/ dual GB Broadcom nics) server I am setting up with teamed NICs got the same RPC Connectivity error. This post saved me a lot of time. Thank you again.]]></description>
		<content:encoded><![CDATA[<p>Thanks Geoff. I spent a long time trying to figure out the same problem. My VM 2008 R2 domain controllers were perfectly fine when joining my native 2003 domain but the hardware (HP DL360 G6 w/ dual GB Broadcom nics) server I am setting up with teamed NICs got the same RPC Connectivity error. This post saved me a lot of time. Thank you again.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Compiling OpenSSL for Win x64 by jgm</title>
		<link>http://gcd.w3.uvm.edu/2010/09/compiling-openssl-for-win-x64/comment-page-1/#comment-933</link>
		<dc:creator>jgm</dc:creator>
		<pubDate>Thu, 23 Sep 2010 20:25:57 +0000</pubDate>
		<guid isPermaLink="false">https://www.uvm.edu/~gcd/2010/09/compiling-openssl-for-win-x64/#comment-933</guid>
		<description><![CDATA[&quot;Shining Light Productions&quot; has been maintaining precompiled OpenSSL binaries for Windows for quite some time... 64-bit, too.
http://www.slproweb.com/products/Win32OpenSSL.html]]></description>
		<content:encoded><![CDATA[<p>&#8220;Shining Light Productions&#8221; has been maintaining precompiled OpenSSL binaries for Windows for quite some time&#8230; 64-bit, too.<br />
<a href="http://www.slproweb.com/products/Win32OpenSSL.html" rel="nofollow">http://www.slproweb.com/products/Win32OpenSSL.html</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Domain Controller Blue Screen by us3rn4me</title>
		<link>http://gcd.w3.uvm.edu/2010/02/domain-controller-blue-screen/comment-page-1/#comment-895</link>
		<dc:creator>us3rn4me</dc:creator>
		<pubDate>Wed, 21 Jul 2010 16:32:34 +0000</pubDate>
		<guid isPermaLink="false">http://www.uvm.edu/~gcd/2010/02/domain-controller-blue-screen/#comment-895</guid>
		<description><![CDATA[Thank you for this article.  After troubleshooting this issue, V2V Windows Server 2008 Hyper-V to ESX vSphere (using stand-alone converter), the issue was resolved in bringing disk1 and disk2 online.  It was a late night working on this Domain Controller and a relief to have it migrated - thanks again - appreciated the insight.]]></description>
		<content:encoded><![CDATA[<p>Thank you for this article.  After troubleshooting this issue, V2V Windows Server 2008 Hyper-V to ESX vSphere (using stand-alone converter), the issue was resolved in bringing disk1 and disk2 online.  It was a late night working on this Domain Controller and a relief to have it migrated &#8211; thanks again &#8211; appreciated the insight.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Troubleshooting Windows Activation by &#187; Vista activation issues E-Musings from the Dean : University of Vermont</title>
		<link>http://gcd.w3.uvm.edu/2008/09/troubleshooting-windows-activation/comment-page-1/#comment-894</link>
		<dc:creator>&#187; Vista activation issues E-Musings from the Dean : University of Vermont</dc:creator>
		<pubDate>Thu, 15 Jul 2010 13:17:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.uvm.edu/~gcd/?p=59#comment-894</guid>
		<description><![CDATA[[...] Pretty much every Optiplex GX755 desktop purchased and deployed by the College during January 2008 has had Vista activation issues. We believe that this issue was triggered by the recent deployment of Vista Service Pack 1 through Active Directory. The version of Vista that we use here at UVM is Vista Enterprise. Vista Enterprise uses a centralized license server, called a KMS server, to provide authentication information back to Vista, &#8220;authenticating&#8221; Vista for another time period after which the computer will again look for the KMS server. If the computer cannot find the KMS server, the original version of Vista would go into Reduced Functionality Mode (RFM) which is another way of saying that it becomes useless. As of Service Pack 1, Microsoft has eliminated RFM. Instead Vista Enterprise will become nagware, posting endless notices that you may be running pirated software and asking you for a product key. The product key on the sticker on your computer is, of course, for the OEM version of Vista which is NOT what&#8217;s currently installed on your computer The fix for this is to simply provide the generic product key (VKK3X-68KWM-X2YGT-QR4M6-4BWMV), which tells Vista Enterprise to look for the server again and all is well. Geoff Duke has more information on this on his Blog [...]]]></description>
		<content:encoded><![CDATA[<p>[...] Pretty much every Optiplex GX755 desktop purchased and deployed by the College during January 2008 has had Vista activation issues. We believe that this issue was triggered by the recent deployment of Vista Service Pack 1 through Active Directory. The version of Vista that we use here at UVM is Vista Enterprise. Vista Enterprise uses a centralized license server, called a KMS server, to provide authentication information back to Vista, &#8220;authenticating&#8221; Vista for another time period after which the computer will again look for the KMS server. If the computer cannot find the KMS server, the original version of Vista would go into Reduced Functionality Mode (RFM) which is another way of saying that it becomes useless. As of Service Pack 1, Microsoft has eliminated RFM. Instead Vista Enterprise will become nagware, posting endless notices that you may be running pirated software and asking you for a product key. The product key on the sticker on your computer is, of course, for the OEM version of Vista which is NOT what&#8217;s currently installed on your computer The fix for this is to simply provide the generic product key (VKK3X-68KWM-X2YGT-QR4M6-4BWMV), which tells Vista Enterprise to look for the server again and all is well. Geoff Duke has more information on this on his Blog [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Troubleshooting Windows Activation by &#187; Vista activation issues CAS Online Media Archive : University of Vermont</title>
		<link>http://gcd.w3.uvm.edu/2008/09/troubleshooting-windows-activation/comment-page-1/#comment-893</link>
		<dc:creator>&#187; Vista activation issues CAS Online Media Archive : University of Vermont</dc:creator>
		<pubDate>Thu, 15 Jul 2010 13:17:19 +0000</pubDate>
		<guid isPermaLink="false">http://www.uvm.edu/~gcd/?p=59#comment-893</guid>
		<description><![CDATA[[...] Pretty much every Optiplex GX755 desktop purchased and deployed by the College during January 2008 has had Vista activation issues. We believe that this issue was triggered by the recent deployment of Vista Service Pack 1 through Active Directory. The version of Vista that we use here at UVM is Vista Enterprise. Vista Enterprise uses a centralized license server, called a KMS server, to provide authentication information back to Vista, &#8220;authenticating&#8221; Vista for another time period after which the computer will again look for the KMS server. If the computer cannot find the KMS server, the original version of Vista would go into Reduced Functionality Mode (RFM) which is another way of saying that it becomes useless. As of Service Pack 1, Microsoft has eliminated RFM. Instead Vista Enterprise will become nagware, posting endless notices that you may be running pirated software and asking you for a product key. The product key on the sticker on your computer is, of course, for the OEM version of Vista which is NOT what&#8217;s currently installed on your computer The fix for this is to simply provide the generic product key (VKK3X-68KWM-X2YGT-QR4M6-4BWMV), which tells Vista Enterprise to look for the server again and all is well. Geoff Duke has more information on this on his Blog [...]]]></description>
		<content:encoded><![CDATA[<p>[...] Pretty much every Optiplex GX755 desktop purchased and deployed by the College during January 2008 has had Vista activation issues. We believe that this issue was triggered by the recent deployment of Vista Service Pack 1 through Active Directory. The version of Vista that we use here at UVM is Vista Enterprise. Vista Enterprise uses a centralized license server, called a KMS server, to provide authentication information back to Vista, &#8220;authenticating&#8221; Vista for another time period after which the computer will again look for the KMS server. If the computer cannot find the KMS server, the original version of Vista would go into Reduced Functionality Mode (RFM) which is another way of saying that it becomes useless. As of Service Pack 1, Microsoft has eliminated RFM. Instead Vista Enterprise will become nagware, posting endless notices that you may be running pirated software and asking you for a product key. The product key on the sticker on your computer is, of course, for the OEM version of Vista which is NOT what&#8217;s currently installed on your computer The fix for this is to simply provide the generic product key (VKK3X-68KWM-X2YGT-QR4M6-4BWMV), which tells Vista Enterprise to look for the server again and all is well. Geoff Duke has more information on this on his Blog [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Troubleshooting Windows Activation by &#187; Vista activation issues Hendrickson Trek 2009 : University of Vermont</title>
		<link>http://gcd.w3.uvm.edu/2008/09/troubleshooting-windows-activation/comment-page-1/#comment-892</link>
		<dc:creator>&#187; Vista activation issues Hendrickson Trek 2009 : University of Vermont</dc:creator>
		<pubDate>Thu, 15 Jul 2010 13:16:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.uvm.edu/~gcd/?p=59#comment-892</guid>
		<description><![CDATA[[...] Pretty much every Optiplex GX755 desktop purchased and deployed by the College during January 2008 has had Vista activation issues. We believe that this issue was triggered by the recent deployment of Vista Service Pack 1 through Active Directory. The version of Vista that we use here at UVM is Vista Enterprise. Vista Enterprise uses a centralized license server, called a KMS server, to provide authentication information back to Vista, &#8220;authenticating&#8221; Vista for another time period after which the computer will again look for the KMS server. If the computer cannot find the KMS server, the original version of Vista would go into Reduced Functionality Mode (RFM) which is another way of saying that it becomes useless. As of Service Pack 1, Microsoft has eliminated RFM. Instead Vista Enterprise will become nagware, posting endless notices that you may be running pirated software and asking you for a product key. The product key on the sticker on your computer is, of course, for the OEM version of Vista which is NOT what&#8217;s currently installed on your computer The fix for this is to simply provide the generic product key (VKK3X-68KWM-X2YGT-QR4M6-4BWMV), which tells Vista Enterprise to look for the server again and all is well. Geoff Duke has more information on this on his Blog [...]]]></description>
		<content:encoded><![CDATA[<p>[...] Pretty much every Optiplex GX755 desktop purchased and deployed by the College during January 2008 has had Vista activation issues. We believe that this issue was triggered by the recent deployment of Vista Service Pack 1 through Active Directory. The version of Vista that we use here at UVM is Vista Enterprise. Vista Enterprise uses a centralized license server, called a KMS server, to provide authentication information back to Vista, &#8220;authenticating&#8221; Vista for another time period after which the computer will again look for the KMS server. If the computer cannot find the KMS server, the original version of Vista would go into Reduced Functionality Mode (RFM) which is another way of saying that it becomes useless. As of Service Pack 1, Microsoft has eliminated RFM. Instead Vista Enterprise will become nagware, posting endless notices that you may be running pirated software and asking you for a product key. The product key on the sticker on your computer is, of course, for the OEM version of Vista which is NOT what&#8217;s currently installed on your computer The fix for this is to simply provide the generic product key (VKK3X-68KWM-X2YGT-QR4M6-4BWMV), which tells Vista Enterprise to look for the server again and all is well. Geoff Duke has more information on this on his Blog [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
