Article ID: 155414
Article Last Modified on 10/28/2006
By default, the Microsoft Exchange Administrator program does not export all of the data fields associated with a mailbox, custom recipient, or DL. If you need a particular field that is not exported by default, the following are your two available methods:
You can use the Bulk Import program to modify attributes associated with
mailboxes, custom recipients, and DLs. To modify the value of an
attribute, export the existing data to a .CSV file, change the value of
the attributes in the data file, and import the file. All existing
objects will be modified with the new values.
Each mailbox, custom recipient, and DL has 10 Custom Attributes that the
administrator can use to specify custom data. These Custom Attributes
can also be modified using the Directory Import program. There are 10
Custom Attributes which are named "Custom Attribute 1" through "Custom
Attribute 10".
To change the value of a particular Custom Attribute for mailboxes,
follow these steps (for Custom Attribute 1):
When you import data into a Custom Attribute, the following error is received:
This error might be received if the Custom Attribute 1 has been renamed.
Please refer to the following Microsoft Knowledge Base articles:
152854 XADM: Using Bulk Import to Remove Data
152727 XADM: Importing Blank Value Won't Modify Mailbox Value
By default, the Secondary E-mail (Proxy) addresses are not exported. For
information about how to export these addresses, please refer to the
following Microsoft Knowledge Base article:
153028 XADM: How to Export Multiple (Secondary) E-mail Addresses
The following Microsoft Knowledge Base article describes how to
associate more than one E-mail address with a mailbox:
148339 XADM: How to Import Multiple SMTP Addresses
The following Microsoft Knowledge Base article describes a possible
reason why the export only contains header fields:
147854 XADM: Custom Recipients DIR Export Creates Headers-Only CSV
The directory import/export can be run from the command line and,
therefore, can be run as part of a batch process. For more information
on running import/export from the command line, please refer to
Microsoft Exchange Administrator's Guide, pages 479-487.
Please refer to the following Microsoft Knowledge Base article:
152472 XADM: How to Specify a Tab or Space as Separator in .csv File
The following Microsoft Knowledge Base article provides more information
about the ExportObject setting:
152300 XADM: ExportObject in Command-Line Export Options File Only
The following Microsoft Knowledge Base article describes how to perform
a command line Directory Export of the Global Address List (GAL) using
the Microsoft Exchange Administrator program:
149447 XADM: How to Perform a Directory Export of the GAL
Microsoft Excel has a limit of 255 characters per cell. When you open a
.CSV file containing DL data, it is very likely that the Members field,
which contains the members of the DL, will be larger than 255 characters
in length. If you use Microsoft Excel to modify the data in the .CSV
file, when you save the file any field with more than 255 characters
will be truncated. This could cause problems when this data is imported
back into the Microsoft Exchange system via the Directory Import
command. It is possible that the members of large DLs will not have all
the original members that were present when the data was exported. It is
also likely that sending mail to these DLs will generate errors.
When you use the Directory Export command interactively from the
Microsoft Exchange Administrator program, there is an Include
Subcontainers check box on the Directory Export dialog. If this check
box is set, subcontainers of the selected container will be exported.
When you run the Directory Export program from the command line, there
is a setting in the Export Options file that you need to be set:
[Export]
Subcontainers=Yes
When you import data from a .CSV file, the following error might be received in the Event Log:
As the error message indicates, this error is generated if the data supplied in the .CSV file is incomplete. In other words, if there are 10 fields specified in the header of the file, each record in the file should have 10 data fields, even if the fields are empty. This problem can easily occur if commas are missing from a line in the .CSV file. It may not be possible to detect this problem by viewing the data in Microsoft Excel because Microsoft Excel does not display the data delimiters (commas, in this case). You will need to update the .CSV file using a text editor like Notepad.Additional query words: faq
Keywords: kbhowto kbusage KB155414