GroupWise Nickname Import (GWNI)
Novell Cool Solutions: Cool Tool
Allows for the mass importing of GroupWise Nicknames.
|Posted:||26 Jan 2007|
Please read the note from our friends in legal before using this file.
GWNI allows for the mass importing of GroupWise Nicknames. It currently only allows importing of nicknames into a user's home post office and sets the nickname to system visibility (both of which can be changed in ConsoleOne). I may add the ability to import nicknames into other domains/post offices as well as the visibility setting if there is a need for it. The primary reason this program was written was to support Microsoft Exchange to Novell GroupWise migrations where an account name change was occurring and the old names needed to be maintained for a period of time.
Last Update: 7/12/2005
GroupWise Nickname Import (GWNI) is a utility which allows for quick and easy import of Nicknames into a GroupWise system. It reads a comma-separated variable (CSV) file and imports nicknames for a user into their home post office. While nicknames can be added for a user in other post offices and domains, GWNI currently only imports nicknames into the user's home post office. Future versions may include the ability to specify domain and post office if such a demand exists. The visibility of the nickname is currently set to "System" and the given name, last name, and expiration date are left blank. This tool was primarily written for use during a Microsoft Exchange to Novell GroupWise migration where there was a change of IDs occurring and support of the old IDs was needed on a temporary basis.
This tool is written in Visual Basic .NET and requires the Microsoft. Net Framework version 1.1 or higher. This can be obtained at www.microsoft.com. In addition, the following are also required:
- Novell Client for Windows
- GroupWise Client for Windows
This program has been tested with GroupWise 6.5 and 7.0. However, it should work with any GroupWise system back to at least version 5.5 EP and any eDirectory version back to the original eDirectory 85.
In addition to the above software requirements, the user running the tool must have FULL file rights to the domain directory and proper administrative rights in eDirectory to modify accounts.
Simply unzip the archive into a directory. The Interop DLL must be in the same directory as the executable.
4. Import File
The import file must be in a CSV format and must have the following fields:
A sample file, sampledata.csv, is included.
Prior to launching GWNI, the workstation should be logged into eDirectory with a drive mapped to a GroupWise domain directory. GWNI must have access to WPDOMAIN.DB in order to function.
Once an import file has been successfully loaded, the "Nickname" button can be selected to begin the import. A status dialog will appear showing the current operation and any errors that have been encountered.
Updates can be found at www.weisberg.net