Ingressor's homepage

To understand the problems NK2 files can create in an Exchange environment you must first understand that the NK2 file caches outgoing email address data. It stores the recipients' Name, Alias (e-mail address or GAL reference), and if it is an Exchange record, the x500 or Distinguished Name information. A typical Exchange address would look like this: c=country code, o=organization, ou=organizational unit, cn=container or canonical name, cn=container or canonical name. A typical address might look like this:

In the above example "jdoe" is the actual recipient's name and would also be the Alias for jdoe.

When an employee attempts to send an e-mail to "jdoe" he would begin typing the first letter(Outlook 2003) or first three letters (Outlook XP) Outlook program will autocomplete the remainder of the recipient information, including the x500 address. The x500 address is not displayed but is included in the information that is sent to the Exchange server. The Exchange server then attempts to find the recipient based upon the information contained in the x500 address line.

Normally this will not create any difficulties unless server data differs from data found in the NK2 file. Possible causes for differences between the GAL and the NK2 data stores could be:

In the case of a difference between the two information stores the desktop version of Outlook will use the NK2 data if the entry has been selected using autocompletion. If the address is selected using autoresolution, the GAL entry will be used.

What can be done to prevent these discrepancies? One possible answer is to use a utility such as our Ingressor Exchange HelpDesk or Commander programs. The HelpDesk version will enable your staff to edit or delete any entries in the NK2 file, including changes to the x500 record. While the HelpDesk version is a wonderful tool for making occasional changes, it lacks the power to be automated. For this reason, we developed the Ingressor Commander (IC) program that operates as a command line driven executable program. One that can be called from within a user login script.

Where: -p = path to NK2 file

The most commonly used function is also the simplest. This string will find all values (such as a domain name) and delete the associated Exchange records. This function can be used to eliminate ANY record containing an unwanted data element. Note that no definition file is required. And, because this program is executed every time the user logs into their computer, it will continue to eradicate unwanted entries as long as you wish.

Ingressor.exe f:\Documents and Settings\User\Applications Data\Microsoft\Outlook\userprofile.nk2 -sd=OU=unwanteddomainname

The net effect of this function removes only those Exchange records containing the unwanted or old domain name while retaining valuable SMTP, MAPIPDL, FAX and desired EX records.

	-s = search string (If not using a definition file)
	-r = replace string (If not using a definition file)
	-d = delete ( A file containing search and replace values separated by a comma)
	-l(L) = logfile name
	-sd = search and delete value

If a single search and replace is required, the -s and -r switches can be used. If you have several entries, use the -d = definition file to list all entries for deletion or change. If the -d switch is used, then the -s and -r switches will be disabled.

Log file contains results of process, such as file not found, successfully processed filename profilename.NK2, etc.

Scripting that will determine the locations of your user's NK2 files are readily available.

One final note. Licensing for this product works the same as with our Helpdesk products. If you desire to purchase our HelpDesk products to assist in minor cleanup, know that they two programs, Command and HelpDesk share user licensing thereby eliminating an redundancy in license acquisition.