Connection allowed when using an invalid certificate

In some cases, and while connecting to a Host on Windows 7, the system may fail and throw an error when attempting to establish a remote connection using Portal Communication profile and connecting either through the Portal (browser) or the Guest app.
The reason why the connection fails is that the TLS Certificate Chain Validation fails and thus, the following error is thrown: Failed to connect to Host. Reason: Cannot connect to Connection Server

In case installing the root CA isn’t possible, as presented in the Solving TLS Certificate Chain Validation failures in Netop Host article, you can temporarily bypass these errors by performing the following: 

• Edit the NETOP.ini file located in C:\Windows on the HOST machine. 
  Open this file using Notepad and look for the heading [HOST]. Under that heading, add an entry that reads 
  W7CacheCertifVerifMinutes=<minutes> (default 0, inactive)
  
  [HOST]
  W7CacheCertifVerifMinutes=<minutes>

  Then restart the Netop Helper service.

• When connecting from the Guest application, make sure the “Connection allowed when using an invalid certificate” is checked. 

When first connecting, you will still see the connection error, but the result will be cached on the HOST for the specified amount of minutes. Any subsequent connection will then be accepted and will ignore any certificate errors during that amount of time (W7CacheCertifVerifMinutes=<minutes>)