One of the methods of populating the grid with subscribers you wish to edit is browsing to a CSV file and loading those users based on their alias or extension number.  The format of the CSV file only needs to follow two rules:

 

1. The values need to be separated by commas.  Tab or CrLf or semicolon separated files will not be parsed correctly.
1. It needs to include a column header in the first line of “extension” and/or “alias”.  This is not case sensitive and can be padded on  the left or right (or both) with spaces.

 

For instance, a file that starts like this will be parsed without a problem:

 

first name, last name, home server, alias, fax number, extension, department, domain

Jeff, Lindborg, EXServer1, jlindborg,,Engineering, 2199, ENG_MAIN

John, Smith, Exserver7, jsmith,,,ENG_LAB

...

 

If the CSV file contains a column for both Extension and Alias, the extension column is used to search first.  If a match is not found then the alias column value will be used.

 

Each row of the CSV file will be read in and the corresponding column that contains “extension” (column #6 above) or “alias” in the first line (column #4 above) will be used to search for the subscriber.  If a match is found, that user will be added to the grid.  If more than one match is found for that extension (which should never happen) or alias, that row will be skipped  - no duplicate users will ever be added to the grid.  When the import is complete a dialog will pop up which will show the total number of rows read in from the file and how many of those users were added to the grid.

 

In the example above, the first row tells the parser that column #6 contains user’s extensions and column #4 contains the alias.  The next row would cause the parser to search for “2199” among all extensions for subscribers on the local box.  If no match is found, then it would fall back and look for “jlindborg” among all aliases for subscribers on the local box.  The 3rd row does not contain an extension so only a search for “jsmith” will be done among aliases for all subscribers on the local box.  

 

Again, only subscribers associated with the local Unity server will be loaded.  If you have multiple Unity servers in the same Exchange site, only those users associated with the local Unity server the BulkEdit tool is being run on will be loaded into the grid.