Signature Servers for non-persistent VDI

Alex- — Thu, 06 Apr 2023 07:37:58 GMT

On-premises EPS, R81.10 T81.

Client E86.80.

I've followed the administration guide to deploy a Shared Signature Server for non-persistent VDI and followed the Policy approach.

At the time of reaching the Setup Validation, I wait 20 minutes as mentioned but nothing ever happens. Even after one hour, trying another folder and so on. The guide just mentions that if the folder is empty, the setup isn't valid without providing any further troubleshooting steps. The EPS and the signatures server have full L3 connectivity between them without further firewalling or filtering, the server can in any case get the policy and updates from the server without any issues.

All parameters have been double-checked. There doesn't seem to be an SK for this feature and I have a TAC case ongoing which isn't conclusive yet. There's nothing in the logs of the EPS either (console and /var/log/) and the local firewall on the signatures server isn't active.

I wonder if anyone here has already successfully deployed such a setup and could share any interesting trips & tricks to make it work.

Re: Signature Servers for non-persistent VDI

Alex- — Thu, 01 Feb 2024 21:06:06 GMT

After a lengthy SR, it appeared the feature required policy mode and this long-standing installation was in mixed mode and the change was quite complex.

Now the whole on-premises installation has been scratched for a brand new EPMaaS on Infinity and each client decommissioned and reintegrated in the cloud-based product so there's no legacy configuration imported.

Yet, the issue remains exactly the same after duly following the admin guide, so we're now not that sure that original reason was valid.

Before going with an SR again, we wonder if anyone who made this work could share tips and tricks which might be outside the admin guide.

topic Re: Signature Servers for non-persistent VDI in Endpoint

Signature Servers for non-persistent VDI

Re: Signature Servers for non-persistent VDI