Tag Info

New answers tagged

1

You need to have the dll deployed to: C:\Program Files\Common Files\microsoft shared\Web Server Extensions\15\BIN if you want the timerjob to be able to use it.


1

I am not sure is there any direct ways to find this information. Timer Jobs are normally created through a Feature Receiver. This receivers are embedded inside assemblies, which is deployed into GAC. So first find out all features which has a feature assembly Get-SPFeature | Where-Object { $_.ReceiverClass -ne "" } Now look the ReceiverClass and see any ...


1

You should login with different account other than System Account. System Account is not allowed to run workflows for security purposes. Read more about why it is blocked. http://blogs.technet.com/b/victorbutuza/archive/2009/03/14/workflows-do-not-start.aspx


0

There is a User Profile Change log that is maintained for 14 days by default. You can query it and determine what changed and even if your property of interest changed. In PowerShell you could get a service context and then do something like: $manager = New-Object Microsoft.Office.Server.UserProfiles.UserProfileManager $context Then use one of the ...


0

As per my knowledge there is no event associated with User Profiles. Hence there is no way we can define an event receiver. As you suggested you need a timer service and then loop through the profile change log. Then take a decision based on that.



Top 50 recent answers are included