We have existing computers on LD8.8. We're upgrading to LD9 on a different core. These machines are all off of the network and use the Management Gateway for communication. Naturally, the certs for the MG are different between the two cores.
Installing the self-contained .exe version of the agent takes a very long time (>10 minutes) on these computers. The bulk of the time is spent in the .msi install part--that's where it seems to hang. Looking at task manager, I see vulscan.exe sitting there, not using any CPU and very little RAM during the entire hung phase. As soon as it disappears, the installer transfers out of the msi section and completes normally.
My guess is that vulscan.exe is trying to communicate with the core during this period and totally failing, but I can't figure out why it would be doing this or how to stop it. Any thoughts?
