I think the problem did away in relation to the new version, and not because of the extra instructions you provided.
On itself, these instruction do not have any effect on the OPC operations, because the CertificateAcceptancePolicy object you created is just an in-memory structure holding the policy parameters. In order for this to work, you would need to assign the "trustedCert" to the .SharedParameters. of the EasyUAClientManagement object. Much more usual approach would be *not* to create a new CertificateAcceptancePolicy, but simply set the parameters of the existing one, something like (not verified)
myEasyUAClientManagement = CREATEOBJECT ("OpcLabs.EasyOpc.UA.EasyUAClientManagement")
myEasyUAClientManagement.SharedParameters.EngineParameters.CertificateAcceptancePolicy.AcceptAnyCertificate = .T.
Back to the original problem, it hopefully it will not appear again. But it had to do not with the server certificate, but own (client) certificate. My advise to you, after checking the software version, would have been to remove the own certificate from the certificate store, and re-start the application at least one with admin (elevated) privileges, so that a new client cert is created.
The OPC UA Configuration Tool is from OPC Foundation. Parts of its functionality can be used to manage QuickOPC applications (and some other OPC UA applications, but not all of them), other parts are basically useless for your purpose. Documentation link is in this article:
kb.opclabs.com/UA_Configuration_Tool_Overview .
Best regards
