The Directory Exporter has been ran and produced the csv files but the NdsUsername column has not been populated.
The NdsUserName is pulled from the Network ID property of the Groupwise Address Book.
If the Network ID is not an available field in the Groupwise Address Book, or if it is available but is empty, then the NdsUserName will not be populated.
Copy the userID column within the csv file into the ndsusername colum within the userstomigrate.csv file. This is because these two fields are almost always the same value.
To make the Network ID an available field in the GroupWise Address Book:
1- Right-click the GroupWise Domain in ConsoleOne and select Properties
2- Select the Address Book option under the GroupWise tab
3- Move the Network ID field to the side that makes it available in the GroupWIse Address Book. In ConsoleOne , this is the 'address Book Fields' side.
4- Click Apply and then OK
The GroupWise client should be restarted at this point to verify that the Network ID field is now available.
The NDS Username field is populated by the Directory Export process, and extracted from the Network ID field in the Groupwise address book. The Network ID field is automatically generated when a user object is created in NDS. This attribute is then replicated to the Groupwise directory.
Guidelines for running Directory Exporter against multiple environment post offices:
For environments with multiple post offices, the following steps are recommended when performing a directory export:
1. Open the Groupwise Client and connect to the first post office.
2. Close the Groupwise Client. This should save certain registry settings, locking the client into opening up in the above post office the next time it is started.
3. Run the directory export. This should populate the ndsusername field for all objects in the post office that the Groupwise client was last connected to.
4. Open the userstomigrate file and sort by post office, and delete any rows that belong to other post offices, while also noting that the ndsusername fields are populated correctly for the post office in question. Save the file.
5. Open the Groupwise Client again and connect to the second post office to be processed. Close the client.
6. Run the directory exporter again. This time, the objects in the previous run should still be intact. However, objects in the second post office will now also have the ndsusername field populated.
7. Repeat the above steps for each post office in the environment until all the ndsusername fields are populated. This should provide a complete users to migrate file which can then be used successfully to migrate all objects.