Printable View
سلام به دوستان
من میدونم که میشه برای اطلاعات شخص New Contact درست کرد ولی
چطور میشه در سرور 2003 یک Contact List درست کرد که تمام اطلاعات کارمندان داخلش باشه. مثل شماره داخلی و ایمیل و .... که کارمندان بتونن با سرچ در Active directory اون لیست رو باز کنن. آیا راهی هست که تمام اطلاعات روی یک فایل باشه؟؟؟؟؟
[LEFT][CODE]http://www.msexchange.org/articles/Migrating-Contacts-Distribution-Lists-Outlook-Active-Directory.html[/CODE]
[B]Migrating Contacts and Distribution Lists from Outlook to Active Directory[/B]
Use script magic to turn your Outlook MAPI based contact information to a lightening fast Active Directory, Exchange enhanced LDAP implementation
[B]Introduction[/B]
In my article "[URL="http://www.msexchange.org/tutorials/Using_Exchange_2000_as_a_low_end_contact_management_solution.html"]Using Exchange 2000 as a low end contact management solution[/URL]" I presented a way of using Active Directory to search for contacts. Active Directory, once it is extended by Exchange, provides a scalable solution for looking up contacts using the LDAP protocol. Resolving contact names using Outlook when accessing Active Directory is really fast, even if you have hundreds of contacts, and doesn't slow down the way it does when you have too many contacts in an Outlook contacts public folder.
On the other hand Outlook contacts folders are really easy to use. You can import information from a lot of sources using the Import and Export wizard without much hassle. Any application which supports exports of its contacts to a text file can be exported to Outlook because you can always rearrange the contact field to match those of Outlook.
While Active Directory provides the LDIFDE and CSVDE utilities for importing bulk information, they are not really the easiest conversion utilities that one could hope for.
I will present here some useful scripts for migrating contacts from Outlook to Active Directory. For you, it can be a two part process. For example, if you need to migrate 70,000 contacts from Outlook Express, you can first export them to Outlook, and then use my scripts to transport them to Active Directory.
[B]Contact Migration Script[/B]
My script, written in VBScript language has the following requirements. It assumes you've placed the contacts in a Public Folder named "Company Contacts", but you can change the line that begins with "Set myfolder = myNameSpace.Folders" to point to whichever Outlook folder suits you.
You will need to change the line that begins with "Set objContainer =" so that it will point to an existing Organization Unit (OU) where the Contacts will be placed. To do this, replace the part that says "OU=….,DC=…." with the distinguishedName attribute of the OU. This property can be found by using the support tools utility ADSIEdit.
[INDENT] [IMG]http://www.msexchange.org/img/upl/image0021108986192056.jpg[/IMG][/INDENT]For the script to work properly you would also require the "countrycodes.csv" file downloaded [URL="http://www.msexchange.org/upl/documents/countrycodes.csv"]here[/URL]. This file allows Active Directory to register a contact's country with its country code.
The script goes through all the contacts in the Public Folder, checks to see whether the contact already exists and if not creates the contact. It goes through all the contact fields and if a contact property exists it is translated to its Active Directory equivalent.
A couple of issues came up while writing this script. The main one was what to do with duplicate contacts, or contacts with same name. The primary check is to see whether the e-mail address exists. If it does not and the contact name already exist (as determined by the DNExists function), the company name is added to the directory name of the new contact.
The script migrates only the business address. You can customize the script to add the home address but know that the Active Directory Users and Computers snap-in does not show this address at this point.
[CODE]
[I]ContactMigationScript.vbs [/I]
[I]Dim objRecip
'On Error Resume Next
Set fs = CreateObject("Scripting.FileSystemObject")
Set myOlApp = CreateObject ("Outlook.Application")
Set myNameSpace = myOlApp.Application.GetNamespace("MAPI")
'Get the Public Folder containing the contacts
Set myfolder = myNameSpace.Folders("Public Folders"). _
Folders("All Public folders").Folders("Public Contacts")
'Open a test file for reporting putposes
Set reportfile = fs.CreateTextFile ("c:\contactreport.txt")
'Look for all contacts in the Public Folder
For I = 1 To myfolder.Items.Count
If TypeName(myfolder.Items.Item(I)) = "ContactItem" Then
Set outlookcontact = myfolder.Items(I)
'Fix the FileAs field so it won't contain Linefeeds.
FixedFileAs = Replace (outlookcontact.FileAs,Chr(13)," - ")
'Get the Public Contacts OU
Set objContainer = GetObject([/I][URL="ldap://OU=Public%20Contacts,DC=company,DC=com"][I]LDAP://OU=Public Contacts,DC=company,DC=com[/I][/URL][I])
TestforContact = False
'Check to see if the e-mail address already exists
For Each adcontact In objContainer
If (CStr (outlookcontact.Email1Address) <> "") And _
(CStr(adcontact.mail) = CStr (outlookcontact.Email1Address)) Then _
TestforContact = True
'Check to see whether this is a new contact with an existing name, but from a different company
If (CStr (adcontact.displayName) = FixedFileAs) And _
(CStr (outlookcontact.CompanyName) = CStr (adcontact.company)) Then _
TestforContact = True
Next
'Create a valid directory name for the contact.
CNName = "CN=" & outlookcontact.FullName
stAddCompany = ""
If DNExists (CNNAME) Then
If outlookcontact.CompanyName = "" Then
TestforContact = True
Else
'If the directory name exists add the company name to it.
CNName = "CN=" & outlookcontact.FullName & " (" & outlookcontact.CompanyName & ")"
If DNExists (CNNAME) Then TestforContact = True
End If
End If [/I]
[I] If TestforContact = False then
' Create a Contact[/I]
[I] Reportfile.WriteLine "Creating: " & FixedFileAs[/I]
[I] Set objContact = objContainer.Create("contact", CNName)[/I]
[I] ' Now fill the contact attributes in Active Directory
With objContact
.Put "displayName", FixedFileAs[/I]
[I] If outlookcontact.LastName <> "" Then _
.Put "sn",CStr(outlookcontact.LastName)
If outlookcontact.FirstName <> "" Then _
.Put "givenName",CStr(outlookcontact.FirstName)
If outlookcontact.CompanyName <> "" Then _
.Put "company" , CStr(outlookcontact.CompanyName)
If outlookcontact.Department <> "" Then _
.Put "department" , CStr(outlookcontact.department)
If outlookcontact.BusinessAddressCity <> "" Then _
.Put "l", CStr(outlookcontact.BusinessAddressCity)
If outlookcontact.Title <> "" Then _
.Put "title", CStr(outlookcontact.Title)
If outlookcontact.WebPage <> "" Then _
.Put "wWWHomePage", CStr(outlookcontact.WebPage)
If outlookcontact.Department <> "" Then _
.Put "department" , CStr(outlookcontact.Department)
If outlookcontact.BusinessAddressStreet <> "" Then _
.Put "streetAddress" , CStr(outlookcontact.BusinessAddressStreet)
If outlookcontact.BusinessAddressPostOfficeBox <> "" Then _
.Put "postOfficeBox" , CStr(outlookcontact.BusinessAddressPostOfficeBox)
If outlookcontact.BusinessAddressPostalCode <> "" Then _
.Put "postalCode" , CStr(outlookcontact.BusinessAddressPostalCode)
If outlookcontact.BusinessAddressState <> "" Then _
.Put "st" , CStr(outlookcontact.BusinessAddressState)
If outlookcontact.BusinessAddressCountry <> "" Then
.Put "co", CStr(outlookcontact.BusinessAddressCountry)
'Open a file containing table of Country Name, Country designation (two characters) and Country Code
'(Numberical code like the one used for dialing)
Set codes = fs.OpenTextFile("c:\countrycodes.csv")
Do While not codes.AtEndOfStream
countryst = codes.ReadLine
countryar = Split (countryst,",")
If countryar(0)= CStr(outlookcontact.BusinessAddressCountry) Then
.Put "c", countryar (1)
.Put "countryCode", CInt(countryar(2))
End If
Loop
End If
If outlookcontact.BusinessTelephoneNumber <> "" Then _
.Put "telephoneNumber" , CStr(outlookcontact.BusinessTelephoneNumber)
If outlookcontact.HomeTelephoneNumber <> "" Then _
.Put "homephone" , CStr(outlookcontact.HomeTelephoneNumber)
If outlookcontact.PagerNumber <> "" Then _
.Put "pager" , CStr(outlookcontact.PagerNumber)
If outlookcontact.MobileTelephoneNumber <> "" then _
.Put "Mobile", CStr(outlookcontact.MobileTelephoneNumber)
'Create the mailNickname (alias) attribute from the e-mail and mail-enable the contact.
If outlookcontact.Email1Address <> "" Then
Set objRecip = objContact
TempAr = Split (outlookcontact.Email1Address,"@")
objRecip.mailNickname = TempAr (0) & "at" & TempAr (1)
FwdAddress = "SMTP:" & outlookcontact.Email1Address
objRecip.MailEnable FwdAddress
End If
.SetInfo[/I]
[I] End With[/I]
[I] Else
Reportfile.WriteLine "Ignoring " & FixedFileAs
End If
End If
Next [/I]
[I]Reportfile.close [/I]
[I]Function DNExists (dn)
'Determines if a directory name exists by querying Active Directory using LDAP
DNExists = False
Set rootDSE=GetObject([/I][URL="ldap://RootDSE"][I]LDAP://RootDSE[/I][/URL][I])
DomainContainer = rootDSE.Get("defaultNamingContext")
Set conn = CreateObject("ADODB.Connection")
conn.Provider = "ADSDSOObject"
conn.Open "ADs Provider"
ldapStr = "<LDAP://" & DomainContainer & ">;(& (cn=" & Mid (dn,4) & ") );adspath;subtree"
Set rs = conn.Execute(LDAPStr)
If rs.RecordCount = 1 Then DNExists = True
conn.Close
End Function[/I]
[/CODE]
The most important and somewhat tricky property of them all is the e-mail address. In Active Directory, a contact is assigned a single e-mail address. It is also assigned an Exchange "alias", now called "mailNickname". This property has no real functionality for contacts but it has to be unique in Active Directory for the contact to be created. In the script I create this property by replacing the "@" symbol with the word "at" but it can be any other unique name.
This script cannot migrate more than the first e-mail. A contact needs to be stamped by Exchange before you can add more e-mail addresses, so I provide a second script which should be run after the Exchange RUS has been fired, which usually happens in a range of fifteen minutes after running the contact migration script.
The second script goes through all the contacts in the Public Folder looks for a matching Exchange stamped contact created earlier and adds the e-mail address. Outlook supports three e-mail addresses per contact but I assumed two will suffice. If you need all three e-mail addresses, simply change the field "Email2Address" to "Email3Address" and run the script again.
[CODE]
[I]Dim objRecip
Dim mycontact' As ContactItem
Dim proxies
'On Error Resume Next
Set rootDSE=GetObject([/I][URL="ldap://RootDSE"][I]LDAP://RootDSE[/I][/URL][I])
DomainContainer = rootDSE.Get("defaultNamingContext")
'Open a connection to the Public Contacts public folder
Set myOlApp = CreateObject("Outlook.Application")
Set myNameSpace = myOlApp.Application.GetNamespace("MAPI")
Set myfolder = myNameSpace.Folders("Public Folders"). _
Folders("All Public folders").Folders("Public Contacts")
'Open a connection to Active Directory
Set conn = CreateObject("ADODB.Connection")
conn.Provider = "ADSDSOObject"
conn.Open "ADs Provider"
'Run through all the contacts in the public folder
For I = 1 To myfolder.Items.Count
If TypeName(myfolder.Items.Item(I)) = "ContactItem" Then
Set mycontact = myfolder.Items(I)
' If a contact has a second e-mail address find the first contact in Active Directory
' by using the first e-mail address
If (mycontact.Email2Address <> "") Then
LDAPStr = "<LDAP://" & DomainContainer & _
">;(&(objectCategory=contact)(mail=" _
& mycontact.Email1Address & "));adspath;subtree"
Set rs = conn.Execute(LDAPStr)
If rs.RecordCount = 1 Then
Set oContact = GetObject(rs.Fields(0).Value)
Set objRecip = oContact
'Add the second e-mail address to the contact if it is njot already a property of the contact
sAddress = "smtp:" & mycontact.Email2Address
bIsFound = False
vProxyAddresses = objRecip.ProxyAddresses
nProxyAddresses = UBound(vProxyAddresses)
nProxyAddress = 0
Do While nProxyAddress <= nProxyAddresses
If vProxyAddresses(nProxyAddress) = sAddress Then
bIsFound = True
Exit Do
End If
nProxyAddress = nProxyAddress + 1
Loop
If Not bIsFound Then
ReDim Preserve vProxyAddresses(nProxyAddresses + 1)
vProxyAddresses(nProxyAddresses + 1) = sAddress
objRecip.ProxyAddresses = vProxyAddresses
oContact.SetInfo
End If[/I]
[I] End If
End If
End If
Next
conn.Close[/I]
[/CODE]
[B]Converting Distribution Lists[/B]
Distribution lists are a very weak link in Outlook. Since Outlook is not really a directory per-se like Active Directory, there is usually some problem with keeping track of where the contacts that belong to the Distribution List exist. Also, when you do an import or export the reference to the contacts is deleted and all that is left is the e-mail address of the contact which is not updated.
Converting the Distribution list requires to create a Universal Distribution Group in Active Directory for each Distribution List and then look for the contacts that already exist in Active Directory, searching according to their e-mail address.
[CODE]
[I]Dim MyDl
Dim objRecip
Dim mailar(2)
' On Error Resume Next[/I]
[I] Set rootDSE=GetObject([/I][URL="ldap://RootDSE"][I]LDAP://RootDSE[/I][/URL][I])
DomainContainer = rootDSE.Get("defaultNamingContext")
Set fs = CreateObject("Scripting.FileSystemObject")
Set userFile = fs.CreateTextFile("c:\DLConvertReport.txt")
Set myOlApp = CreateObject("Outlook.Application")
Set myNameSpace = myOlApp.Application.GetNamespace("MAPI")
'Open a connection to the DLs public folder.
Set myfolder = myNameSpace.Folders("Public Folders"). _
Folders("All Public folders").Folders("DLs")[/I]
[I] FindContactinDLs = False
'Go through all the distribution lists in the folder
For I = 1 To myfolder.Items.Count
If TypeName(myfolder.Items.Item(I)) = "DistListItem" Then[/I]
[I] Set MyDl = myfolder.Items(I)
' Set the Type of Group as Universal Distribution Group [/I]
[I] lGroupType = &H8 'ADS_GROUP_TYPE_UNIVERSAL_GROUP
' Create the Group[/I]
[I] Set objContainer = GetObject([/I][URL="ldap://OU=DLs,DC=company,DC=com"][I]LDAP://OU=DLs,DC=company,DC=com[/I][/URL][I])
strGroupName = MyDl.DLName
Set iAdGroup = objContainer.Create("group", "cn=" + strGroupName)
' Create a login name for the group that conforms to the NT4 standards
strSamAcctName = "DL" & Replace(strGroupName, " ", "")
strSamAcctName = Left(strSamAcctName, 12)
'Add a number at the end of login name of the group if it exists
n = 2
If LoginNameExists (strSamAcctName) Then _
strSamAcctName = strSamAcctName & "2"
Do While LoginNameExists (strSamAcctName)
n = n + 1
strSamAcctName = Left (strSamAcctName,12) & CStr (n)
Loop
iAdGroup.Put "sAMAccountName", strSamAcctName
iAdGroup.Put "groupType", lGroupType
userFile.WriteLine "Creating " & strGroupName
' Flush to the directory
iAdGroup.SetInfo[/I]
[I]'Mail Enable
Set iMailGroup = iAdGroup
iMailGroup.mail = strSamAcctName & "@company.com"
iMailGroup.MailEnable[/I]
[I]' Write Exchange information to the directory.
iAdGroup.SetInfo
' Look for members of the distribution list in Active Directory
For y = 1 To MyDl.MemberCount
Set DLMember = MyDl.GetMember(y)
WScript.Echo DLMember.Name & " " & DLMember.Address
If DLMember.Address <> "" Then
contactMail = MyDl.GetMember(y).Address
recipient =
Set conn = CreateObject("ADODB.Connection")
conn.Provider = "ADSDSOObject"
conn.Open "ADs Provider"[/I]
[I] ldapStr = "<LDAP://" & DomainContainer & _
">;(&(&(objectCategory=contact)(!extensionAttribute1=ShowInGAL)" & _
"(&(&(& (| (&(objectCategory=person)(objectClass=contact))" & _
")))(objectCategory=contact)(proxyAddresses=smtp:" & _
CStr(contactMail) & "))));adspath;subtree"[/I]
[I] Set rs = conn.Execute(ldapStr)
'If contact is found add it to the corresponding Universal Group [/I]
[I] If Not rs.EOF Then
Set oContact = GetObject(rs.Fields(0).Value)
path = oContact.ADsPath
If Not (iAdGroup.IsMember(path)) Then
userFile.WriteLine " Adding Contact " & path
iAdGroup.Add path
iAdGroup.SetInfo
End If
End If
Else
'If member is a Distribution list itself, look for it in Active Directory
'and add it to the Universal Group
DLName = MyDl.GetMember(y).Name
Set conn = CreateObject("ADODB.Connection")
conn.Provider = "ADSDSOObject"
conn.Open "ADs Provider"[/I]
[I] ldapStr = "<LDAP://" & DomainContainer _
& ">;(&(&(&(& (mailnickname=*) (| (objectCategory=group) )))(objectCategory=group)(displayName=" & DLName & ")));adspath;subtree"[/I]
[I] Set rs = conn.Execute(ldapStr)[/I]
[I] If Not rs.EOF Then
Set oUDG = GetObject(rs.Fields(0).Value)
path = oUDG.ADsPath
userFile.WriteLine " Adding DL " & path
If Not (iAdGroup.IsMember(path)) Then
iAdGroup.Add path
iAdGroup.SetInfo
End If
End If
End If
Next
End If
Next[/I]
[I] Function LoginNameExists (login)
'Check to see if login name already exists in Active Directory
LoginNameExists = False
Set rootDSE=GetObject([/I][URL="ldap://RootDSE"][I]LDAP://RootDSE[/I][/URL][I])
DomainContainer = rootDSE.Get("defaultNamingContext")
Set conn = CreateObject("ADODB.Connection")
conn.Provider = "ADSDSOObject"
conn.Open "ADs Provider"
WScript.Echo login
ldapStr = "<LDAP://" & DomainContainer & _
">;(& (sAMAccountName=" & login & ") );adspath;subtree"
Set rs = conn.Execute(LDAPStr)
If rs.RecordCount = 1 Then LoginNameExists = True
conn.Close
End Function [/I]
[/CODE]
[B]Conclusion[/B]
If the scripts look tricky to you, they are easy to modify to match your Active Directory and e-mail domain. On the other hand, once you learn to master scripting Active Directory and Exchange, the true power of these scripts will reveal itself. The great thing about using a script rather than say a wizard, even a well thought out one like the Outlook Import and Export one is that you get almost absolute flexibility. You can write almost any rule to eliminate unwanted contacts during the migration process. You can decide on whatever naming standard for contacts you choose and make it as complex or as simple as you would like. You can create different contacts in different folders according to any criteria that you choose. The sky is really the limit when it comes to the power of scripting.
[/LEFT]
[LEFT][CODE]http://technet.microsoft.com/en-us/library/bb727091.aspx[/CODE]
[B]Step-by-Step Guide to Bulk Import and Export to Active Directory
[/B]This guide introduces batch administration of the Active DirectoryTM service, using both the LDAP Data Interchange Format (LDIF) utility and a simple program you can write using the Visual Basic® Scripting Edition (VBScript) development system. Using these tools, you can export, import, and modify objects such as users, contacts, groups, servers, printers, and shared folders.
[B]On This Page[/B]
[URL="http://technet.microsoft.com/en-us/library/bb727091.aspx#EDAA"] [/URL] [URL="http://technet.microsoft.com/en-us/library/bb727091.aspx#EDAA"]Introduction[/URL]
[URL="http://technet.microsoft.com/en-us/library/bb727091.aspx#ECAA"] [/URL] [URL="http://technet.microsoft.com/en-us/library/bb727091.aspx#ECAA"]Using the LDIFDE Utility[/URL]
[URL="http://technet.microsoft.com/en-us/library/bb727091.aspx#EBAA"] [/URL] [URL="http://technet.microsoft.com/en-us/library/bb727091.aspx#EBAA"]Using VBScript and ADSI[/URL]
[URL="http://technet.microsoft.com/en-us/library/bb727091.aspx#EAAA"] [/URL] [URL="http://technet.microsoft.com/en-us/library/bb727091.aspx#EAAA"]Important Notes[/URL]
[B]Introduction[/B]
In this guide, you will perform the following tasks:
[LIST][*] [B]Perform batch operations using the LDIFDE utility[/B]. Export users from the Marketing organizational unit (OU) in the Reskit domain into a file format compatible with the LDIF standard format. Perform a batch modification of all the users in the Marketing OU. Use LDIF to create a new user and delete a user.[*] [B]Perform batch operations using ADSI and VBScript[/B]. Export users from the Marketing OU in the Reskit domain into a text file, using a script written with ADSI and VBScript. Use VBScript to perform a batch modification of all the users in the Marketing OU. Use VBScript to create a new user and delete a user.[/LIST]
[B]Requirements and Prerequisites[/B]
You must install the Windows 2000 Server operating system, including Active Directory, on a server in your network. You can then run the Administration Tools from the server or from a workstation running the Windows 2000 Professional operating system.
This step-by-step guide assumes that you have run the procedures in A Common Infrastructure for Windows 2000 Server Deployment Step-by-Step [URL="http://www.microsoft.com/windows2000/techinfo/planning/server/serversteps.asp"]Part 1[/URL].
The common infrastructure documents specify a particular hardware and software configuration. If you are not using the common infrastructure, you need to make the appropriate changes to this document. For the latest information about hardware requirements and compatibility for servers, clients, and peripherals, see the Windows 2000 Product Compatibility search page ([URL]http://www.microsoft.com/windows2000/server/howtobuy/upgrading/compat/default.asp[/URL]).
The Administration Tools are installed by default on all Windows 2000-based domain controllers. The LDIFDE utility described in this guide is installed by default on servers, and can be copied to any Windows 2000-based workstation. The VBScript programs that you create can be run from either servers or workstations.
For all procedures in this guide, you must be logged on as an administrator. If you log on using an account that does not have administrative privileges, you may not be able to perform export and import operations in Active Directory.
[URL="http://technet.microsoft.com/en-us/library/bb727091.aspx#mainSection"] [/URL] [URL="http://technet.microsoft.com/en-us/library/bb727091.aspx#mainSection"]Top of page[/URL]
[B]Using the LDIFDE Utility[/B]
The LDAP Data Interchange Format (LDIF) is an Internet draft standard for a file format that can be used for performing batch operations on directories that conform to the LDAP standards. LDIF can be used to export and import data, allowing batch operations such as Add, Modify, and Delete to be performed in Active Directory. A utility called LDIFDE is included in the Windows 2000 operating system to support batch operations based on the LDIF standard.
[B]Using LDIF to Export All Objects in the Marketing OU[/B]
You can use LDIFDE to export all objects in the Marketing organizational unit (OU), created in " [URL="http://www.microsoft.com/windows2000/techinfo/planning/server/serversteps.asp"]Step-by-Step Guide to Common Infrastructure Part 1[/URL]". This example searches the organizational unit for certain objects and creates a file containing the names of those objects.
[B]To export all objects in the Marketing OU [/B]
[LIST=1][*] Click [B]Start[/B], point to [B]Programs[/B], then point to [B]Accessories[/B], and click [B]Command Prompt[/B].[*] At the command prompt, type:
ldifde -f marketing.ldf -s hq-res-dc-01-d"ou=Marketing,dc= reskit,dc=com"-psubtree–r"(objectCategory=CN=Person,CN=Schema,CN=Configuration,DC=reskit,DC=com)"[/LIST]
This creates a LDIF file named [I]Marketing.ldf[/I], by connecting to the server named [I]HQ-RES-DC-01 [/I]and executing a subtree search of the Marketing OU for all objects of the category [I]Person[/I]. (See Figure 1 below.)
Note that [I]objectCategory [/I]is an indexed attribute designed to enhance search performance.
[URL="http://technet.microsoft.com/en-us/library/Bb727091.bulkst01_big%28en-us,TechNet.10%29.gif"] [IMG]http://i.technet.microsoft.com/Bb727091.bulkst01%28en-us,TechNet.10%29.gif[/IMG][/URL]
[B]Figure 1: Creating an LDF file[/B]
You can use this LDIF file to perform a batch import of all the objects from the Marketing OU into any other LDAP-compatible directory. Some attributes may not be applicable to other implementations of LDAP. In particular, if you use this mechanism to import the objects into another Active Directory, some attributes must be omitted because they are automatically generated during object creation. (If they are not specifically omitted, the operation will fail.)
For example, the LDIFDE command that is used to omit these attributes is:
ldifde -f marketing.ldf -s hq-res-dc-01 d
"ou=Marketing,dc= reskit,dc=com"–r
>"(objectCategory=CN=Person,CN=Schema,CN=Configuration,DC=reskit,DC=com)" –m
[B]Using LDIF to Modify All Objects in the Marketing OU[/B]
In this example, the entire Marketing organization has moved to a new office address. You use LDIF to perform a batch modification for all user objects in the Marketing organization by altering the state, street, locality, and postal code attributes.
[B]To modify all objects in the Marketing OU [/B]
[LIST=1][*] Click [B]Start[/B], point to [B]Programs[/B], then point to [B]Accessories[/B], and click [B]Command Prompt[/B].[*] At the command prompt, type the following command to extract the required entries:
ldifde -f marketing.ldf -s hq-res-dc-01-d"ou=Marketing,dc= reskit,dc=com"-psubtree–r"(objectCategory=CN=Person,CN=Schema,CN=Configuration,DC=reskit,DC=com)" –l "l,st,streetAddress, postalCode"[*] Use a text editor such as Notepad to edit the LDIF file, Marketing.ldf. (Save the file as an .ldf file.) Modify each entry so that it is similar to that shown in Figure 2 below.
[URL="http://technet.microsoft.com/en-us/library/Bb727091.bulkst02_big%28en-us,TechNet.10%29.gif"] [IMG]http://i.technet.microsoft.com/Bb727091.bulkst02%28en-us,TechNet.10%29.gif[/IMG][/URL]
[B]Figure 2: Editing attributes for a move[/B] [*] Run [B]LDIFDE [/B]to import the modifications into Active Directory. At the command prompt, type the following command, and then press [B]> Enter[/B]. (See Figure 3 below.)
ldifde –i -f marketing.ldf -s hq-res-dc-01
[URL="http://technet.microsoft.com/en-us/library/Bb727091.bulkst03_big%28en-us,TechNet.10%29.gif"] [IMG]http://i.technet.microsoft.com/Bb727091.bulkst03%28en-us,TechNet.10%29.gif[/IMG][/URL]
[B]Figure 3: Importing modifications into the Active Directory[/B] [*] To confirm that the entries have been modified, check the [B]Active Directory Users and Computers [/B]snap-in. (For help with using this snap-in, see the [URL="http://technet.microsoft.com/en-us/library/bb742437.aspx"]Step-by-Step Guide to Managing the Active Directory[/URL]. )[/LIST]
For further information on using LDIFDE, type [B]LDIFDE /? [/B]at the command prompt.
[B]Note:[/B] Another utility called CSVDE performs the same export functions as LDIFDE, but uses a comma-separated file format. Import operations with CSVDE are "add" only, and CSVDE does not offer the ability to modify or delete objects. The CSV file format is supported by applications such as Microsoft Excel.
[B]Using LDIF to Create a New User[/B]
In this example, you use LDIF to add a new user named James Smith to the Marketing organizational unit.
[LIST=1][*] Start a text editor, such as Notepad, and create a new text file named [B]Newuser.ldf[/B]. (Save the file as an ldif file, not as a text file.)[*] Edit the LDIF file Newuser.ldf, and add the following text (see Figure 4 below):
dn: CN=JamesSmith,OU=Marketing,DC=reskit,DC=com
changetype: add
cn: James Smith
objectClass: user
samAccountName: James
> givenName: James
> sn: Smith[*] Save and close the LDIF file.[*] Run LDIFDE to import the new user into Active Directory. On the [B]Start [/B]menu, point to [B]Programs[/B], then point to [B]Accessories[/B], and click [B]Command Prompt[/B]. Type the following command, and then press [B]Enter[/B].
ldifde –i -f newuser.ldf -s hq-res-dc-01[*] To confirm that the new user has been created, check the [B]Active Directory Users and Computers [/B]snap-in.
[URL="http://technet.microsoft.com/en-us/library/Bb727091.bulkst04_big%28en-us,TechNet.10%29.gif"] [IMG]http://i.technet.microsoft.com/Bb727091.bulkst04%28en-us,TechNet.10%29.gif[/IMG][/URL]
[B]Figure 4: Adding a new user to the Marketing OU[/B] [/LIST]
[B]Using LDIF to Delete a User[/B]
In this example, you use LDIF to remove the user named James Smith from the Marketing OU.
[LIST=1][*] Start a text editor such as Notepad, and create a new file named [B]Deluser.ldf[/B].[*] Edit the LDIF file Deluser.ldf, and add the following text.
dn: CN=JamesSmith,OU=Marketing,DC=reskit,DC=com
changetype: delete
[IMG]http://i.technet.microsoft.com/Bb727091.bulkst05%28en-us,TechNet.10%29.gif[/IMG]
[B]Figure 5: Remove James Smith from OU[/B] [*] Run LDIFDE to delete the user from Active Directory. At the command prompt, type the following command, and then press [B]Enter[/B].
ldifde –i -f deluser.ldf -s hq-res-dc-01[*] To confirm that the user has been deleted, check the [B]Active Directory Users and Computers [/B]snap-in.[/LIST]
[URL="http://technet.microsoft.com/en-us/library/bb727091.aspx#mainSection"] [/URL] [URL="http://technet.microsoft.com/en-us/library/bb727091.aspx#mainSection"]Top of page[/URL]
[B]Using VBScript and ADSI[/B]
Active Directory Services Interfaces (ADSI) makes it easy to develop directory-enabled applications. In conjunction with the Windows Script Host, batch directory operations can be scripted using VBScript or Jscript® development software. In this guide, the procedures that were described in the previous section (which used LDIF) are performed using simple applications written in VBScript.
Please note that these scripts do not include any error checking, nor are they meant to provide a programmer's reference to VBScript and ADSI. All of the examples included here assume you are logged on with the proper credentials on a machine that is a member of the target domain. It is possible in ADSI to explicitly specify credentials and a target domain. For more information on this, see the documentation on ADSI's OpenDSObject in the Platform SDK ([URL]http://msdn.microsoft.com/downloads/sdks/platform/platform.asp[/URL]).
After each procedure, confirm that the entries have been modified by checking the [B]Active Directory Users and Computers[/B] snap-in.
[B]Using VBScript to Export All Objects in the Marketing OU[/B]
In this example, you use a text editor such as Notepad to create a VBScript program. The script searches the Marketing OU and creates a text file that lists all of the user objects and a subset of their attributes.
[B]To create the export script [/B]
Copy the following text into your text editor:
[CODE]
'Global variables
Dim oContainer
Dim OutPutFile
Dim FileSystem
'Initialize global variables
Set FileSystem = WScript.CreateObject("Scripting.FileSystemObject")
Set OutPutFile = FileSystem.CreateTextFile("marketing.txt", True)
SetoContainer=GetObject("LDAP://OU=marketing,DC=reskit,DC=com")
'Enumerate Container
EnumerateUsers oContainer
'Clean up
OutPutFile.Close
Set FileSystem = Nothing
Set oContainer = Nothing
WScript.Echo "Finished"
WScript.Quit(0)
Sub EnumerateUsers(oCont)
Dim oUser
For Each oUser In oCont
Select Case LCase(oUser.Class)
Case "user"
If Not IsEmpty(oUser.distinguishedName) Then
OutPutFile.WriteLine "dn: " & oUser.distinguishedName
End If
If Not IsEmpty(oUser.name) Then
OutPutFile.WriteLine "name: " & oUser.Get ("name")
End If
'need to do this because oUser.name would get back the Relative
Distinguished name (i.e. CN=Jo Brown)
If Not IsEmpty(oUser.st) Then
OutPutFile.WriteLine "st: " & oUser.st
End If
If Not IsEmpty(oUser.streetAddress) Then
OutPutFile.WriteLine "streetAddress: " & oUser.streetAddress
End If
Case "organizationalunit" , "container"
EnumerateUsers oUser
End Select
OutPutFile.WriteLine
Next
End Sub
[/CODE]
[LIST=1][*][*] Save the file as [B]Export.vbs[/B].[*] At the command prompt type [B]export.vbs [/B]and press [B]Enter[/B]. This creates a file named [I]Marketing.tx[/I]t, which contains a list of users and some of their attributes, such as distinguished name, name, state, and street address.[/LIST]
With appropriate modification, this script can be used with any application that supports COM and Visual Basic technologies. Such applications include Microsoft Visual Basic, Microsoft Excel, and Microsoft Access. Scripting can also be hosted by Internet Explorer and Internet Information Services 5.0, which is part of Windows 2000 Server.
[B]Using VBScript to Modify All Objects in the Marketing OU[/B]
In this example, the Marketing organization has moved to a new office address. A simple VBScript program is used to perform a batch modification for all user objects in the Marketing organization. The script alters the state, street, locality, and postal code attributes.
[LIST=1][*] Copy the following text into your text editor:
[CODE]Dim
oContainer Set oContainer=GetObject("LDAP://
OU=marketing,DC=reskit,DC=com")
ModifyUsers oContainer
'cleanup
Set oContainer = Nothing
WScript.Echo "Finished"
Sub ModifyUsers(oObject)
Dim oUser
oObject.Filter = Array("user")
For Each oUser in oObject
oUser.Put "st","New York"
oUser.Put "streetAddress","825 Eighth Avenue"
oUser.Put "postalCode","10019"
oUser.Put "l","New York"
oUser.SetInfo
Next
End Sub
[/CODE][*][*] Save the file as [B]Modify.vbs[/B].[*] At the command prompt, type [B]modify.vbs [/B]and press [B]Enter[/B]. This processes all objects in the Marketing organizational unit and modifies all users, altering the state, street address, postal code, and locality attributes.[/LIST]
[B]Using VBScript to Create a User Object in the Marketing OU[/B]
In this example, you use VBScript to add a new user to the Marketing organization. This example illustrates how easy it is to use ADSI and VBScript to programmatically access the directory. Note that in this example, only a limited set of attributes are configured during the user creation.
[B]To create the script and add the user [/B]
[LIST=1][*] Copy the following text into your text editor:[/LIST]
[CODE]
Dim oContainer 'Parent container
of new user Dim
oUser 'Created user
'Get parentcontainerSetoContainer=GetObject("LDAP://OU=marketing,
DC=reskit,DC=com")
'Create user
Set oUser = oContainer.Create("User","CN=Jo Brown")
'Assign properties values to user
oUser.Put "samAccountName","Jo"
oUser.Put "givenName","Jo"
oUser.Put "sn","Brown"
oUser.Put "userPrincipalName","jo@reskit.com"
oUser.SetInfo
'Clean up
Set oUser = Nothing
Set oContainer = Nothing
WScript.Echo "Finished"
[/CODE]
[LIST=1][*][*] Save the file as [B]Adduser.vbs[/B].[*] At the command prompt, type [B]adduser.vbs [/B]and press [B]Enter[/B]. This creates a new user named [B]Jo Brown [/B]in the Marketing OU.[/LIST]
[B]Using VBScript to Delete a User[/B]
In this example, you use VBScript to delete a user from the Marketing organization.
[LIST=1][*] Copy the following text into your text editor:[/LIST]
[CODE]
Dim oContainer 'Parent container of object to be
deleted 'Get parent
container Set oContainer=GetObject("LDAP://OU=marketing,
DC=reskit,DC=com")
'Delete user
oContainer.Delete "user","CN=Jo Brown"
'Clean up
Set oContainer = Nothing
WScript.Echo "Finished"
[/CODE]
[LIST=1][*][*] Save the file as [B]Deluser.vbs[/B].[*] At the command prompt, type [B]deluser.vbs [/B]and press [B]Enter[/B]. This deletes the user Jo Brown from the Marketing OU.[/LIST]
[B]Important Notes[/B]
The example company, organization, products, people, and events depicted in these step-by-step guides are fictitious. No association with any real company, organization, product, person, or event is intended or should be inferred.
This common infrastructure is designed for use on a private network. The fictitious company name and DNS name used in the common infrastructure are not registered for use on the Internet. Please do not use this name on a public network or Internet.
The Active Directory service structure for this common infrastructure is designed to show how Windows 2000 features work and function with the Active Directory. It was not designed as a model for configuring an Active Directory for any organization–for such information see the Active Directory documentation.
[/LEFT]
[LEFT][CODE]http://www.computerperformance.co.uk/vbscript/vbscript_contact_create.htm[/CODE]
[B] Example 1 - Script to Create a Contact in Active Directory[/B]
[B]Prerequisites[/B]
Recommended: You logon as administrator, preferably at a domain controller. Remote Desktop would be a suitable alternative. If that is not possible, you could get these sample scripts to work from an XP machine as a non-administrator, but why introduce extra complications? At the beginning you want easy success, with fewest obstacles.
[B] Instructions for Creating a Contact in Active Directory[/B]
[LIST=1][*]You need access to a Windows Active Directory domain.[*]Copy and paste the example script below into notepad or a VBScript editor.[*]Decide what value to use for strContainer. Where is your spreadsheet?[*]Change the values of the variable strEmail to a Contact that you know.[*]Save the file with a .vbs extension, for example: contact[SIZE=1] [/SIZE].vbs[*]Double click contact[SIZE=1] [/SIZE].vbs. Open Active Directory Users and Computers and check the strContainer container for strContactName. If necessary, 'Refresh' the contents of your OU.[/LIST]
[B]Script to Create a Contact in your Active Directory[/B]
[CODE]
[SIZE=1]' Contact .vbs
' Purpose VBScript to create a contact object in Active Directory
' Author Guy Thomas http://computerperformance.co.uk/
' Version 1.3 - May 2005
' --------------------------------------------------------------'
Option Explicit
Dim objRoot, objOU, objDomain, objContact, strYourDescription
Dim strDNS, strContainer, strContactName, strEmail
' Set string variables
strContainer = "OU=Suppliers"
strContactName = "cn=MySupplier1"
strEmail = "supplier@supplyme.com"
strYourDescription = "Guy's Contact"
' Section to attach to Active Directory
Set objRoot = GetObject("LDAP://rootDSE")
strDNS = objRoot.Get("defaultNamingContext")
Set objDomain = GetObject("LDAP://" & strDNS)
' Section to create the contact
Set objOU = GetObject("LDAP://"& strContainer & "," & strDNS)
Set objContact = objOU.Create("contact", strContactName)
objContact.Put "Description", strYourDescription
objContact.Put "Mail", strEmail
objContact.SetInfo
Wscript.Echo "Look in " & strContainer & " for (F5) " & strEmail
' End of Sample Contact VBScript[/SIZE]
[/CODE]
[/LEFT]
[RIGHT]البته چون سوال شما مقداری گنگ است ، پیش خودم فکر کردم شاید منظورتان این کار است
[LEFT][CODE]http://support.microsoft.com/?scid=kb%3Ben-us%3B238007&x=8&y=6[/CODE]
[B]How to Configure the Address Book to Query Users Contained in Active Directory[/B]
The Address Book is the default search client that ships with Windows 2000 and Microsoft Internet Explorer 5. It is a high-level Lightweight Directory Access Protocol (LDAP) client, and LDAP does not support users specifying filters for a search. Instead, you can input the string for the filter and the Ambiguous Name Resolution (ANR) set is used
[B]Windows 2000 Considerations[/B]
When you install Windows 2000, the Address Book is configured to search a particular Active Directory server. You are not required to specify a Base Distinguished Name (BaseDN) or a server name. Setup configures the BaseDN and server name, and they are displayed as null.
To view Active Directory properties:
[LIST=1][*]Click [B]Start[/B], point to [B]Programs[/B], point to [B]Accessories[/B], and then click [B]Address Book[/B].[*]On the [B]Tools[/B] menu, click [B]Accounts[/B].[*]When the [B]Internet Accounts[/B] dialog box is displayed, you can add, remove, or modify an existing account by selecting the appropriate account, and then clicking [B]Properties[/B].[/LIST]
[B]NOTE[/B]: The [B]Server name[/B] and [B]Account name[/B] fields are displayed as null. The Locator service caches the actual server and account name. When you log on to a workstation, the Locator service attempts to find a domain controller. The name of the domain controller detected by the Locator service is used as the server name, and the account that you use to log on serves as the account name. [URL="http://support.microsoft.com/?scid=kb%3Ben-us%3B238007&x=8&y=6#top"][IMG]http://support.microsoft.com/library/images/support/kbgraphics/public/en-us/uparrow.gif[/IMG]Back to the top[/URL]
[B]Downlevel Client Considerations with the Address Book[/B]
Internet Explorer 5 is considered a downlevel client when it is installed on a computer running Microsoft Windows 98 or Microsoft Windows NT 4.0. To use the Address Book to search Active Directory, you must configure the following items:
[LIST][*]Server name[*]BaseDN[*]Account name (if not validating against Active Directory)[/LIST]
To configure the Address Book with downlevel clients:
[LIST=1][*]Install Internet Explorer 5 (if it is not currently installed).[*]Click [B]Start[/B], point to [B]Programs[/B], point to [B]Accessories[/B], and then click [B]Address Book[/B].[*]On the [B]Tools[/B] menu, click [B]Accounts[/B].[*]To add a new account, click [B]Add[/B]. This starts the Internet Connection wizard.[*]In the [B]Internet directory (LDAP) server[/B] box, type the name of an LDAP server (Windows 2000 domain controller). You can also type the domain name, but do not use the fully qualified domain name (FQDN) in either case.[*]Click [B]Next[/B], click [B]Next[/B], and then click [B]Finish[/B].[*]The account you just created is not displayed in the list. Click to select the account, and then click [B]Properties[/B].[*]Click to select the [B]This server requires me to log on[/B] check box.[*]In the [B]Account name[/B] box, type Domainname\Username, where Domainname is the name of your domain and Username is the user's name. In the [B]Password[/B] box, type the appropriate password.[*]On the [B]Advanced[/B] tab, the value displayed in the [B]Directory service (LDAP)[/B] box is 3268 by default (the global catalog port). If you clear the [B]Directory service (LDAP)[/B] box and click [B]Use Default[/B], the value changes to 389. If you use 389, you need to type data the [B]Search Base[/B] box (it should read DC=domainname,DC=com).
[B]NOTE:[/B] Port 3268 is recommended for most searches. Also, if you select the [B]This server requires a secure connection (SSL)[/B] check box on the [B]Advanced[/B] tab, the port number is changed to 636. If you are using port 636 to search, ensure that the [B]Search base[/B] box is populated with the correct base DN (that is, DC=domainname,DC=com).[*]Click [B]OK[/B] to save the changes.[/LIST]
To search for a user in Active Directory:
[LIST=1][*]Click [B]Start[/B], point to [B]Programs[/B], point to [B]Accessories[/B], and then click [B]Address Book[/B].[*]Click [B]Find People[/B].[*]In the [B]Look In[/B] box, click [B]Active Directory[/B] (for Windows 2000 clients) or the name you chose in step 5 above.[*]Type a user's name or e-mail address, and then click [B]Find Now[/B].[*]When the user account is displayed, you can view the user's properties or add the user to the Address Book.[/LIST]
For additional information, click the article number below to view the article in the Microsoft Knowledge Base: [URL="http://support.microsoft.com/kb/254610/EN-US/"]254610[/URL] ([URL="http://support.microsoft.com/kb/254610/EN-US/"]System Event ID 36876 When Using LDAP SSL Query of the Active Directory[/URL] ) System Event ID 36876 When Using LDAP SSL Query of the Active Directory
[/LEFT]
[/RIGHT]
