Ticket History #5753: NIM: BUG: APP: Do not report errors for modules that are not installed

If an ImagePath value is not defined for a module, the module should be
ignored and an error loading the module should not be reported to the
user.

There are many legitimate reasons why there might be a Module key for a
module that is not installed. Examples include:

(1) Roaming profile and the module in question is installed on some
machines but not others

(2) 64-bit and 32-bit environments. A module might be installed in
one but not the other.

(3) The module was uninstalled and the user's profile was not available
to perform cleanup.

In all of these cases, annoying the user with an error and incrementing
the error count on the module is wrong. If the user wants to know why a
module is not present, she can look on the plugins page and easily see
that the module is not installed.

Remove Krb5Cred, Krb5Ident, and Krb4Cred default configuration data from
the KMM Schema. Require that modules that are installed be properly
installed.

Add NIM Module Registry values to the NSIS installer. These values were
already being set by the Wix installer.

By removing the ImagePath default, unable to load module errors will
not be generated when the module has not in fact been installed.


Commit By: jaltman



Revision: 20022
Changed Files:
U trunk/src/windows/identity/kmm/kmmconfig.csv
U trunk/src/windows/installer/nsis/kfw-fixed.nsi

When there is no ImagePath value for a module it indicates
that the module has not been installed. Do not report an
error to the end user for uninstalled modules. This will
only annoy the user and there is probably nothing the user
can do about it. Perhaps the user uninstalled the module
intentionally. The fact that there is still a HKCU key
remaining is not an indication that the module is in use.


Commit By: jaltman



Revision: 20023
Changed Files:
U trunk/src/windows/identity/kmm/kmm_registrar.c