Vighnesh Bendre - MS technologies

[Modified:11 Oct 2010] Now you can find the source code for this example in CodePlex The out-of-the-box SharePoint people picker allows users to select users, SharePoint groups, Distribution Lists & Security groups . Users may accidentally add large AD groups to SharePoint groups and send notifications to hundreds of people. The administrator may want more control over the security of the people picker control. In some scenario the administrator may want to restrict the user to only select ‘users’ or ‘SharePoint Groups’. This can be achieved by creating a custom people picker control which inherits from SharePoint people editor. In below example, we are going to explore creation of custom people picker control, replace the OOTB people editor control, provide a people picker settings page in central administration and create menu to access the settings page in Central Administration. 1. Create custom people picker For creating a custom control (which inherits from SharePoint PeopleE...

Error: From: Manage Profile Service Where: Application Management->Manage Service Applications->User Profile Service Application->Manage->Start Profile Synchronization Can not navigate to the requested page while User Profile Synchronization is running. Please wait for the current Synchronization run to finish. From: Manage Services on Server- User Profile Synchronization Service Where: Application Management->Manage Services on Server->User Profile Synchronization Service->Start Below error is thrown in the event viewer. Solution: It seems that the service account used for running the ‘User Profile Synchronization Service’ is not part of local administrator. I read in other blogs that this service tries to access HKLM\SYSTEM\CurrentControlSet\Services\FIMSynchronizationService\Parameters registry key. So adding this service account to local administrator group in ‘Server Manager’ would solve the problem. -Vighnesh Bendre

Hi all, While I was working on SharePoint 2010 recently I came across some issues. I am putting them across so that anyone facing the same issue may find solution easily. Error: Error occurred in deployment step 'Activate Features': Feature with Id xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx' is not installed in this farm, and cannot be added to this scope. Solutions: I was getting this error while ‘deploy’ing a feature from Visual Studio 2010. I searched the entire project for this GUID which is mentioned in the error. I did not find it anywhere. While troubleshooting, I opened the physical folder and opened ‘Feature1.feature’ file in notepad. This xml file was using the before mentioned GUID. I was not able to find it in VS 2010 :( I copied the GUID mentioned in the ‘Feature1.feature’ file and pasted it in the Feature ID section in ‘Feature1.Template.xml’ file. This solved the problem. Why I thought to mention it is because the exception thrown is confusing. It does not tell you...