Tag Info

Hot answers tagged

6

This is what I follow. The most important thing to note is if you screw up somewhere along the way you have to blow away your service application before trying again. Update Very rarely I have to remove the FIM certificates when things are really broken with the user profile service: Stop the SharePoint Timer Service Stop the User Profile Service if ...


6

I found my solution from this blog. Go to your Central Admin website Go to "Application Management" Go to "Service Applications -> Manage Service Applications" Click on "User Profile Service Application" Click on "Synchronization -> Configure Synchronization Connections" Click on your connection and select "Edit Connection Filters" from the menu Add a new ...


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

I believe that James is wright on. When you build a WSS instance it will pull in details from AD. However, changes after the fact don't update the user properties in WSS 3. This is supported in MOSS 2007 and greater. I used a product that was able to overcome this limitation. Here is a link Simego


4

There are workarounds to utilize local account when installing on Win7, but you wont want to do that in a production because: you wont be supported by Microsoft your farm wont scale you can count on having weird issues that you will most likely not find documentation on. In order for you to setup synchronization, when you configure the sync you need to ...


3

Quotes from relevant source: http://www.harbar.net/archive/2011/02/10/account-deletion-and-sharepoint-2010-user-profile-synchronization.aspx ..during the first incremental synchronization after the accounts are deleted from AD, the user profiles will be marked for deletion in the Profile database. In order to actually delete the profiles, we ...


3

This problem is down to the disconnect between the UserInfo table and the Profiles. WSS only uses UserInfo table, hence the core platform in the team sites etc relies on this. When you do a profile sync the UserInfo table is updatedd, but (and here the problem) if the User is identified as active. (i.e. they have actually contributed something to a ...


3

When the user's name was changed was a new account created or was the display name on the old one changed? Since SharePoint's profiles link to the SID of each account a new account would have a new SID and there would officially be two accounts in SharePoint. When you resolve them in people and groups with the new name, you are pointing to the new account. ...


3

Just as you say - you cannot use the UPA in Standalone configuration. You need a server Farm setup. I wouldn't even try a workaround with UPA on standalone - enough trouble getting it rollin on a farm already :-) Configuring a server farm does not take much more time or problems compared to a Standalone, esp if its a demo or dev box. Almost the opposite - ...


3

To isolate the problem during setting up of User Profiles sync, it is very common that you may not get to the actual error straightaway. The right way to get the actual error message is to use the Synchronization service manager (MIIS Client). Path to MIIS Client can be found here: C:\Program Files\Microsoft Office Servers\14.0\Synchronization ...


3

I found this great article on how to accomplish this. Assuming that you already have basic user profile synchronization working, the steps are: Create an import PictureUrl mapping - Go to your Central Admin site "Manage Service Applications -> User Profile Service Application -> Manager User Properties -> Picture" and select "thumbnailPhoto" as the ...


2

You don't have to export anything back to AD after importing the profiles. Just don't allow any mapped properties to be edited and don't complete the setup for the two-way sync. Note however even though you don't write anything back, you still need to provide an AD account that has replicate directory changes as specified in any of the MSDN documentation for ...


2

Yes, each site collection has a SQL table that stores the name of each security group/user. Check to make sure that your Profile Synchronization timer job has run correctly for that site collection. If the issue persist, you can call the SharePoint users and groups webservice to manually update the display name for that user.


2

Here's how I was able to do something about: I marked property Birthday as Replicable Start full synchronization Later I was pleasantly surprised that field Birthday was also created into Users Information List on the Site Collection, so, cool, but there are nothing into value I looked with Reflector how to sync works via ...


2

When the user first provisions or accesses their MySite they are prompted if the want Microsoft Office to remember the location of their MySite. I believe if the user selects "Yes" it writes the value to AD, but I have never reverse engineered this to see how it actually works. I believe the value is being updated directly into AD and is not using User ...


2

I've validated that this is resolved in the SharePoint Dec 2011 CU. Also, uploading pictures for other users via Central Admin has been fixed, which was purposefully broken in the June CU. You can find the links to the Dec CU updates here.


2

Microsoft has confirmed this bug in the Oct 2011 cumulative update. According to this MSDN blog post the fix should be included in the Dec 2011 cumulative update and should be released around December 27th.


2

You can also accomplish this by going to http://yourservername/my/user%photos/ This takes you to a picture library that houses all uploaded photos. It will contain three images per person (three different sizes). Once you get to this location you can open the folder in explorer view, select properties and see what the size is as well as how many files are ...


2

You could create user profiles programmatically using UserProfileManager.CreateUserProfile method. You can leverage this method either by using Console Application, or by creating a PowerShell script. I'd prefer the latter approach. PowerShell code for creating one profile would look something like this: $serviceContext = Get-SPServiceContext ...


2

You must ensure all the points taken care of before you start the User Profile Sync Service as mentioned here - Rational Guide to implement user profile synchronization service and Stuck on Starting UPSC problems. With time, these articles has somewhat become a defacto reference for User Profile related issues and almost majority of the issues have root ...


1

Does your service account have Replicate Directory Changes permission on your domain? Read more here: http://technet.microsoft.com/en-us/library/0eeb69e0-c799-4da1-b3ec-c0cc4efd585e#RDCdomain. Your account needs the proper permissions to replicate with the domain through UPS. HTH


1

I think I have understood your question. Please correct me if I have mistaken. Before synchronizing user profile properties in AD, you will have to map the properties in AD to the properties in SharePoint user profile. If you do not provide a mapping or remove a mapping, ideally that particular column will not be imported. Please visit this msdn article ...


1

Looks like there is an AD problem. We have here two SharePoint installations, one for productive usage and one for testing. We also have two AD and two Exchange server. Test-AD has a group called SharePoint Admins Universal Group Properties and contains the user folder from the one and the other AD. This is to get known of the common users of productive ...


1

Microsoft changed the name from Pictures to "User Photos" in the October CU and the December CU does not fix the problem. They didn't update the error message either, so it still says it's looking for Pictures, but it's really looking for "User Photos". You can confirm this by looking at the code for the upload control in reflector. Create a Picture ...


1

There is no out of the box way to handle validation or approval processes for user maintained fields in the User Profile. I've worked through some scenarios for updating a selection of fields with validation, but that was using a custom ApplicationPage hosted in the layouts directory. My recommendation would be to limit the fields that a user can edit to ...


1

Alernatively, you could look at the Forefront Identity Manager tool (the software that actually does the Sync) to look at the import/export errors. This would help you identify the users who did not sync and give you more information about how to correct the issues on their accounts. The tool can be found at C:\Program Files\Microsoft Office ...


1

The most likely cause of problems starting user profile synchronization are the farm account permissions, which needs the "log on locally" right and to be local admin. on the machine running the synchronization while the service is provisioned. The definitive source of information on this topic is Spence Harbar's blog: Rational Guide to implementing ...


1

Ok, not sure if this has been tried since there's a bout 50 million things to try on Harbar's site (Good site though) I always do the following if the actual Service is stuck in Stopping or Starting: Firstly, run this: Get-SPServiceInstance This will show a list of service Instances. Find your broken Service (Status will be Provisioning or ...


1

You basically need to add all the plumbing to "hook up" the organization profiles. The UI and some API stuff exist but it was never really finished. That is to say, you can make it do whatever you like as long as you are willing to put in the work. MS API Organization Profile Class ...


1

The link below describes how to remove disabled users. http://www.bryanporter.com/archive/2010/02/20/excluding-disabled-user-accounts-from-profile-synchronization-in-sharepoint-2010.aspx



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