<?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>Dom Cosgrove Blog &#187; Administration</title>
	<atom:link href="http://blog.domcosgrove.com/tag/administration/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.domcosgrove.com</link>
	<description>Dom&#039;s views on the SharePoint World</description>
	<lastBuildDate>Wed, 17 Mar 2010 11:53:39 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>How to perform a phased roll out of SharePoint MySites</title>
		<link>http://blog.domcosgrove.com/how-to-perform-a-phased-roll-out-of-sharepoint-mysites/</link>
		<comments>http://blog.domcosgrove.com/how-to-perform-a-phased-roll-out-of-sharepoint-mysites/#comments</comments>
		<pubDate>Sun, 15 Nov 2009 09:33:00 +0000</pubDate>
		<dc:creator>Dominick Cosgrove</dc:creator>
				<category><![CDATA[Administration]]></category>
		<category><![CDATA[SharePoint]]></category>

		<guid isPermaLink="false">http://blog.domcosgrove.com/how-to-perform-a-phased-roll-out-of-sharepoint-mysites/</guid>
		<description><![CDATA[While working at an large utility organisation that has an Enterprise deployment of MOSS; they had their MySite Functionality turned off for all users. Now while I agree that there is a considerable amount of resource required to implement and manage the MySite functionality in SharePoint, it does have it’s benefits:

Aids SharePoint adoption as uses [...]]]></description>
			<content:encoded><![CDATA[<p align="justify">While working at an large utility organisation that has an Enterprise deployment of MOSS; they had their MySite Functionality turned off for all users. Now while I agree that there is a considerable amount of resource required to implement and manage the MySite functionality in SharePoint, it does have it’s benefits:</p>
<ul>
<li>Aids SharePoint adoption as uses have <em>Site Owner</em> rights to their MySite, which means they can create Lists, Add Web Parts, Upload Documents e.t.c. giving them a full flavour of what SharePoint can do, in an isolated environment; </li>
<li>It can replace the user drive (U:\ drive or equivalent); </li>
<li>It can promote Sharing of information with colleges, rather than having silos of information on Shared Drives; </li>
<li>It can allow you to target information to particular sets of users; </li>
<li>
<div align="justify">It helps finding people by skills, roles, department, corporate structure e.t.c.</div>
</li>
</ul>
<ul>
<p align="justify">One approach I find useful is to phase / incrementally deployment of MySites across the Enterprise. The following will show how you can achieve this:</p>
<p>   <strong>1. </strong>Within the Active Directory (AD) create a new group called “<em>SharePoint MySite Users”</em> or something similar, this should be created as per your corporate policy;     </ul>
<p align="justify"><a href="http://blog.domcosgrove.com/wp-content/uploads/2009/11/image1.png"><img style="border-right-width: 0px; display: inline; border-top-width: 0px; border-bottom-width: 0px; border-left-width: 0px" title="image" border="0" alt="image" src="http://blog.domcosgrove.com/wp-content/uploads/2009/11/image_thumb1.png" width="400" height="395" /></a> </p>
<p> <strong>2. </strong>Add the users that you plan to initially grant access to MySites to the newly created Group. You can also add existing AD Groups to this groups; for instance if you wanted to add the IT department you could add a AD Group that contains all members of that Department;   </p>
<p align="justify"><a href="http://blog.domcosgrove.com/wp-content/uploads/2009/11/image2.png"><img style="border-right-width: 0px; display: inline; border-top-width: 0px; border-bottom-width: 0px; border-left-width: 0px" title="image" border="0" alt="image" src="http://blog.domcosgrove.com/wp-content/uploads/2009/11/image_thumb2.png" width="400" height="273" /></a> </p>
<p align="justify"><strong>3. </strong>Launch your <strong>Central Administration</strong> console and select the <strong>Shared Services</strong> associated the SharePoint Site. From the Shared Services Home page select <strong>Personalization services permissions;</strong></p>
<p align="justify"><a href="http://blog.domcosgrove.com/wp-content/uploads/2009/11/image3.png"><img style="border-right-width: 0px; display: inline; border-top-width: 0px; border-bottom-width: 0px; border-left-width: 0px" title="image" border="0" alt="image" src="http://blog.domcosgrove.com/wp-content/uploads/2009/11/image_thumb3.png" width="400" height="268" /></a> </p>
<p align="justify"><strong>4. </strong>This will launch the a permissions page where you can grant rights to various personalisation services. You will notice that by default the <strong>NT AUTHORITY\Authenticated Users</strong> have been granted <strong>Personal Features</strong> and <strong>Personal Site</strong> rights. We are interested in the <em>Personal Site</em> rights. We need to remove these rights from the Authenticated Users groups<em>. </em>To do this select the Authenticated Users, and click <strong>Modify Permissions of Selected Users</strong>;</p>
<p align="justify"><a href="http://blog.domcosgrove.com/wp-content/uploads/2009/11/image4.png"><img style="border-right-width: 0px; display: inline; border-top-width: 0px; border-bottom-width: 0px; border-left-width: 0px" title="image" border="0" alt="image" src="http://blog.domcosgrove.com/wp-content/uploads/2009/11/image_thumb4.png" width="400" height="104" /></a> </p>
<p align="justify"><strong>5. </strong>On the <strong>Modify Permissions </strong>page deselect <strong>Create Personal Site</strong> and click <strong>Save;</strong></p>
<p align="justify"><a href="http://blog.domcosgrove.com/wp-content/uploads/2009/11/image5.png"><img style="border-right-width: 0px; display: inline; border-top-width: 0px; border-bottom-width: 0px; border-left-width: 0px" title="image" border="0" alt="image" src="http://blog.domcosgrove.com/wp-content/uploads/2009/11/image_thumb5.png" width="400" height="161" /></a> </p>
<p align="justify"><strong>6.</strong> From the <strong>Manage Permissions</strong> page select <strong>Add Users / Groups</strong>. On the <strong>Add Users / Groups</strong> page enter the group that you created in steps 1 &amp; 2. You can use the people picker functionality to help find the group. Check the box next to <strong>Create Personal Site</strong> and click <strong>Save</strong>;</p>
<p align="justify"><a href="http://blog.domcosgrove.com/wp-content/uploads/2009/11/image6.png"><img style="border-right-width: 0px; display: inline; border-top-width: 0px; border-bottom-width: 0px; border-left-width: 0px" title="image" border="0" alt="image" src="http://blog.domcosgrove.com/wp-content/uploads/2009/11/image_thumb6.png" width="400" height="163" /></a> </p>
<p align="justify"><strong>7.</strong> You will now see that the <strong>SharePoint MySite Users</strong> group has the rights to create personal sites;</p>
<p align="justify"><a href="http://blog.domcosgrove.com/wp-content/uploads/2009/11/image7.png"><img style="border-right-width: 0px; display: inline; border-top-width: 0px; border-bottom-width: 0px; border-left-width: 0px" title="image" border="0" alt="image" src="http://blog.domcosgrove.com/wp-content/uploads/2009/11/image_thumb7.png" width="400" height="113" /></a></p>
<p align="justify"><strong>8. </strong>To verify this log in to the Portal with an account that is a member of the <strong>SharePoint MySite Users</strong> group. You will see the link to the <strong>My Site</strong> in the top right corner of the standard SharePoint site template;</p>
<p align="justify"><a href="http://blog.domcosgrove.com/wp-content/uploads/2009/11/image8.png"><img style="border-right-width: 0px; display: inline; border-top-width: 0px; border-bottom-width: 0px; border-left-width: 0px" title="image" border="0" alt="image" src="http://blog.domcosgrove.com/wp-content/uploads/2009/11/image_thumb8.png" width="300" height="80" /></a></p>
<p align="justify"><strong>9.</strong> Now log in with a user who is not a member and you will notice that the <strong>My Site</strong> link no longer appears;</p>
<p align="justify"><a href="http://blog.domcosgrove.com/wp-content/uploads/2009/11/image9.png"><img style="border-right-width: 0px; display: inline; border-top-width: 0px; border-bottom-width: 0px; border-left-width: 0px" title="image" border="0" alt="image" src="http://blog.domcosgrove.com/wp-content/uploads/2009/11/image_thumb9.png" width="300" height="74" /></a> </p>
<p>Using this approach you can safely deploy My Sites functionality across and enterprise in a controlled fashion. This will allow you to ensure quota’s, content database, site deletion e.t.c are provisioned as per the requirements (governance) of your organisation.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.domcosgrove.com/how-to-perform-a-phased-roll-out-of-sharepoint-mysites/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
