Tag Info

Hot answers tagged

2

This is just an expansion of @aveenavs answer, which works great for me, unless the user is on the root site of the application. The only difference is using _spPageContextInfo.webAbsoluteUrl instead of _spPageContextInfo.webServerRelativeUrl in the url in the ajax call. So I would change it to this: //Get user's personal MySite url ...


2

I would recommend using a query against the change log. The "Event Receiver" really isn't it's just a timer job using the same approach detailed in the article. You could even run it all external to SharePoint from PowerShell if you wanted. No need to deploy custom code to SharePoint.


2

You can disable the timer job responsible for sending mail for MySite Suggestions Email job. From Central Administration, click Monitoring Under the Timer Jobs heading, click Review job definitions Scroll down (or click through pages) until you find a job called User Profile Service - User Profile My Site Suggestions Email Job


1

Yes, it should work. Personally, I don't use the syntax $userProfile["$property"], instead without the quotes like $userProfile[$property], but it should not make a difference, AFAIK. What I don't see in your code, where the $userProfile variable in the Update-UserProfileProperty method was defined. What is the type of your custom property? String / date / ...


1

The User Profile Synchronization Service must be provisioned by the farm account. So if you run your Powershell script using another account (the setup account typically), it will fail. The solution is either: 1) To run your Powershell script using the farm account. Try shift+right click on Powershell shortcut -> "run as another user"; or directly log in ...



Only top voted, non community-wiki answers of a minimum length are eligible