Many of us are glad to see the return of the AD direct import function for creating and maintaining user profiles in SharePoint 2013. In my own experience, it enabled a quick and clean setup of profile sync that currently has the pleasant side-effect of allowing one to apply the recent March (KB 2767999) and April (KB 2726992) CUs without FIM issues.
Using Spencer Harbar’s great blog, and doing some digging, I discovered that the FIM bits in SP 2013 RTW were once again (remember UPS in 2010) not real current. Indeed, I found that is was not easy or possible maybe to get the User Profile Sync windows service running once again after the application of the March/April CUs.
Hum…where have I seen that before…
Suffice it to say that the 2013 farm installation I was using was hosted on Server 2012 rather than 2008 R2, and I am now quite certain this was part of the root cause of the issue.
Except for the few cases where FIM might actually be required, this is a moot point for anyone who can use ADI to create and update profiles. If you need FIM to work correctly, wait a while and it may happen. However, presenters at TechEd said that FIM was probably going to be deprecated from SharePoint at some point.
Back to ADI itself, a nice addition to the profile sync timer job executing is that ULS entries are created as a trace of what transpired during the operation; these entries are prefixed with this text below.
Use can just search the ULS log file for this string and find all the entries – nice! In addition, if you look at the Usage Log settings in Central Administration, you should see that an entry for User Profile ActiveDirectory Import Usage has been checked for inclusion in the Usage logs. Unfortunately, this cannot be reported via Usage Reports (read this post by Joel Oleson), nor is any detail about the ADI sync readily available.
Is it asking too much to have a log of detailed ADI results for debugging the import process?