Tag Info

Hot answers tagged

9

Gary Lapointe and Mathew McDermott recently published an article on this topic in SharePointPro magazine. It is available online here: http://www.sharepointpromag.com/article/sharepoint/monitor-sharepoint-user-profile-changes-129846 Synopsis of the article: First you enable logging via the STSADM tool (no PS available for this) stsadm -o ...


7

This is a pretty old thread so you've probably already figured this out but for the sake of helping to close it out, here's one way you could solve the problem (there are others): $profiles | ForEach-Object { $vals = $_.GetEnumerator(); $hash = @{}; foreach ($val in $vals) { $hash[$val.Key] = $val.Value } New-Object PSObject ...


7

The function below will get you the UserProfile based on the accountName public static UserProfile GetUserInfo(string AccountName) { UserProfile profile = null; SPServiceContext serviceContext = SPServiceContext.Current; UserProfileManager profileManager = new UserProfileManager(serviceContext); if (AccountName != string.Empty) { ...


6

It is not possible to add event handlers to the user info list. Please see this following thread: http://social.msdn.microsoft.com/Forums/en-US/sharepointdevelopment/thread/81aae5ef-9621-48c5-ad52-706e5d6a0f05 That was me asking the question.


6

You can try this if I understand you correct? Microsoft.SharePoint.SPContext.Current.Web.CurrentUser.LoginName; or HttpContext.Current.User.Identity.Name and Microsoft.SharePoint.SPContext.Current.Web.CurrentUser.ID; hope this helps :)


5

Theres not much stuff out there regarding User Profile upgrade yet, but technet dont report any specific considerations beside if you use choice lists, you should remap these later to Managed Metadata Service tags if you choose in-place upgrade and if you use db attach (recommended) you should create MMS before so it can be mapped during upgrade. Remember ...


5

This will give you all profiles, without restrictions: var serviceContext = SPServiceContext.GetContext(site); var userProfileManager = new UserProfileManager(serviceContext); foreach (UserProfile userProfile in userProfileManager) { // ... } This operation in itself is not super costly, but retrieving individual user profile properties can be. ...


5

It is not possible to configure the user profile synchronization service to import users from other sources than the built in synchronization sources (AD DS, Novell, Tivoli....) I dont think it is possible to write your own synchronization connection - there are absolutely no documentation, and after having poked around i reflector for days i found no where ...


5

SPUtility.ResolvePrincipal can do this - but I can't guarantee that it'll be fast. It should be something like: SPPrincipcalInfo user = SPUtility.ResolvePrincipal( webApp, null, "email", SPPrincipalType.User, SPPrincipalSource.Windows, true); UserProfileManager profileManager = new UserProfileManager(serviceContext); if ...


5

Browse to the User Profile service application and select the manage user properties link. From here, find the mobile number field and select the edit item from the item context menu. Once in there, scroll down to the Display Settings section and check the "Show on the Edit Details page" option. You may also want to check the "Show in the profile ...


5

Here is simple code example to get you started: Add-PSSnapin Microsoft.SharePoint.PowerShell $siteUrl = "http://mycoolsite/" $accountName = "MyAccountName" $site = Get-SPSite $siteUrl $context = Get-SPServiceContext($site) $pm = new-object Microsoft.Office.Server.UserProfiles.UserProfileManager($context) # If user profile doesn't exist create new one ...


5

Finally I figured it out. UserProfileManager internally checks HttpContext.Current.User to determine if current user can view property value. The trick is to replace context and user (if HttpContext.Current.User is null, null reference thrown in UserProfileManager constructor, so this is required). The final code looks like this one: ...


5

Have you enabled "replicable" on the field properties? If this isnt enabled, the properties are not propagated to the hidden user list Edit: if you look at this post, it seems that not all user profile types are propagated. Change one of the properties to TEXT just to test if this is the cause of this.


4

If you are using regular WSS then you would need to go to the User Information list (Site Actions, Site Settings, People and Groups, All People), select the user and edit their display name. You would need to do this on each Site Collection since there is no centralized profile. If you are using a version of MOSS you have the ability to change go into the ...


4

Contrary to the accepted answer, there's a number of ways to accomplish this using out-of-the-box SharePoint 2010 features. You can allow certain users permissions to manage any user profile in the system by granting them Manage Profiles permissions in Central Admin. You can find more info on TechNet: Assign administration of User Profile service features ...


4

To set the Manage Profiles permissions do as follows: Go to Central Admin Choose Application Management > Manage Service Applicatrions Select the User Profile Service Application (do not click the link) Click Administrators in the ribbon Add the user and set the Manage Profiles permission for it Click OK Your done!


4

I think in the case of the User Profile Service Application databases the recommendation is to replicate, rather than propagate these between farms. I don't think you can attach a User Profile database from one farm to another. If your user profile data is mainly coming from Active Directory I would suggest you just re-import the AD profiles in the other ...


4

If you look in your web.config you'll see which FBA SQL database is being used. This is a standard SQL Database that you can Query from using any SQL tool, Including Excel.


4

I think it is a known side effect when installing June CU. You can either uninstall .Net 4.0 or force FIM to use .Net Framework v2.0 It is explained here in detail: http://blogs.technet.com/b/patrick_heyde/archive/2011/07/02/sharepoint-2010-junecu-2011-available-side-effect-info-amp-solution.aspx


4

Take a look at Property Class There are two types of user profile properties: Regular - Defines the property data type and the corresponding user profile flags. Section - Property that serves as a separator for user interface grouping purposes. In order to move properties 'into' section you just need to reorder them. I am providing a ...


4

I had the same issue. But I solved it as Toni Frankola said. May be you did wrong steps to add permissions to the user profile service. Look at this post to be sure that you added these permissions correctly.


4

Considering the fact that there could be lots of users in Active Directory, I reckon that the best approach here will be to use SharePoint search, sort by Hire date descending, and select only top N users. Then, you can display results, for example using DataViewWebPart. It is not an easy way to achieve the goal, but it is preferrable. Here are some links ...


4

You need to execute the following Move-SPUser command (an equivalent of the STSADM MigrateUser command) for the user account in order to update the account name in SharePoint: Move-SPUser -Identity "DOMAIN\jdoh" -NewAlias "DOMAIN\jdoe"


4

Use some powershell like $url = "http://sp2010/" $site = Get-SPSite $url $context = Get-SPServiceContext $site $profileManager = New-Object Microsoft.Office.Server.UserProfiles.UserProfileManager($context) $profiles = $profileManager.GetEnumerator() while ($profiles.MoveNext()) { $userProfile = $profiles.Current $name = $userProfile.DisplayName ...


4

You will need to load it from the User Profiles and not the SPUser object. SPServiceContext svcContext = SPServiceContext.GetContext(site); UserProfileManager profileManager = new UserProfileManager(svcContext); UserProfile profile = profileManager.GetUserProfile(accountname); string department = profile["department"].Value;


4

You also can use the SPUser and SPUserCollection Object to iterate through all user profiles using Microsoft.SharePoint; using Microsoft.Office.Server.UserProfiles; using Microsoft.Office.Server; using System.Web; here is the code: SPSecurity.RunWithElevatedPrivileges(delegate() { using (SPSite siteCollection = new ...


4

The master page of the mysite is the normal v4.master and doesn't load any user profile. There is a web control in every article page in the mysite that makes sure the profile gets loaded. <SPSWC:ProfilePropertyLoader id="m_objLoader" LoadFullProfileOfCurrentUser="true" runat="server" /> If you like to get this done in the masterpage you need to add ...


4

You can use the Where cmdlet to filter the users. $profiles = $profileManager.GetEnumerator() | Where {$_.name -like "IT*"} Note: This does the filtering after retrieving the full list. Also $profiles = $profileManager.GetEnumerator() | Where {$_.MultiloginAccounts -like "domainname\adminID*"}


4

For a client solution I would use the Search REST API. The grouping has to be done on the client, it depends on how you configure your Managed Properties. The trick with People is to pass the correct Result Source ID in the query: For example: ...


4

You cannot change any properties in the User Profiles via client OM code (neither .NET nor via JavaScript) with the exception of the user's profile picture. MSDN - Work with user profiles in SharePoint 2013 Not all functionality that you find in the Microsoft.Office.Server.UserProfiles assembly is available from client APIs. For example, you have ...



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