Re: Full Username

What you want is (the free) Enhanced AD User Discovery from
http://www.systemcentertools.com/scripts.html

Since I personally had to re-install this on my (recently failed
badly) central primary, you will benefit from my documentation!
Here's the steps I did to configure it just a few weeks ago--I'm sure
you can use this as a base for your configuration:


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. Probably
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 personally like all my sms
logs in the sms\logs folder, not on the root of c:


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 part of that system's automation is to pull the phone
number listed in the AD Attribute "ipPhone" and populate a registry
key on every client. I just like to know that the ad attribute is
correctly populated (because as you know, no matter what, the Desktop
Admin is always responsible for everything that might affect a regkey
on an xp workstation, even if the project has absolutely nothing to
do
with their responsibilities!)


===============
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, 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 domain admin service account.

================
Or, as Kim Oppalfens would say..."The easiest way I can think of to do
this is to migrate your hierarchy
to Configmgr 2007 (the new sms version) and just configure the ad
user
discovery method to collect the attributes."

On Sep 5, 1:44 pm, MSAdmin <MSAd...@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
All the default reports list nt userid. Is there a way to pull the full
uesrname from active directory?

Thanks


.

Relevant Pages

  • Re: Help with a query I am writing
    ... What you want is Enhanced AD User Discovery from ... location for that folder on that sms server. ... This next file you can leave alone forever; but if you want to pull ... and your SMS server has to pull in the information. ...
    (microsoft.public.sms.admin)
  • Re: SMS Active Directory User Discovery-Pull additional attributes?
    ... What you want is Enhanced AD User Discovery from ... if you wish to pull in more AD Attributes than those in the default ... location for that folder on that sms server. ... and your SMS server has to pull in the information. ...
    (microsoft.public.sms.misc)
  • Re: Help with a query I am writing
    ... inner join v_gs_system_enclosure sysenc on ... if you wish to pull in more AD Attributes than those in the default ... location for that folder on that sms server. ... and your SMS server has to pull in the information. ...
    (microsoft.public.sms.admin)
  • Re: Help with a query I am writing
    ... if you wish to pull in more AD Attributes than those in the default ... location for that folder on that sms server. ... You'll either see if fail almost immediately if a configuration is ... and your SMS server has to pull in the information. ...
    (microsoft.public.sms.admin)
  • Re: SMS Active Directory User Discovery-Pull additional attributes?
    ... can you use the Active Directory User Discovery to pull the User First and Last names so it can be added to a query? ... The easiest way I can think of to do this is to migrate your hierarchy to Configmgr 2007 (the new sms version) and just configure the ad user discovery method to collect the attributes. ...
    (microsoft.public.sms.misc)
Loading