Is suspect this is a bug related to filesystem redirection and x64, can
anyone confirm this. Have seen this at two customers running x64 eDirectory.

Scenario:
eDirectory tree with two servers (one 32-bit, the other 64-bit - both
running on windows)

DNs to both servers are listed in the W0 object

Problem:
PKIHealthCheck doesn't show that the eDirectory 64-bit is properly
configured as a SDI Key Server.

----------
PKIHealthCheck log file on x64 server shows:

Step 0 Check if this server should be an SDI Key Server.
Testing for keyfile -- C:\Windows\system32\novell\nici\nicisdi.key.
This server does not have any SDI keys on it.
Step 0 succeeded.

The real path to this file is C:\WINDOWS\syswow64\novel\nici\nicisdi.key
(however it seems that PKIHealthCheck is running as a 64 bit process and
doesn't get redirected to syswow64 like a 32 bit process would when
requesting system32)

PKIHealthCheck log file on x86 server is OK:
Step 0 Check if this server should be an SDI Key Server.
Testing for keyfile -- C:\WINDOWS\system32\novell\nici\nicisdi.key.
keyfile size 247.
This server is already in the list.
Step 0 succeeded.

-

SDIDiag check was OK

SDIDIAG> check
*** [Key Consistency Check - BEGIN] ***
[Checking SDI Domain]
SDI Check Domain Configuration...
SDI Domain Key Server
..x64SERVER-NDS.Servers.Services.ACME.IDV-TREE.
- Configuration is good.
SDI Domain Key Server
..x86SERVER-NDS.Servers.Services.ACME.IDV-TREE.
- Configuration is good.
*** SDI Check Domain Configuration is [GOOD]
SDI Check Domain Keys...
SDI Domain Key Server
..x86SERVER-NDS.Servers.Services.ACME.IDV-TREE.
- Keys are good.
SDI Domain Key Server
..x64SERVER-NDS.Servers.Services.ACME.IDV-TREE.
- Keys are good.
*** SDI Check Domain Keys are [GOOD]

[Checking SDI Domain: GOOD]

*** No Problems Found ***