Editor's Note: This article is excerpted from this TID. Please check the actual TID before using this information, as the TIDs are occasionally updated after we have highlighted them here.
If you've ever wished you could create a GroupWise user with a specific File ID (FID) in order to access an archive or restore a deleted user, you will love this tip from Novell Technical Services.
If you need to recreate a GroupWise account but you also need a specific FID so the user can open an archive or use a restore area and recover mail, you have a couple of options. You can import the user with the correct FID by importing them in to GroupWise. See TID How to import a user with their FID into GroupWise.
OR you can create the GroupWise user and then, before the user logs in to GroupWise, modify the FID on the new user.
Follow these steps to create a new user with a specified FID number.
First you will need to create a new user account in GroupWise using any user name / user ID you choose. You may already have the NDS user account and do not have to delete this account but rather just add a GroupWise account to it. If the NDS user already has a GroupWise account you can either disassociate the GroupWise account from it or delete just the GroupWise account from the NDS user.
Do not log in to the account via the GroupWise client. Follow the steps below before allowing the user to log in to GroupWise in order to change the FID of the existing user to a specified FID.
To change the FID for the user:
When the user logs in for the first time you may encounter error C067 or C05D if the user was not deleted completely.
The C05D and C067 errors are flip sides of the same coin. The C05D error indicates that the database in question is registered in the Guardian database but is not on disk. The C067 indicates that the database in question is found on disk but is not registered in the guardian database. In both cases the POA is not able to resolve the problems on its own so manual intervention is needed.
If you need to rename a GroupWise database always use .old (userxxx.old) rather the userxxxold.db. Renaming a file and using a .db extension will result in the file being adopted in to the ngwguard.db when a contents check is run, so when renaming always ensure that the .db extension is removed.
If you encounter the following errors C067 or the C05D please see TID 10074228
This solution does not work for an External GroupWise Entity as NGW: FileID does not display in the Other tab. The external could be converted to a full NDS user with a GroupWise account temporarily to perform this step.
To edit the FID on an existing archive to be opened by a user with a different FID you may use the following tools: Archive FID editor - TID10014261, or the GUI wrapped version with a seven day trial offered FIDIt by Email Essentials Inc.
To restore mail for the user whose mail and or account was accidently deleted see How to set up a restore area
I was very interested when I saw this article referenced in a recent issue of GroupWise Cool Solutions. However, after taking a look I see that the TID most of this is copied from is a year old and is only associated with GroupWise 6.5 and some earlier versions. The command line Archive FID editor TID says it is for versions lower than GW 7 and the link to FIDIt by Email Essentials brings you to a page that says the product is no longer distributed or supported by email essentials. So does either the archive FID renaming or the GroupWise account FID renaming work on GW 7 or is there a way to do the same things for GW 7? Thanks.