By Euricom on 12/18/2009 11:44 AM

 Although setting up the My Sites web sites is described in this TechNet article, there are a couple of things you will need to take care of to get the complete My Sites functionality working, especially if you don't want to use the default settings.

First of, where do you find the place to enter the settings?

On the start page of the Central Administration you will find a link to "Manage service applications" under the "Application Management" header. In the list of service applications, choose "User Profile Service Application".

This will bring you to a page where there is a paragraph "My Site Settings". Most of the things you have to do, will be located in this paragraph, though not everything.

A good first step is to check out the default settings. So choose "Setup My Sites" and see what is alreay in there. The three most important things here are:

• My Site Host

• Personal Site Location

• Site Naming Format

For us to run through the complete workflow, let's say these settings are not to your liking and you want to change them. What steps do we need to take to change the entire setup.

 

By Ronny Gabriels, SharePoint Team Leader, Euricom

Read More »

By Euricom on 12/18/2009 10:49 AM

 Last week we had a strange thing happen to one of our customers. While trying to activate one of our custom features containing some webparts, the person got an "Access Denied" error message. This is certainly not surprising until we found that this person was a Site Collection admin and therefore an admin for the site he was trying to activate the feature in. 

After some intensive search to found out what the problem was, we found that it was in fact a user permission that was turned of for the web application that was the problem. With this permission turned of the Site Collection admin (or any other person with enough permissions on the site to activate features) wasn't able to activate any features containing webparts. Even standard MOSS features like SharePoint Search features were affected. Features not containing webparts where no problem however. 

The fact that a user permission for the web application prohibits this is on its own not that surprising, but the permission is called "Create Subsites" and that has, in our eyes at least, nothing to do with activating features.  

Read More »