After installing the SafeGuard Client using MSIEXEC with ADDLOCAL parameters, no SafeGuard Credential Provider is available for logon to Windows. As a result, the initial user synchronization doesn't happen. The user status remains "unknown" (greyed out in Client status). Another effect may be that no inventory information of the client is sent to the SafeGuard server.
First seen in
SafeGuard Device Encryption
Windows Vista, Windows 7
When installing the SafeGuard Client using MSIEXEC with ADDLOCAL parameters (see Knowledge Base Artikel 108426) to add certain modules of the client, the command didn't contain "CredentialProvider" to install the SafeGuard Credential Provider.
This can be validated with the installer logfile (e.g. with this logging parameters: msiexec /i SGNClient.msi /L*vx) or after the installation by checking the registry.
Example for a wrong installation:
What To Do
When installing the SafeGuard Client with MSIEXEC with ADDLOCAL parameters, make sure that "CredentialProvider" is listed in the command.
Example for the installation of the Volume-based Encryption and Data Exchange modules:
msiexec /i C:\SGN\SGNClient.msi ADDLOCAL=Client,BaseEncryption,SectorBasedEncryption,CredentialProvider,SecureDataExchange
Example of a correct installation:
The SafeGuard Credential Provider can be added to the installation by using the complete MSIEXEC command which should have been used in the first place. After a reboot, the SafeGuard Credential Provider should be available and the initial user synchronization should complete.
If the installation was performed correctly but nevertheless the SafeGuard Credential Provider is not available, please see also the following Knowledge Base article:
120376 - The SafeGuard Credential Provider tile is not available on systems with a "Validity" fingerprint device and OmniPass software installed