MOSS AD Synch Issues Part 2

So I was having issues with the MOSS AD Synch of the user profile info into MOSS from Active Directory (email address, first and last name etc).

The issue is this, the import process into the Shared Services database from Active Directory was working and scheduled and fine. A full import was done and all users came in. Then, I scheduled hourly incremental import (runs like 10-20seconds max on a 1200 user AD). Fine.

But, the individual Sharepoint sites each have their own Content Database (SQL db) right? What was happening is the UserProfile table (where all this info is stored) was not being updated in the Content DBs but WAS BEING UPDATED IN THE SSP DB. Turns out their is a Timer job called ProfileSynch that was failing. It had no credentials to login to the SSP_DB as the specified user (EGSEG-ROSMOS01\sa_MOSS2007). So, now I am off now to fix that problem (and hope this works)! Why can't MOSS be less complicated? UGH - the NCAA games are starting soon.. GO TIGERS!!! Memphis, Lousiville, UNC, and Syracuse are my Final 4 with Memphis over UNC in the championship!

MOSS AD Synch Issues Part 1

1. MOSS provides user profile from AD sync to user profile list while WSS doesn't.

2. MOSS support Active Directory sync to user profile other than lists, and computer information in AD can not be synced.

3. If you want to get MULTIPLE AD information in AD sync to one list, it is also impossible using MOSS provided user profile sync.

Here is a custom tool from sharepointboost.com (for purchase?) that tries to address the shortcomings: