The PCs that it doesn't work on - do you have group policies applied that may be preventing making registry changes?
By Bryan Keadle
We have a single image for our Standard Load. We use this program to "import" the user's NDS information into the registry so that the user information correctly reflects the user information stored in NDS.
This program simply reads the user attributes: "Given Name", "SurName", and "Initials", converts them to the binary equivalent and populates the registry entries. We run this once per user, upon login.
It is particularly important to set these values to the user so that when users try to open a file from the network that is being used by another user, Office will report correctly which user has the file open instead of the generic user "Information Systems" that is contained within our standard load image.
This tool is set to find version 8.0 - 11.0, that is, through Office 2003; though only tested on Office 2000 and Office 2003.
SYNTAX: OfficeUserInformation (RESET / QUIET)
RESET - Clears out the Office User Information settings in the registry. Next time a user launches an Office product, they'll be prompted for the information
QUIET - Suppress any confirmation window boxes
OfficeUserInformation looks at the environment variable, NWUSERNAME, to determine the Novell Network login name. This should automatically be set if your are using the Novell client.
If you would like to use a different environment variable to resolve the Novell username, you may create an OfficeUserInformation.INI file, place it in the same directory as the executable, and define which environment variable to use. For example, if you have an environment variable, LN, that is the Novell username, create an INI with this content:
OfficeUserInformation will use the LN environment variable for the Novell user object to retrieve the NDS attributes.