![]() |
|
|
| Become a Columnist Microsoft Exchange Site Microsoft Support SiteMSDN Exchange Site | ||
|
|
How to create a mailbox in Exchange 2000 Server using LDIF In
Exchange 5.5 you could use the tool Header.exe to create a header file for a csv
file. After this you could use the csv file to automatically import users in
your Exchange Server and so create multiple mailboxes at a time. For those that
have been looking for it … sorry but Exchange 2000 Server does not support the
CSV file any longer and now relies on the tool LDIF. Well you can do the same
with the LDIF format as you did before with the csv file although it is a little
bit harder to do. Below is a sample script to create an user in the Windows 2000
Active Directory and create a mailbox for this user. This user is named John Doe
and works for company.com dn:
CN=John Doe,CN=Users,DC=company,DC=com changetype:
add cn:
John Doe objectClass:
user samAccountName:
John givenName:
John sn:
Doe userAccountControl:
512 userPrincipalName:
john mail:
john@company.com mailNickname:
John homeMDB:
CN=Test,CN=First Storage Group,CN=InformationStore,CN=Servername,CN=Servers,CN=First
Administrative Group,CN=Administrative Groups,CN=company,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=company,DC=nl mDBUseDefaults:
TRUE proxyAddresses:
SMTP:John@company.com proxyAddresses:
X400:c=us;a= ;p=Company;o=Exchange;s=Doe;g=John Here
are a few short explanations for the above: Dn:
fully distinguished name Changetype:
very important .. you can either put here add, delete or modify Cn:
Common name UserAccountControl:
513 is used to create a mail enabled user in combination with mailNickname MailNickname:
the mailbox alias ProxyAddresses:
use these to create additional addresses. I’ll
continue to work on this document so keep checking it out J Till
later, Martin |
|
|
|
Disclaimer: Your use of the information contained in these pages is at your sole risk. All information on these pages is provided "as is", without any warranty, whether express or implied, of its accuracy, completeness, fitness for a particular purpose, title or non-infringement, and none of the third-party products or information mentioned in the work are authored, recommended, supported or guaranteed by Pro Exchange. OutlookExchange.Com and Pro Exchange shall not be liable for any damages you may sustain by using this information, whether direct, indirect, special, incidental or consequential, even if it has been advised of the possibility of such damages.
© Copyright Pro Exchange, Inc., 2006