<?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>Unflappings &#187; Windows</title>
	<atom:link href="http://blog.unflap.com/category/howtos/windows/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.unflap.com</link>
	<description>Network and Systems Documentation</description>
	<lastBuildDate>Wed, 11 Aug 2010 18:13:16 +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>Trouble with VMware NICs and File Sharing Permissions</title>
		<link>http://blog.unflap.com/2010/03/04/trouble-with-vmware-nics-and-file-sharing-permissions/</link>
		<comments>http://blog.unflap.com/2010/03/04/trouble-with-vmware-nics-and-file-sharing-permissions/#comments</comments>
		<pubDate>Thu, 04 Mar 2010 22:41:54 +0000</pubDate>
		<dc:creator>Andrew</dc:creator>
				<category><![CDATA[Quick Fixes]]></category>
		<category><![CDATA[Windows]]></category>
		<category><![CDATA[7]]></category>
		<category><![CDATA[Linux]]></category>
		<category><![CDATA[network]]></category>
		<category><![CDATA[openfiler]]></category>
		<category><![CDATA[vista]]></category>
		<category><![CDATA[windows 7]]></category>
		<category><![CDATA[windows vista]]></category>

		<guid isPermaLink="false">http://blog.unflap.com/?p=161</guid>
		<description><![CDATA[For anyone who is trying to access file shares inside local VM&#8217;s running windows Vista or Windows 7, the following article does a great job explaining what needs to be done in order to change the &#8220;Location&#8221; of the VMware NICs. Apparently by default Windows cannot figure out what or where they are, so it [...]]]></description>
		<wfw:commentRss>http://blog.unflap.com/2010/03/04/trouble-with-vmware-nics-and-file-sharing-permissions/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Convert a PFX file to a PEM file</title>
		<link>http://blog.unflap.com/2010/03/03/convert-a-pfx-file-to-a-pem-file/</link>
		<comments>http://blog.unflap.com/2010/03/03/convert-a-pfx-file-to-a-pem-file/#comments</comments>
		<pubDate>Wed, 03 Mar 2010 20:42:09 +0000</pubDate>
		<dc:creator>Andrew</dc:creator>
				<category><![CDATA[General]]></category>
		<category><![CDATA[HowTos]]></category>
		<category><![CDATA[Linux]]></category>
		<category><![CDATA[Windows]]></category>
		<category><![CDATA[certificates]]></category>
		<category><![CDATA[openssl]]></category>
		<category><![CDATA[pem]]></category>
		<category><![CDATA[pfx]]></category>
		<category><![CDATA[pki]]></category>
		<category><![CDATA[ssl]]></category>
		<category><![CDATA[windows server]]></category>

		<guid isPermaLink="false">http://blog.unflap.com/?p=155</guid>
		<description><![CDATA[Bold indicates a button clicked or key pressed. “quotes” indicates a value which has been entered. Grey block quote is a command typed directly into the console. Purpose The following steps allow you to convert a PFX certificate file in Windows Server to a PEM file. This is important since most Linux/Unix systems prefer a [...]]]></description>
		<wfw:commentRss>http://blog.unflap.com/2010/03/03/convert-a-pfx-file-to-a-pem-file/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Restrict AD users from Certain Domain Machines in Server 2003</title>
		<link>http://blog.unflap.com/2009/11/02/restrict-ad-users-from-certain-domain-machines-in-server-2003/</link>
		<comments>http://blog.unflap.com/2009/11/02/restrict-ad-users-from-certain-domain-machines-in-server-2003/#comments</comments>
		<pubDate>Tue, 03 Nov 2009 01:11:49 +0000</pubDate>
		<dc:creator>rtrinkle</dc:creator>
				<category><![CDATA[HowTos]]></category>
		<category><![CDATA[Operating Systems]]></category>
		<category><![CDATA[Windows]]></category>

		<guid isPermaLink="false">http://blog.unflap.com/?p=99</guid>
		<description><![CDATA[This guide is mainly helpful for when you need to lock down a computer using GPO’s and Active Directory. The situation here is a group of users which need to be locked down to the bare minimum usability features. In addition, the computers in which these users sign on are in highly sensitive areas, requiring [...]]]></description>
		<wfw:commentRss>http://blog.unflap.com/2009/11/02/restrict-ad-users-from-certain-domain-machines-in-server-2003/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Windows Server 2003 R2 IAS Installation</title>
		<link>http://blog.unflap.com/2009/10/06/windows-server-2003-r2-ias-installation/</link>
		<comments>http://blog.unflap.com/2009/10/06/windows-server-2003-r2-ias-installation/#comments</comments>
		<pubDate>Wed, 07 Oct 2009 00:32:29 +0000</pubDate>
		<dc:creator>Andrew</dc:creator>
				<category><![CDATA[HowTos]]></category>
		<category><![CDATA[Windows]]></category>
		<category><![CDATA[IAS]]></category>
		<category><![CDATA[microsoft]]></category>
		<category><![CDATA[RADIUS]]></category>
		<category><![CDATA[windows server 2003]]></category>

		<guid isPermaLink="false">http://blog.unflap.com/?p=61</guid>
		<description><![CDATA[Bold indicates a button clicked or key pressed. “quotes” indicates a value which has been entered. Grey block quote is a command typed directly into the console. Procedures 1. Navigate to Start &#124; Control Panel &#124; Add/Remove Programs &#124; Add/Remove Windows Components 2. Networking Services &#124; Details &#124; Internet Authentication Service &#124; Ok &#124; Next [...]]]></description>
		<wfw:commentRss>http://blog.unflap.com/2009/10/06/windows-server-2003-r2-ias-installation/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
<!-- WP Super Cache is installed but broken. The path to wp-cache-phase1.php in wp-content/advanced-cache.php must be fixed! -->