<?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/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
	>

<channel>
	<title>Web Active Directory Blog &#187; Powershell</title>
	<atom:link href="http://blog.webactivedirectory.com/category/powershell/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.webactivedirectory.com</link>
	<description>Sharing Active Directory Best Practices</description>
	<lastBuildDate>Thu, 02 Feb 2012 16:51:24 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
<cloud domain='blog.webactivedirectory.com' port='80' path='/?rsscloud=notify' registerProcedure='' protocol='http-post' />
<image>
		<url>http://s2.wp.com/i/buttonw-com.png</url>
		<title>Web Active Directory Blog &#187; Powershell</title>
		<link>http://blog.webactivedirectory.com</link>
	</image>
	<atom:link rel="search" type="application/opensearchdescription+xml" href="http://blog.webactivedirectory.com/osd.xml" title="Web Active Directory Blog" />
	<atom:link rel='hub' href='http://blog.webactivedirectory.com/?pushpress=hub'/>
		<item>
		<title>Active Directory Management Gateway Service (ADMGS) Errors and McAfee Anti-Virus Software</title>
		<link>http://blog.webactivedirectory.com/2012/01/20/active-directory-management-gateway-service-admgs-errors-and-anti-virus-software/</link>
		<comments>http://blog.webactivedirectory.com/2012/01/20/active-directory-management-gateway-service-admgs-errors-and-anti-virus-software/#comments</comments>
		<pubDate>Fri, 20 Jan 2012 16:00:11 +0000</pubDate>
		<dc:creator>Jason Cox</dc:creator>
				<category><![CDATA[Active Directory]]></category>
		<category><![CDATA[Active Directory Management Gateway Service]]></category>
		<category><![CDATA[Microsoft Active Directory]]></category>
		<category><![CDATA[PeopleProvision]]></category>
		<category><![CDATA[Powershell]]></category>
		<category><![CDATA[Windows 7]]></category>
		<category><![CDATA[Windows Server 2008]]></category>
		<category><![CDATA[Windows Server 2008 R2]]></category>
		<category><![CDATA[AD]]></category>
		<category><![CDATA[ADMGS]]></category>
		<category><![CDATA[windows 7]]></category>
		<category><![CDATA[windows server 2008]]></category>
		<category><![CDATA[windows server 2008 R2]]></category>

		<guid isPermaLink="false">http://blog.webactivedirectory.com/?p=1826</guid>
		<description><![CDATA[I posted last month about an issue with the Active Directory Management Gateway Service (ADMGS) on Windows Server 2008. The ADMGS  (which runs as the Active Directory Web Services, ADWS, service) allows you to use the Active Directory module for Windows PowerShell to manage AD remotely in domains where there are no Server 2008 R2 domain [...]<img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=blog.webactivedirectory.com&amp;blog=10038206&amp;post=1826&amp;subd=webactivedirectory&amp;ref=&amp;feed=1" width="1" height="1" />]]></description>
		<wfw:commentRss>http://blog.webactivedirectory.com/2012/01/20/active-directory-management-gateway-service-admgs-errors-and-anti-virus-software/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
	
		<media:content url="http://0.gravatar.com/avatar/e36fd0d4f4c557faea46d2b82b24e1d1?s=96&#38;d=identicon&#38;r=G" medium="image">
			<media:title type="html">jasonpcox21</media:title>
		</media:content>
	</item>
		<item>
		<title>Diagnose Active Directory Management Gateway Service (ADMGS) Errors</title>
		<link>http://blog.webactivedirectory.com/2011/12/15/diagnose-active-directory-management-gateway-service-admgs-errors/</link>
		<comments>http://blog.webactivedirectory.com/2011/12/15/diagnose-active-directory-management-gateway-service-admgs-errors/#comments</comments>
		<pubDate>Thu, 15 Dec 2011 15:00:53 +0000</pubDate>
		<dc:creator>Jason Cox</dc:creator>
				<category><![CDATA[Active Directory]]></category>
		<category><![CDATA[Active Directory Management Gateway Service]]></category>
		<category><![CDATA[Microsoft Active Directory]]></category>
		<category><![CDATA[PeopleProvision]]></category>
		<category><![CDATA[Powershell]]></category>
		<category><![CDATA[Windows 7]]></category>
		<category><![CDATA[Windows Server 2008]]></category>
		<category><![CDATA[Windows Server 2008 R2]]></category>
		<category><![CDATA[AD]]></category>
		<category><![CDATA[ADMGS]]></category>
		<category><![CDATA[windows 7]]></category>
		<category><![CDATA[windows server 2008]]></category>
		<category><![CDATA[windows server 2008 R2]]></category>

		<guid isPermaLink="false">http://blog.webactivedirectory.com/?p=1777</guid>
		<description><![CDATA[I recently worked on a Windows Server 2008 system with the Active Directory Management Gateway Service (ADMGS) installed. The ADMGS allows you to use the Active Directory module for Windows PowerShell to manage AD remotely in domains where there are no Server 2008 R2 domain controllers running. The ADMGS service (which runs as the Active [...]<img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=blog.webactivedirectory.com&amp;blog=10038206&amp;post=1777&amp;subd=webactivedirectory&amp;ref=&amp;feed=1" width="1" height="1" />]]></description>
		<wfw:commentRss>http://blog.webactivedirectory.com/2011/12/15/diagnose-active-directory-management-gateway-service-admgs-errors/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
	
		<media:content url="http://0.gravatar.com/avatar/e36fd0d4f4c557faea46d2b82b24e1d1?s=96&#38;d=identicon&#38;r=G" medium="image">
			<media:title type="html">jasonpcox21</media:title>
		</media:content>
	</item>
		<item>
		<title>Addressing the PowerShell Script Error for AuthorizationManager check failed</title>
		<link>http://blog.webactivedirectory.com/2011/10/21/addressing-the-powershell-script-error-for-authorizationmanager-check-failed/</link>
		<comments>http://blog.webactivedirectory.com/2011/10/21/addressing-the-powershell-script-error-for-authorizationmanager-check-failed/#comments</comments>
		<pubDate>Fri, 21 Oct 2011 15:00:44 +0000</pubDate>
		<dc:creator>Jason Cox</dc:creator>
				<category><![CDATA[Powershell]]></category>
		<category><![CDATA[Windows Server 2008]]></category>
		<category><![CDATA[Windows Server 2008 R2]]></category>
		<category><![CDATA[Security]]></category>
		<category><![CDATA[windows server 2008]]></category>
		<category><![CDATA[windows]]></category>
		<category><![CDATA[windows server 2008 R2]]></category>
		<category><![CDATA[windows server]]></category>
		<category><![CDATA[security]]></category>
		<category><![CDATA[internet explorer]]></category>
		<category><![CDATA[ie]]></category>
		<category><![CDATA[authorizationmanager]]></category>

		<guid isPermaLink="false">http://blog.webactivedirectory.com/?p=1737</guid>
		<description><![CDATA[I was recently working in a client environment and running a PowerShell script that calls a bunch of other scripts on the file system using the dot sourcing technique. The scripts run fine in a number of other customer environments as well as our test environment but I kept seeing an &#8220;AuthorizationManager check failed&#8221; when [...]<img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=blog.webactivedirectory.com&amp;blog=10038206&amp;post=1737&amp;subd=webactivedirectory&amp;ref=&amp;feed=1" width="1" height="1" />]]></description>
		<wfw:commentRss>http://blog.webactivedirectory.com/2011/10/21/addressing-the-powershell-script-error-for-authorizationmanager-check-failed/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
	
		<media:content url="http://0.gravatar.com/avatar/e36fd0d4f4c557faea46d2b82b24e1d1?s=96&#38;d=identicon&#38;r=G" medium="image">
			<media:title type="html">jasonpcox21</media:title>
		</media:content>

		<media:content url="http://webactivedirectory.files.wordpress.com/2011/10/unblockfile.png" medium="image">
			<media:title type="html">Windows File Properties - Unblock File</media:title>
		</media:content>
	</item>
		<item>
		<title>PowerShell Errors Connecting to Active Directory Domains and Forests</title>
		<link>http://blog.webactivedirectory.com/2011/10/13/powershell-errors-connecting-to-active-directory-domains-and-forests/</link>
		<comments>http://blog.webactivedirectory.com/2011/10/13/powershell-errors-connecting-to-active-directory-domains-and-forests/#comments</comments>
		<pubDate>Thu, 13 Oct 2011 15:00:23 +0000</pubDate>
		<dc:creator>Jason Cox</dc:creator>
				<category><![CDATA[Active Directory]]></category>
		<category><![CDATA[Microsoft Active Directory]]></category>
		<category><![CDATA[Powershell]]></category>
		<category><![CDATA[get-addomain]]></category>
		<category><![CDATA[new-psdrive]]></category>
		<category><![CDATA[server 2003]]></category>
		<category><![CDATA[server 2008]]></category>
		<category><![CDATA[windows server]]></category>
		<category><![CDATA[windows server 2008]]></category>
		<category><![CDATA[windows server 2008 R2]]></category>

		<guid isPermaLink="false">http://blog.webactivedirectory.com/?p=1731</guid>
		<description><![CDATA[I needed to work with data from a child domain in our test environment so I tried to access the child domain using the Get-ADDomain cmdlet from the Active Directory module for PowerShell. When that operation failed, I attempted to map a PS drive to the child domain instead, but this operation failed as well. [...]<img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=blog.webactivedirectory.com&amp;blog=10038206&amp;post=1731&amp;subd=webactivedirectory&amp;ref=&amp;feed=1" width="1" height="1" />]]></description>
		<wfw:commentRss>http://blog.webactivedirectory.com/2011/10/13/powershell-errors-connecting-to-active-directory-domains-and-forests/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
	
		<media:content url="http://0.gravatar.com/avatar/e36fd0d4f4c557faea46d2b82b24e1d1?s=96&#38;d=identicon&#38;r=G" medium="image">
			<media:title type="html">jasonpcox21</media:title>
		</media:content>
	</item>
		<item>
		<title>Routing PowerShell Command Results to the Write-Output Cmdlet</title>
		<link>http://blog.webactivedirectory.com/2011/10/06/routing-powershell-command-results-to-the-write-output-cmdlet/</link>
		<comments>http://blog.webactivedirectory.com/2011/10/06/routing-powershell-command-results-to-the-write-output-cmdlet/#comments</comments>
		<pubDate>Thu, 06 Oct 2011 19:01:06 +0000</pubDate>
		<dc:creator>Jason Cox</dc:creator>
				<category><![CDATA[Powershell]]></category>
		<category><![CDATA[cmdlet]]></category>
		<category><![CDATA[pwd]]></category>
		<category><![CDATA[write-output]]></category>

		<guid isPermaLink="false">http://blog.webactivedirectory.com/?p=1727</guid>
		<description><![CDATA[I am working on a project where we host a PowerShell runspace in IIS and I needed to dump some output from a command using the Write-Output cmdlet. I futzed around for a while trying to execute a command in the middle of the Write-Output parameter something like what follows. This is my attempt to [...]<img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=blog.webactivedirectory.com&amp;blog=10038206&amp;post=1727&amp;subd=webactivedirectory&amp;ref=&amp;feed=1" width="1" height="1" />]]></description>
		<wfw:commentRss>http://blog.webactivedirectory.com/2011/10/06/routing-powershell-command-results-to-the-write-output-cmdlet/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
	
		<media:content url="http://0.gravatar.com/avatar/e36fd0d4f4c557faea46d2b82b24e1d1?s=96&#38;d=identicon&#38;r=G" medium="image">
			<media:title type="html">jasonpcox21</media:title>
		</media:content>
	</item>
		<item>
		<title>Using the PowerShell Get-ADDomain cmdlet with an IIS Application Pool Identity</title>
		<link>http://blog.webactivedirectory.com/2011/08/10/using-the-powershell-get-addomain-cmdlet-with-an-iis-application-pool-identity/</link>
		<comments>http://blog.webactivedirectory.com/2011/08/10/using-the-powershell-get-addomain-cmdlet-with-an-iis-application-pool-identity/#comments</comments>
		<pubDate>Wed, 10 Aug 2011 15:00:41 +0000</pubDate>
		<dc:creator>Jason Cox</dc:creator>
				<category><![CDATA[.NET]]></category>
		<category><![CDATA[ASP.NET]]></category>
		<category><![CDATA[Development]]></category>
		<category><![CDATA[IIS]]></category>
		<category><![CDATA[Powershell]]></category>
		<category><![CDATA[application pool identity]]></category>

		<guid isPermaLink="false">http://blog.webactivedirectory.com/?p=1401</guid>
		<description><![CDATA[We use the PowerShell Active Directory module cmdlets for our applications and wanted to share a tip if you&#8217;re running the Get-ADDomain cmdlet using the default IIS application pool identity. Since this identity is actually a Windows Virtual Account, you cannot get to a domain using Get-ADDomain based on the application identity since there is no [...]<img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=blog.webactivedirectory.com&amp;blog=10038206&amp;post=1401&amp;subd=webactivedirectory&amp;ref=&amp;feed=1" width="1" height="1" />]]></description>
		<wfw:commentRss>http://blog.webactivedirectory.com/2011/08/10/using-the-powershell-get-addomain-cmdlet-with-an-iis-application-pool-identity/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
	
		<media:content url="http://0.gravatar.com/avatar/e36fd0d4f4c557faea46d2b82b24e1d1?s=96&#38;d=identicon&#38;r=G" medium="image">
			<media:title type="html">jasonpcox21</media:title>
		</media:content>
	</item>
		<item>
		<title>PowerShell Hosting in ASP.NET: Resolving Errors with PowerShell Set-ExecutionPolicy</title>
		<link>http://blog.webactivedirectory.com/2011/08/08/powershell-hosting-in-asp-net-resolving-errors-with-powershell-execution-policy/</link>
		<comments>http://blog.webactivedirectory.com/2011/08/08/powershell-hosting-in-asp-net-resolving-errors-with-powershell-execution-policy/#comments</comments>
		<pubDate>Mon, 08 Aug 2011 15:00:43 +0000</pubDate>
		<dc:creator>Jason Cox</dc:creator>
				<category><![CDATA[.NET]]></category>
		<category><![CDATA[ASP.NET]]></category>
		<category><![CDATA[IIS]]></category>
		<category><![CDATA[Powershell]]></category>
		<category><![CDATA[Windows 7]]></category>
		<category><![CDATA[Windows Server 2008]]></category>
		<category><![CDATA[Windows Server 2008 R2]]></category>
		<category><![CDATA[.net]]></category>
		<category><![CDATA[asp.net]]></category>
		<category><![CDATA[errors]]></category>

		<guid isPermaLink="false">http://blog.webactivedirectory.com/?p=1388</guid>
		<description><![CDATA[One of the great innovations in Windows PowerShell is the ability to host the PowerShell run-time environment in any number of run-time hosts. We use this capability to host PowerShell in an ASP.NET web application process for our PeopleProvision solution. Everything works great once you get over a couple of big security hurdles. File SomePowerShellFile.ps1 [...]<img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=blog.webactivedirectory.com&amp;blog=10038206&amp;post=1388&amp;subd=webactivedirectory&amp;ref=&amp;feed=1" width="1" height="1" />]]></description>
		<wfw:commentRss>http://blog.webactivedirectory.com/2011/08/08/powershell-hosting-in-asp-net-resolving-errors-with-powershell-execution-policy/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
	
		<media:content url="http://0.gravatar.com/avatar/e36fd0d4f4c557faea46d2b82b24e1d1?s=96&#38;d=identicon&#38;r=G" medium="image">
			<media:title type="html">jasonpcox21</media:title>
		</media:content>
	</item>
		<item>
		<title>Active Directory Provisioning with PowerShell: Extensibility and Power without Costly Implementation (Part 3 of 4)</title>
		<link>http://blog.webactivedirectory.com/2011/08/04/active-directory-provisioning-with-powershell-extensibility-and-power-without-costly-implementation-part-3-of-4/</link>
		<comments>http://blog.webactivedirectory.com/2011/08/04/active-directory-provisioning-with-powershell-extensibility-and-power-without-costly-implementation-part-3-of-4/#comments</comments>
		<pubDate>Thu, 04 Aug 2011 19:25:45 +0000</pubDate>
		<dc:creator>Jason Cox</dc:creator>
				<category><![CDATA[Active Directory]]></category>
		<category><![CDATA[Active Directory Users and Computers (ADUC)]]></category>
		<category><![CDATA[Business Philosophy]]></category>
		<category><![CDATA[Exchange]]></category>
		<category><![CDATA[Microsoft Active Directory]]></category>
		<category><![CDATA[PeopleProvision]]></category>
		<category><![CDATA[Powershell]]></category>
		<category><![CDATA[SQL Server]]></category>
		<category><![CDATA[User Experience]]></category>
		<category><![CDATA[Windows Server 2008 R2]]></category>
		<category><![CDATA[Active Directory Users and Computers]]></category>

		<guid isPermaLink="false">http://blog.webactivedirectory.com/?p=1350</guid>
		<description><![CDATA[This is Part 3 of Web Active Directory&#8217;s blog post series highlighting our new PowerShell-enabled platform. We introduced the series with an exam of how other software vendors approach provisioning with costly implementation services and then looked at WebAD&#8217;s PeopleProvision solution more closely. In this post, we look at how easy it is to implement [...]<img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=blog.webactivedirectory.com&amp;blog=10038206&amp;post=1350&amp;subd=webactivedirectory&amp;ref=&amp;feed=1" width="1" height="1" />]]></description>
		<wfw:commentRss>http://blog.webactivedirectory.com/2011/08/04/active-directory-provisioning-with-powershell-extensibility-and-power-without-costly-implementation-part-3-of-4/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
	
		<media:content url="http://0.gravatar.com/avatar/e36fd0d4f4c557faea46d2b82b24e1d1?s=96&#38;d=identicon&#38;r=G" medium="image">
			<media:title type="html">jasonpcox21</media:title>
		</media:content>
	</item>
		<item>
		<title>Active Directory Provisioning with PowerShell: Extensibility and Power without Costly Implementation (Part 2 of 4)</title>
		<link>http://blog.webactivedirectory.com/2011/08/03/active-directory-provisioning-with-powershell-extensibility-and-power-without-costly-implementation-part-2-of-4/</link>
		<comments>http://blog.webactivedirectory.com/2011/08/03/active-directory-provisioning-with-powershell-extensibility-and-power-without-costly-implementation-part-2-of-4/#comments</comments>
		<pubDate>Wed, 03 Aug 2011 15:00:10 +0000</pubDate>
		<dc:creator>Jason Cox</dc:creator>
				<category><![CDATA[.NET]]></category>
		<category><![CDATA[Active Directory]]></category>
		<category><![CDATA[Active Directory Users and Computers (ADUC)]]></category>
		<category><![CDATA[Business Philosophy]]></category>
		<category><![CDATA[Exchange]]></category>
		<category><![CDATA[Microsoft Active Directory]]></category>
		<category><![CDATA[PeopleProvision]]></category>
		<category><![CDATA[Powershell]]></category>
		<category><![CDATA[SQL 2008]]></category>
		<category><![CDATA[SQL Server]]></category>
		<category><![CDATA[User Experience]]></category>
		<category><![CDATA[Windows Server 2008 R2]]></category>
		<category><![CDATA[Active Directory Users and Computers]]></category>

		<guid isPermaLink="false">http://blog.webactivedirectory.com/?p=1348</guid>
		<description><![CDATA[We are taking a look at Web Active Directory&#8217;s new PowerShell-enabled platform this week in a series of blog posts. We introduced the series by discussing how many software companies like to squeeze every red cent from their customers by using proprietary technologies that require costly implementation services. This post introduces WebAD&#8217;s PeopleProvision tool to [...]<img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=blog.webactivedirectory.com&amp;blog=10038206&amp;post=1348&amp;subd=webactivedirectory&amp;ref=&amp;feed=1" width="1" height="1" />]]></description>
		<wfw:commentRss>http://blog.webactivedirectory.com/2011/08/03/active-directory-provisioning-with-powershell-extensibility-and-power-without-costly-implementation-part-2-of-4/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
	
		<media:content url="http://0.gravatar.com/avatar/e36fd0d4f4c557faea46d2b82b24e1d1?s=96&#38;d=identicon&#38;r=G" medium="image">
			<media:title type="html">jasonpcox21</media:title>
		</media:content>

		<media:content url="http://webactivedirectory.files.wordpress.com/2011/08/ppro_v1_0_createuserscreen.png" medium="image">
			<media:title type="html">Simple Design Philosophy for PeopleProvision v1.0</media:title>
		</media:content>
	</item>
		<item>
		<title>Active Directory Provisioning with PowerShell: Extensibility and Power without Costly Implementation (Part 1 of 4)</title>
		<link>http://blog.webactivedirectory.com/2011/08/02/active-directory-provisioning-based-on-powershell-extensibility-without-costly-implementation/</link>
		<comments>http://blog.webactivedirectory.com/2011/08/02/active-directory-provisioning-based-on-powershell-extensibility-without-costly-implementation/#comments</comments>
		<pubDate>Tue, 02 Aug 2011 15:00:09 +0000</pubDate>
		<dc:creator>Opus55</dc:creator>
				<category><![CDATA[Active Directory]]></category>
		<category><![CDATA[Exchange]]></category>
		<category><![CDATA[Microsoft]]></category>
		<category><![CDATA[Microsoft Active Directory]]></category>
		<category><![CDATA[PeopleProvision]]></category>
		<category><![CDATA[Powershell]]></category>
		<category><![CDATA[active directory self service]]></category>
		<category><![CDATA[Active Directory Users and Computers]]></category>
		<category><![CDATA[AD]]></category>
		<category><![CDATA[ADUC]]></category>
		<category><![CDATA[development]]></category>
		<category><![CDATA[exchange mailbox]]></category>
		<category><![CDATA[micorsoft powershell]]></category>
		<category><![CDATA[microsoft exchange]]></category>
		<category><![CDATA[update active directory]]></category>
		<category><![CDATA[web active directory]]></category>

		<guid isPermaLink="false">http://blog.webactivedirectory.com/?p=1318</guid>
		<description><![CDATA[Too often, software companies want absolute control of their black box of intellectual property (IP). These companies only want extensibility and customizability if it means more revenue from implementation services. A few companies in our space have even developed their own scripting languages to make customers pay for more services or training to learn yet [...]<img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=blog.webactivedirectory.com&amp;blog=10038206&amp;post=1318&amp;subd=webactivedirectory&amp;ref=&amp;feed=1" width="1" height="1" />]]></description>
		<wfw:commentRss>http://blog.webactivedirectory.com/2011/08/02/active-directory-provisioning-based-on-powershell-extensibility-without-costly-implementation/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
	
		<media:content url="http://1.gravatar.com/avatar/3d94c1cfb1f73431df7aa8018aaad15f?s=96&#38;d=identicon&#38;r=G" medium="image">
			<media:title type="html">Opus55</media:title>
		</media:content>
	</item>
	</channel>
</rss>
