Where can the new Ignoreisactive Parameter for the STSADM Sync Operation be used?


After the Microsoft Office SharePoint Server build 12.0.6314.5000, the stsadm Sync operation introduced a new parameter – “ignoreisactive”, specially designed for the issue described in the following article: http://support.microsoft.com/default.aspx/kb/952683 .

This issue occurs because the tp_IsActive flag is false (0) for the user in the userinfo table in thecontent database of the Web Application (by default only active user profile is synchronized).

Regarding the article, if you experience this problem (The welcome name on a site is not changed as expected after you edit the name of a user profile in SharePoint Server 2007), the solution is to install the update, but :

After you apply the update, the welcome name on the site is still not changed as expected. However, if you add a new user after you apply the update, this name will be listed as the welcome name.

So, do I really need to delete and create the user again?


No, you can use the ignoreisactive parameter, as follows:

1. Ensure you are running MOSS version 12.0.6314.5000 or higher

(New parameter added for stsadm -o sync)

2. Run stsadm -o sync -ignoreisactive 1

(All profiles we be synchronized, the flag will be ignored)

3. Run stsadm -o deleteolddatabases 0

(All synchronization logs will be deleted >> next profile sync run will be a "full sync")

After that, with the next profile synchronization job execution, all profiles will be synchronized. To check this, you can run stsadm -o listolddatabases 0 and search for the GUID of the affected content database.

However, if you don’t want to wait for the next profile execution job, you can use stsadm –o sync –synctiming m:5 command (http://technet.microsoft.com/en-us/library/cc263196.aspx) to force the profile synchronization job to be executed every 5 minutes. In a productive environment please changes back the value to 1 hour or you may experience a performance decrease!

Note that this workaround is valid to all changes in AD properties (not only the welcome name).

See you next time …

Nuno Nunes