@jburleson Yes both firefox and chrome uses the windows cert store as Tom posted. I know because we had to do this with our vCenter servers. You need to take the public root certificate of the self signed certificate and import it into the machine’s trusted root certificate store. Once you do that then there is no warnings in any of the three browsers.
While these instructions are specific to vCenter the process would be the same for any self signed root certificate. https://tinkertry.com/how-to-get-rid-of-vsphere-browser-certificate-warnings-in-windows
@processor Great you figured it out!!
Do you know if it’s possible the client to use only physical interface and not the virtuals ?
Here is an old discussion we started about virtual adapters: https://forums.fogproject.org/topic/7032/ignore-tunnel-interface-on-client
Joe who developed the fog-client makes a clear point about the filter should only be in one place - the server side. We have filter settings in FOG (FOG Configuration -> FOG Settings -> …) but I see that it might be quite hard to figure this out. Maybe we should add a hint on which MAC address it finds duplicated so it’s easier to find. I am open for any suggestion on this.
It’s probably going to be two weeks or longer before I can adjust the daily tests - I’m super busy this weekend, next week, and vacation is the week after. But I’m pretty confident I can test upgrades. At least upgrading from the last release.