This project is read-only.
Please read all of the documentation below prior to running the job. The job will update user profiles and delete inactive users from the site collection user list. If you would like to see what users will be detected, run the job using the Dry Run command below. As another precaution, you may also want to run this on a test web application/test environment prior to running this on any production environment.

This feature creates a timer job that runs daily on the web application
that it was activated on and updates the users in the site collection users group.

To see an example site users list, access:

http://<site collection name>/_catalogs/users/simple.aspx

Within each site collection users list, it will attempt to:
1. Remove any users that are no longer active in Active Directory
2. Update user properties if they have changed in Active Directory
3. Populate 0 or more site collection User Information Lists within the web application with all AD users

1. Run the deploySPUserInfoUpdater.bat to deploy the feature to the farm.
This feature is a web application feature and can be found under:
Central Administration -> Application Managment -> Manage Web application features

2. IMPORTANT****** Restart the Windows SharePoint Services Timer on each server
- either open the Services console on each server to restart
- or run the restartSharePointServicesTimer.bat

3. Select the web application to activate this feature on.

Once this feature is activated, it adds a SharePoint timer job titled:
"SP User Info Updater job" to the timer job definitions. (Found under Central Administration ->
Operations -> Timer job definitions)

4. Run the newly installed command below to see the job information:

stsadm -o SPUserInfoUpdaterGetJobInfo -url <webApplicationUrl>

5. Configure the job information using the stsadm commands detailed below

1. Deactivate the web application feature to remove the timer job and the properties stored in the web
application property bag
2. Run the retractSPUserInfoUpdater.bat to retract and remove the feature from the farm.

Get Job Info
Once the feature is activated, you can see the job details (output path, last run time, schedule)
by specifying:

stsadm -o SPUserInfoUpdaterGetJobInfo -url <webApplicationUrl>
Ex. stsadm -o SPUserInfoUpdaterGetJobInfo -url ''

Ensuring All users in a site collection
Default site collections: ';;' under site collection: ''
To make updates, run:

stsadm -o SPUserInfoUpdaterSetSCToEnsureAllADUsers -url <webApplicationUrl> -sitecollections <siteCollectionUrl1;siteCollectionUrl2;>
Site Collections must be delimited with a ';'

Ex. stsadm -o SPUserInfoUpdaterSetSCToEnsureAllADUsers -url '' -sitecollections ';;'

Output is logged under the default application data folder:

C:\Documents and Settings\All Users\Application Data\Microsoft\SharePoint\Microsoft\SharePoint\SPUserInfoUpdaterLog

By default all log files are retained.

To make updates, run:

stsadm -o SPUserInfoUpdaterSetJobLogPath -url <webApplicationUrl> -path <path> -daystokeep <days to keep log files>

Ex. stsadm -o SPUserInfoUpdaterSetJobLogPath -url '' -path 'C:\\logs' -daystokeep '120'

If using a UNC path, make sure that the identity that is running the Windows SharePoint Services Timer
has full control access under the Security tab and the Sharing tab of the folder

If all log files should be retained, specify "0" for the "daystokeep"

NOTE: the log file is written to the output folder, under a subfolder with the web application name.
The file is written after it has processed the site collection; depending on the number of users, and how often it
has been updated, this can take anywhere from a few minutes up to a few hours.

Job Schedule
The default job schedule is "daily at 22:00:00", which specifies to run daily at 10:00PM

To make updates, run:

stsadm -o SPUserInfoUpdaterSetJobSchedule -url <webApplicationUrl> -schedule <schedule> -dryrun 0

Ex. stsadm -o SPUserInfoUpdaterSetJobSchedule -url '' -schedule 'daily at 09:00:00' -dryrun 0

If you would like a dry run, with no changes actually made, but outputted to a log, specify -dryrun 1

Last edited May 16, 2012 at 4:21 PM by sparsee, version 16


No comments yet.