Showing Employee ID from AD

[Hopsta]

Looks relatively simple... should i beware and book a week off?

[Mac]

When you say show what do you mean? In ADU&C or via ADO/VB? It's easy to access from VB - employeeID.

You want to show it in ADU&C it's a bit fussier. I did it with VBScript, could dig it out if you want, probably, if I can remember who I did it for.

[Frodo]

Or you could populate or map to a field that is already visible in ADUC or the GAL (Global Address List) Company and Office are visible in GAL and ADUC or use custom-attributes 1 through 15. Depends what you want to do, how the data is getting populated and who needs to see it

[Hopsta]

Need in ad u & c, seen a few scripts on the web, plus need to adsiedit. Will be doing a bulk import with the data.

[Mac]

Bulk import and also need access via ADU&C? Like the man said above, use an already exposed field, it's easier.

[Hopsta]

These the ones that come when you have integrated Exchange? To be honest I need quite a few fields, so using the custom ones would be ideal

[nordberg]

Use one of the user specified attributes and import with csvde.

Done lots of this in the past with great results.

[Frodo]

You can also use LDIFDE which has one benefit over CSVDE and that is it can amend as well.

Couple of other options:

Use "dsmod user" I've used this before as you can apply the syntax in Excel with a few string manipulations. Each row being a seperate command, then save as tab delimited and change to a batch file.

If your doing it often have a look at ADModify.Net which has the benefit of saving a backout xml file so if you screw-up you just run the unapply xml

If you manipulating daily then learn to script with Powershell or VBScript (latter is easier in my opinion but is now deprecated by MS). Libaries of interest being ADO and ADSI

Have fun!

[Mac]

Vb is easier but Powershell is way more powerfull once you have the hang of it

[Frodo]

I know, I know Mac but eveything always seems to be needed to be done quickly. So 5 minutes in VBScript or about 3 hours in Powershell because I have to look everything up. Oh well get there one day

[Mac]

Yeah I do know what you mean. You know you can link out to object calls in the traditional VB manner? My early scripts all have that in, before I got the hang of it proper

$oShell=new-object -comobject "wscript.shell"

for example is pretty much the same as

SET oShell=CreateObject("wscript.shell")

Grandmother, eggs etc.

[Frodo]

I've seen that done in a few script examples.

I am pretty okay now with the get-wmi (gwmi) cmdlet but some of the stuff is a bit more alien. Still not really worked out how to call functions and the fact you have to write the function before you use it whilst in vbscript I had all the sub-functions after the main sub.

[Hopsta]

Cheers lads, will be able to sort something one way or another next week