Important Problematic conditions are checked only on the server on which this manifest is run. To make sure that you have maximum coverage, we recommend that you run this package on every computer in a SharePoint farm.
This article describes the function of the SPUserProfile2013 manifest file.
Required permissionsThe rules in the diagnostic package use the SharePoint Windows PowerShell snap-in for information about your farm. Therefore, the account that is used to run the diagnostic package must be the farm account or be given the required permissions through the Add-SPShellAdmin command. The farm account is the account under which the timer service and central administration site's application pool run.
Some rules in this diagnostic package must also have local server administrative permissions to use remote and local administrative tools and also to access secure system locations such as the registry. You can use the following table to reference the permissions that are required for each rule.
|Permission code||Description||Required permission|
|1||Use SharePoint Windows PowerShell cmdlets to interact with the SharePoint farm.||Farm administration|
|2||Run queries against SharePoint databases.||Farm administration|
|3||Access server administrative tools.||Server administrative|
|4||Access files and other resources on the server.||Server administrative|
Information that is collected
Password synchronization reportThe password synchronization report is a new file that is generated by the troubleshooter. The report output resembles the following:
Password Synchronization Report Generated from SERVER1: 04/08/2011 10:51:13The information is sorted by UserName and Name (application pool). As the sample output shows, the password hash for the 0cbce7b825854b9d93b2610c3627533a application pool has a different value on SERVER1 than it has on SERVER2. This indicates that the passwords do not match. This might have occurred because the password was changed on one server but not on the other. As the sample output for the SharePoint – 80 application pool shows, the password hash is identical on both servers in the farm. This indicates that the passwords are in sync.
Machine Name UserName Password Hash
======== ==================================== =================== ========================
SERVER1 0cbce7b825854b9d93b2610c3627533a contoso\user1 taggcB3Cg9kkSVLVZlCTyg==
SERVER2 0cbce7b825854b9d93b2610c3627533a contoso\user1 KU91YgOOM8CYdezeuhn96w==
SERVER1 SecurityTokenServiceApplicationPool contoso\user1 taggcB3Cg9kkSVLVZlCTyg==
SERVER2 SecurityTokenServiceApplicationPool contoso\user1 KU91YgOOM8CYdezeuhn96w==
SERVER1 SharePoint - 30699 contoso\user1 taggcB3Cg9kkSVLVZlCTyg==
SERVER2 SharePoint - 30699 contoso\user1 KU91YgOOM8CYdezeuhn96w==
SERVER1 SharePoint Central Administration v4 contoso\user1 taggcB3Cg9kkSVLVZlCTyg==
SERVER1 c408cf58b72d493da1925746dd8a0012 contoso\user2 LmbbRTCUtCxxfGHdq3l/nA==
SERVER2 c408cf58b72d493da1925746dd8a0012 contoso\user2 LmbbRTCUtCxxfGHdq3l/nA==
SERVER2 SharePoint - 80 contoso\user2 LmbbRTCUtCxxfGHdq3l/nA==
SERVER1 SharePoint - 80 contoso\user2 LmbbRTCUtCxxfGHdq3l/nA==
ID do Artigo: 2837391 - Última Revisão: 5 de ago de 2015 - Revisão: 1