-
What version are you using? (OS, client, server, etc.)
EPP client version: 2605.1.2.0
EPP server version: 2604.0.1.0
OS: Windows 11 25H2 -
Policy Update unsuccessful.
Agent is seen connected in the EPP Server console.
Agent installed in the client successfully - during installation we set the server IP and port.
But post installation - when we try to update the policy - on the client it shows as unsuccessful.
When we check using “ctrl alt I” we see the agent as connected but besides Server IP & port it shows as “Not Set”
We have tried reinstalling the agent and same scenario occurs.
Hello. Vishwa.
You need to track the details in the debug logs.
Create c:\eppclient.log file with administrator privileges and restart the EPP service to verify that logs are being generated.
(Kill the epp service using the taskkill command in cmd, or restart your PC.)
In my experience, there were likely many trust issues with CodeSign certificates for EPP component files (DLL, exe, MSI).
Hello Jeremy,
Thank you for your response.
It seems the issue might be just that the DigiCert Trusted Certification is not being downloaded by the Windows Store automatically due to internet connectivity (as advised by the support team.)
We are going to try to manually import certs from a system with internet connectivity and see what happens.
Edit: It didn’t work. We imported one cert and another was missing from the system.
Does your solution also take into account no internet connectivity on the client system other than necessary whitelisted?
You can extract the certificate from PC where the installation works correctly and install it on the PC where the problem occurs.
It seems you installed the wrong certificate.
I resolved many CodeSign certificate errors using the method above in an environment without internet access.
Hi Jeremy,
We were able to export and import the certificates which resolved the issue.
It seems the first time failed because we only used the single certificate found (we didn’t find the other one) and we couldn’t use powershell. Fortunately after help with tech support we were able to solve this.
Thank you for your help.

