Hot answers tagged

9

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 ...


8

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

You can perform the following to resolve the issues: Make sure User Profile Synchronization service is running In the user profile service application make sure "Profile Synchronization Status" is not stuck in synchronizing state. Start a full User Profile Synchronization Re-add forest and make sure the password of the account used for synchronization ...


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.


5

Go to Central Admin -> Manage Service Applications -> User Profile Service Application


5

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

Please read this article by Harbar: http://www.harbar.net/articles/sp2010ups2.aspx there are full definition of your problem and ways to resolve it


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 ...


4

based on your statement, it looks like the user profile sync is not happening properly. follow the below troubleshooting steps: Try doing a sync manually meaning re-importing. that should clear the problems. Inspect the log entries Make sure timer services and user profile sync services are running properly. Also, additionally make sure the account used ...


4

The primary issue happened to be that IE used "normal" mode to open the CA site. To get the context menu for AD connection I had to force IE11 to use "compatibility mode" for CA site, this added the missing controls to the connections list.


3

The screenshot shows the People Picker and I take it you'd like to prevent certain Active Directory (AD, LDAP) Users from being shown. As you've tagged the question with Profile-Sync and talk about 'Search' you may be more concerned with multiple profiles in the User Profile Service (UPS). People Picker If it's the People Picker you're interested in then ...


3

No, you should be using the single sync connection for the entire forest. If you have a secondary forest (or more) create a sync connection per forest.


3

You have more copies of each services because your farm has more servers. Try this to see the online services: Get-SPServiceInstance | where {$_.Status -eq "online" } | Sort TypeName | Format-Table TypeName,Id,Status,Server Take also a look here: multiple results for each service instance


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

I could be very wrong here but I think the AD user profile sync is only available in MOSS Server and SharePoint 2010 Server, and not in plain WSS.


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

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 ...


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 ...


3

This sounds like 'Replicating Directory Changes' permissions was not appropriately applied to your sync account. I aggree with Seb, you should use the Harbar guide.


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 ...


2

A common problem is people removing the farm account from local administrators on the servers, due to security. This is a good practise, but if you perform backups using the SharePoint methods (powershell/central admin) it'll unprovision UPS before backup to get a stable snapshot of the farm and then try to provision it again after the backup, but fail due ...


2

You can only have a one way sync of user profile properties between AD en SharePoint. You cannot import and export attributes at the same time unfortunately. More info at http://technet.microsoft.com/en-us/library/gg188041.aspx and http://www.harbar.net/articles/sp2010ups.aspx (search for the keyword "direction" in both articles)


2

Sometimes the changes do not propagate to the web app. Go to the hidden user list and verify the email address is not correct: http://sitecol/_catalogs/users/simple.aspx ..delete the user in question. Now to pull that user down again, you must add them to a group or grant permissions (You can delete those permissions immediately) ...


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 ...


2

As stated by my comment, you may need to recreate the service application...


2

Sounds like you have a configuration issue with either a AD sync or your User Profile Manager. There is a timer job that runs and tries to link each mysite with a owner, if it doesn't find it, it starts the clean up. This is basically the thing that will delete the "My Content". Other data will remain in the sync process. Read up here: ...


2

Open the MIISClient: C:\Program Files\Microsoft Office Servers\14.0\Synchronization Service\UIShell\miisclient.exe Check for any detailed error messages and cancel the current run.


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 ...



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