Guy’s Scripting Ezine 53 – Creating Contacts in AD

Contents for Guy’s Scripting Ezine 53 – Creating Contacts in Active Directory

• This Week’s Secret
• This Week’s Mission – To create Contacts
• Example 1 – Create an OU then build a Contact object in that OU
• Example 2 – Create Contacts from an Excel Spreadsheet
• Summary
• See more on Creating Contacts here
• N.B. Additional Material thanks to JT.

This Week’s Secret

I firmly believe that God gave us all two ears and only one mouth so that we would listen more than we speak.  Listening to you the reader, I see from the survey results, that you want slightly more complex scripts and Active Directory is your favoured topic.

This Week’s Secret is that I am still a little puzzled by WSH (Windows Scripting Host).  If I ignore WSH my scripts don’t work.  However, when I investigate WSH, it does not seem to do much.  My conclusion is that WSH is essential to ‘bind to’ objects, for example Active Directory or network drives.  VBScripts without WSH would be like walls without cement.  The particular WSH ‘cement’ that we use this week is getObject and createObject.

Guy Recommends:  SolarWinds’ Free Bulk Import Tool

Import users from a spreadsheet.  Just provide a list of the users with their fields in the top row, and save as .csv file.  Then launch this FREE utility and match your fields with AD’s attributes, click and import the users.

Optionally, you can provide the name of the OU where the new accounts will be born. Download your FREE bulk import tool.

If you need more comprehensive software, download a free trial of SAM (Server & Application Monitor)

This Week’s Mission – To create Contacts

We have two distinct strategy for creating our contacts.  The first script is simple, it just shows how to create a single contact using VBScript.  The second method is more versatile and demonstrates how to build contact objects using information stored in a spreadsheet.

Introduction to Creating Contacts in Active Directory

Of all the objects in Active Directory, Contacts would seem to be the simplest object to create.  However, I always want to do more than just produce a script which you slavishly copy.

What we both have to remember is that I do not know the name of your Active Directory domain.  This is why so many of my scripts bind to the Root LDAP name rather than requiring you to replace my domain name with your domain name.  The result is that this script will work on which ever domain you execute the .vbs file.   For reference, here are the lines of code which bind to Active Directory.

Set objRoot = GetObject("LDAP://rootDSE")
strDNS = objRoot.Get("defaultNamingContext")
Set objDomain = GetObject("LDAP://" & strDNS)

Guy Recommends: Tools4ever’s UMRA

Tired of writing scripts? The User Management Resource Administrator solution by Tools4ever offers an alternative to time-consuming manual processes.

It features 100% auto provisioning, Helpdesk Delegation, Connectors to more than 130 systems/applications, Workflow Management, Self Service and many other benefits. Click on the link for more information onUMRA.

Example 1 – Create an OU then create a Contact in that OU.

Now I could play safe and create the Contact objects in the Users’ container, but it is more exciting and more realistic to create these Contacts in an OU.  However this leads to the question of what shall we call the OU?  Answer: Suppliers.  Next question, should the script create an OU?  Answer Yes. What happens when you run the script and the OU already exists?  Answer: – it fails!  As a well defined problem is half the solution, I hope that you will be alert and amend my script to cure such problems.

JT wrote in with a solution using On Error... See here

(By the way, if you know of an ‘IF Exists’ method that would apply to the OU problem then do email it to me.  Trust me, I have tried a few methods but to no avail.)

Instructions

1. Important: Which OU will use?  My script uses OU=Suppliers.  Either accept this name, or change the script to reflect YOUR OU, for example OU=MyContacts.
2. Optionally, find and change strYourDescription
3. Copy and paste the script below into notepad or OnScript.
4. Save the file with .vbs extension e.g. Contact.vbs.
5. Double click and examine the message boxes.
6. Check out strContainer

Learning Points

Note 1: Binding is a key concept in WSH scripting.  Check out where the script binds with YOUR domain name. See :
Set objRoot = GetObject("LDAP://rootDSE").

Note 2: Once the script ‘bound’ to Active Directory, did you see the objects that it created?  "OrganizationalUnit" and later "contact".

Note 3: Examine how this script actually creates an OU.  If you run the script for a second time, then either
a) Rem out : ‘ Section to create an OU.
b) Go to your Active Directory and delete the Suppliers OU.
c) Observe the Error Correcting Code in Example 1a

Note 4: See how this line uses & (ampersand) to join three elements, the OU (strContainer),  a COMMA, and finally your Domain
Set objOU = GetObject("LDAP://" & strContainer &  ","  & strDNS)

Note 5: Check the .Put, and .SetInfo methods which actually form the contact object.  ObjUser.SetInfo then gives birth to the Contact.

Note 6: See more on Creating Contacts here

Guy Recommends:  A Free Trial of the Network Performance Monitor (NPM) v11.5

SolarWinds’ Orion performance monitor will help you discover what’s happening on your network.  This utility will also guide you through troubleshooting; the dashboard will indicate whether the root cause is a broken link, faulty equipment or resource overload.

What I like best is the way NPM suggests solutions to network problems.  Its also has the ability to monitor the health of individual VMware virtual machines.  If you are interested in troubleshooting, and creating network maps, then I recommend that you try NPM now.

Download a free trial of Solarwinds’ Network Performance Monitor

Example 1a – With Error correcting code thanks to John T.

This script incorporates On Error Resume Next.  It also uses
If Err.Number <> 0 Then… To catch and then correct the error.  Many thanks to John T for suggesting the error correcting code.

Example 2 – Create Contacts by importing their names and addresses from an Excel Spreadsheet.

The last time that I mentioned using a spreadsheet to import data, 99% of readers were thrilled with the extra dimension provided by a Do.. While…loop.  This technique of reading data from cells is essential for a bulk import.  However, Mr Angry wrote in and complained because he needed Excel on the machine in order for my script to work.  Sorry Mr Angry, but once again you will need Excel in order to give my script a chance of reading from a spreadsheet.

Example 2 follows on from the first example with the addition of the following assumptions:

Assumption 1: You have an OU called Suppliers.

Assumption 2: You have Excel!  In Excel you put the names of your contacts in Column A and the corresponding email addresses in Column B.

Spreadsheet Example:

Row 1 Name     Email

Row 2 Guido     [email protected]

Row 3 Wally     [email protected]

Example of a very simple Spreadsheet Download here

Assumption 3: You understand and can modify:
strPathExcel = "E:\Files\contacts.xls"

Learning Points

Note 1: Go back through the script and check through all the ‘ Comments between each section.

Note 2: If you are looking for a challenge, then try shortening the script.  Perhaps only use one variable strContact where I have used two, strExcelContact and strContactName.

Note 3: Should you be able to come up with an ‘If Exists’ to check on the OU (strContainer) I will be mightily impressed and offer you a free ebook of your choice. (JT Wrote in with a solution)

Summary: Creating Contacts

If you need to add lots Contacts to Active Directory then consider a VBScript.  In cases where you already have the names and email addresses in a spreadsheet, it makes good sense to design a VBScript to import the names and email addresses.

See More Active Directory VBScripts featuring contacts

• User Spreadsheet  • LDAP Properties  • Create Users  • Bulk Import User Ad  • Ezines

• Ezine 23 Enable Accounts  •VBScript Exchange Contact  •VBScript Create Contact  • Tool Kit

• Ezine 42 LDAP  • Ezine 44 CSVDE  •Ezine 53 Contacts  • Ezine 81 Contacts  • Ezine 82 Contacts