Configuring SystemCenterTools.com's Enhanced User Discovery 1.1
Last summer, I had to rebuild our central primary site after hardware failure. At the time, I took detailed notes of how I setup http://www.systemcentertools.com 's EUD, or Enhanced User Discovery 1.1, for SMS 2003. I recently came across my notes and thought "This would be a good blog entry."
After installation on your primary site server, you need to edit 1 file to configure. There is another file to edit if you wish to pull in more AD Attributes than those in the default settings file.
File #1: \program files\Enhanced AD user Discovery v1.1\Enhanced AD User Discovery.exe.config
Line 6: change value="SMSDomain" to be your (shortname) domain. I assume it might be something like MYCOMPANY (not mycompany.com)
Line 11: change value="" to be your fqn domain name. Like mycompany.com
Line 15: change value="SMSSERVER" to be the name of your smsserver.
Line 19: change value="RC2" to be the site code of your smsserver.
Line 22: change value="c:\sms\inboxes\ddm.box\" to be the correct location for that folder on that sms server. For me, we install sms to the E: drive, so I had to change it.
Line 27: (optional) change value="c:\enhancedaduserdisc.log" to <yourdriveletter>:\sms\logs\enhaduserdisc.log.
(I called that optional simply because I like all my sms logs in the sms\logs folder, not on the root of c:
File #2 \program files\Enhanced AD user Discovery v1.1\aduserattribs.xml. This next file you can leave alone forever; but if you want to pull in more ad attributes, you'd add them to aduserattribs.xml. For me, I added 2 additional attributes. I wouldn't mess with that file until you've confirmed success for the defaults attributes.
<ADAttrib>
<ADAttribName>telephoneNumber</ADAttribName>
<DDRPropertyName>Telephone</DDRPropertyName>
<DDRPropertyLength>128</DDRPropertyLength>
</ADAttrib>
<ADAttrib>
<ADAttribName>ipPhone</ADAttribName>
<DDRPropertyName>IPPhone</DDRPropertyName>
<DDRPropertyLength>64</DDRPropertyLength>
</ADAttrib>
The reason I added them was because at my company we have a VOIP phone system, and I wanted that attribute available for SMS reports for the helpdesk and techs.
How to test:
Double-click the executable (assuming your logged-in account has the credentials to read user objects in AD)
Open up the log file (for me, that was e:\sms\logs\enhaduserdisc.log) using trace32.exe
You'll either see if fail almost immediately if a configuration is incorrect; or, you'll see it start enumerating all of your user accounts out of AD. For me, it only takes ~3 minutes to finish gathering data. Then it has to send the DDRs into the ddm.box folder, and your SMS server has to pull in the information. Depending upon your server, and the number of user objects in AD for you, I can't estimate how long that might take; but give it at least 5-10 minutes. Then in the SMS console, the All Users collection, pick a user (like yourself) that will most likely have entries for email, department, title, description, first name, last name (which are the default attributes pulled in); right-click that user, and scroll through the list of things--you should hopefully see the new attributes (with data) listed!
How to automate so it pulls in any new or changed user information:
I set up a scheduled task on my primary site server to run that executable at 3 a.m. daily, using a service account. On whatever schedule you normally use when checking on overall SMS Health, check the enhaduserdisc.log to confirm it is working as expected.
Notes: at this time, EUD 1.1 is not needed if you are running ConfigMgr 07; you can pull in additional Active Directory user attributes by modifying the existing Discovery Method for "Active Directory User Discovery", the Active Directory Attributes tab.