http://technet.microsoft.com/en-us/sharepoint/ff800847

If you want to be alerted or aware of updates then you can subscribe to the SharePoint Team Blog.

• Aids SharePoint adoption as uses have Site Owner 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;
• It can replace the user drive (U:\ drive or equivalent);
• It can promote Sharing of information with colleges, rather than having silos of information on Shared Drives;
• It can allow you to target information to particular sets of users;
• It helps finding people by skills, roles, department, corporate structure e.t.c.

One approach I find useful is to phase / incrementally deployment of MySites across the Enterprise. The following will show how you can achieve this:

1. Within the Active Directory (AD) create a new group called “SharePoint MySite Users” or something similar, this should be created as per your corporate policy;

2. 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;

3. Launch your Central Administration console and select the Shared Services associated the SharePoint Site. From the Shared Services Home page select Personalization services permissions;

4. This will launch the a permissions page where you can grant rights to various personalisation services. You will notice that by default the NT AUTHORITY\Authenticated Users have been granted Personal Features and Personal Site rights. We are interested in the Personal Site rights. We need to remove these rights from the Authenticated Users groups. To do this select the Authenticated Users, and click Modify Permissions of Selected Users;

5. On the Modify Permissions page deselect Create Personal Site and click Save;

6. From the Manage Permissions page select Add Users / Groups. On the Add Users / Groups page enter the group that you created in steps 1 & 2. You can use the people picker functionality to help find the group. Check the box next to Create Personal Site and click Save;

7. You will now see that the SharePoint MySite Users group has the rights to create personal sites;

8. To verify this log in to the Portal with an account that is a member of the SharePoint MySite Users group. You will see the link to the My Site in the top right corner of the standard SharePoint site template;

9. Now log in with a user who is not a member and you will notice that the My Site link no longer appears;

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.

A free book called Mastering PowerShell is available to download here:

http://powershell.com/Mastering-PowerShell.pdf

IISreset.exe is a magical command that resolves many problems! Err… well, yeah that command restarts all IIS related processes and thus essentially running it cleans up all the “mess”. So is there anything special about IISReset.exe in Windows 2008? Yes and I do not recommend using it and here’s very useful information that you must know about what this command does.

Windows 2008 introduced a new service called Windows Process Activation service aka WAS. In IIS 7.0 you can run HTTP and non HTTP services (like net.tcp) in the same application pool. WAS manages application pools and worker processes for HTTP and non HTTP protocols. IIS uses the HTTP protocol with WAS. With WAS we opened it up for others to use our process model. The IIS process model is very efficient and I believe we made this change due to good feedback.

Back to IISERSET…. IISReset.exe restarts the following Windows Services

• IISADMIN
• W3SVC
• WAS

So do you see what would happen if your ran IISReset.exe with the intention to restart ONLY IIS, but you also have other services dependent via WAS?

Conclusion: Running IISReset.exe will restart WAS and restarting WAS will restart all services that are dependent on it, including IIS, if installed. This can be problematic in production environments where you have non HTTP services implemented with WAS but your intention is to only restart IIS. An example to this will be with Small Business Server.

Therefore, the recommended way to restart IIS on Windows 2008 machines will be to use one of the following methods:

• Open IIS Manager and then select the server node. In the right side pane, you will have an option to restart IIS.
• Open a command prompt as Administrator and run the following commands

1. net stop w3svc
2. net stop IISAdmin
3. net start IISAdmin
4. net start w3svc