<?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>Ulysses Ludwig&#039;s SharePoint blog &#187; PowerShell</title>
	<atom:link href="http://www.sharepointassist.com/category/powershell/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.sharepointassist.com</link>
	<description>How I do it...</description>
	<lastBuildDate>Sun, 06 Nov 2011 03:25:01 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3</generator>
		<item>
		<title>Creating one Content Database Per Site Collection In SharePoint 2010 using Windows PowerShell</title>
		<link>http://www.sharepointassist.com/2011/02/19/creating-one-content-database-per-site-collection-in-sharepoint-2010-using-windows-powershell/</link>
		<comments>http://www.sharepointassist.com/2011/02/19/creating-one-content-database-per-site-collection-in-sharepoint-2010-using-windows-powershell/#comments</comments>
		<pubDate>Sat, 19 Feb 2011 18:40:40 +0000</pubDate>
		<dc:creator>ujludwig</dc:creator>
				<category><![CDATA[2010]]></category>
		<category><![CDATA[PowerShell]]></category>
		<category><![CDATA[SharePoint]]></category>
		<category><![CDATA[SharePoint 2010]]></category>
		<category><![CDATA[SharePoint 2010 PowerShell]]></category>
		<category><![CDATA[Site Collections]]></category>

		<guid isPermaLink="false">http://www.sharepointassist.com/2011/02/19/creating-one-content-database-per-site-collection-in-sharepoint-2010-using-windows-powershell/</guid>
		<description><![CDATA[One of the most common problems I see in a client built SharePoint environment is multiple site collections comingled in the same content database.&#160; While this isn’t the end of the world, it’s a problem because SLAs, security, and even back strategies are often assigned to specific databases based upon the needs of the users [...]]]></description>
		<wfw:commentRss>http://www.sharepointassist.com/2011/02/19/creating-one-content-database-per-site-collection-in-sharepoint-2010-using-windows-powershell/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>Unable to Move Sites Due to the &#8220;Drop Off Library&#8221;</title>
		<link>http://www.sharepointassist.com/2010/12/03/unable-to-move-sites-due-to-the-drop-off-library/</link>
		<comments>http://www.sharepointassist.com/2010/12/03/unable-to-move-sites-due-to-the-drop-off-library/#comments</comments>
		<pubDate>Fri, 03 Dec 2010 23:42:20 +0000</pubDate>
		<dc:creator>ujludwig</dc:creator>
				<category><![CDATA[2010]]></category>
		<category><![CDATA[PowerShell]]></category>
		<category><![CDATA[SharePoint 2010]]></category>
		<category><![CDATA[PowerShell; SharePoint 2010; Content Organizer]]></category>

		<guid isPermaLink="false">http://www.sharepointassist.com/2010/12/03/unable-to-move-sites-due-to-the-drop-off-library/</guid>
		<description><![CDATA[I have a client who could no longer moves sites using the SharePoint content organizer due to the fact that the enterprise features were enabled, with the enterprise features enabled on all sites, the Drop Off Library prevents sites from being moved.  Unfortunately, simply disabling the Content Organizer feature does not correct the problem, you [...]]]></description>
		<wfw:commentRss>http://www.sharepointassist.com/2010/12/03/unable-to-move-sites-due-to-the-drop-off-library/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>The local farm is not accessible. Cmdlets with FeatureDependencyId are not registered</title>
		<link>http://www.sharepointassist.com/2010/01/29/the-local-farm-is-not-accessible-cmdlets-with-featuredependencyid-are-not-registered/</link>
		<comments>http://www.sharepointassist.com/2010/01/29/the-local-farm-is-not-accessible-cmdlets-with-featuredependencyid-are-not-registered/#comments</comments>
		<pubDate>Fri, 29 Jan 2010 23:20:14 +0000</pubDate>
		<dc:creator>ujludwig</dc:creator>
				<category><![CDATA[2010]]></category>
		<category><![CDATA[PowerShell]]></category>
		<category><![CDATA[SharePoint]]></category>
		<category><![CDATA[Backup & Restore]]></category>
		<category><![CDATA[SharePoint 2010]]></category>

		<guid isPermaLink="false">http://www.sharepointassist.com/2010/01/29/the-local-farm-is-not-accessible-cmdlets-with-featuredependencyid-are-not-registered/</guid>
		<description><![CDATA[Problem When you run powershell on your server you get the following error: The local farm is not accessible. Cmdlets with FeatureDependencyId are not registered. &#160; Solution Make sure the logged in user has rights to the SharePoint_Configuration database SharePoint_Shell_Access DB_owner (try reducing the privileges after you get it working in order to support “least [...]]]></description>
		<wfw:commentRss>http://www.sharepointassist.com/2010/01/29/the-local-farm-is-not-accessible-cmdlets-with-featuredependencyid-are-not-registered/feed/</wfw:commentRss>
		<slash:comments>6</slash:comments>
		</item>
	</channel>
</rss>

