Install certificates
The policy configuration Certificate for Windows can be used to install certificates on Windows 10/11 devices via Relution. Depending on the certificate type, either the certificate store or the location of the certificate and its key can be specified.
Upload certificates to Relution
To be able to distribute certificates via Relution, they must first be uploaded to the certificate store of Relution (see also Certificate Management →).
- To do this, one has to go to
Settings→Certificates. - Then the button Add has to be clicked.
- A name has to be assigned, the password has to be entered for password-protected certificate files (e.g. PKCS#12) and finally, the certificate file has to be selected.
- The entry is then confirmed with Save.
Applying certificates on Windows 10/11 devices
- One has to navigate to
Devices→Policiesin the Relution Portal and click on Add. - A Windows policy has to be created and a name has to be assigned. Then, Save has to be chosen.
- After clicking Add, the Certificate option is selected and the process is continued with Add details.
- Under Certificate, the Select certificate option (default) is chosen and the certificate uploaded in the previous section is selected via Select. The further options depend on the certificate type:
- Certificate without private key (PEM/DER): a Certificate store is selected (default: Automatically). Intermediate Certificate Authority, Personal, Trusted Root Certificate Authority, Trusted People and Trusted Publishers are also available.
- PKCS#12 certificate (
.p12/.pfx), certificate template or user certificate: under Certificate Location, either Device (default) or User is selected, the Certificate Key Location is set (TPM, TPM if available, Software or Windows Hello for Business; default: Software) and Key is exportable is enabled if required. The toggle is only available with Software.
- The configuration has to be saved and the current version of the policy has to be published (Publish).
- To apply the policy to Windows 10/11 devices, one must add the desired devices via the Devices with this policy tab. The selected certificates will then automatically be installed on the devices.
With Automatically, Relution chooses the store based on the certificate: self-signed CA certificates are installed under Trusted Root Certificate Authority, other CA certificates under Intermediate Certificate Authority and all other certificates under Personal. If the certificate store of an existing configuration is changed, Relution removes the certificate from the previous store.
Under Certificate Location, Device installs the certificate in the computer’s certificate store, User in the user’s certificate store. As with the certificate store, if the location of an existing configuration is changed, Relution removes the certificate from the previous location. Under Certificate Key Location, TPM stores the private key in the device’s TPM (Trusted Platform Module); if the device has no TPM, the installation fails. TPM if available falls back to Software in this case. If Key is exportable is enabled (disabled by default), the private key can be exported on the device later.
The certificate of an existing configuration cannot be changed afterwards. A different certificate requires a new configuration. Configurations created with a version prior to Relution 5.25 can no longer be edited and must also be created again.
Distribute certificates from certificate templates
Since Relution 26.0, it is also possible to distribute certificates from certificate templates directly to Windows devices. The template (e.g. a template of the Built-In CA →) is selected in step 4 via Select certificate instead of an uploaded certificate. Templates are listed on the Certificate templates tab of the Select a certificate or a certificate template dialog, which opens via Select. Each device receives its own certificate, issued based on the template. The options for PKCS#12 certificates (location of the certificate and of the key) then apply.
Distribute user certificates
As an alternative to Select certificate, the Use user certificate option can be chosen under Certificate. The user certificate from the profile of the user assigned to the device is then installed (see User certificates →). User certificates of the Category General certificate are taken into account. If the user has several of them, the longest-lived one is installed; a value in the Certificate name field is currently not saved in this configuration. The options for PKCS#12 certificates apply here as well.
If no user is assigned to the device or the user has no certificate of this category, no certificate is installed. In this case, the device receives a compliance notice stating the cause.