We have a very distributed environment; most of our machines use the Juniper IVE SSL VPN product to connect to hq resources. Therefore, when they are not connected, they communicate through the Management Gateway. As the Juniper product actually creates its own virtual NIC (in Windows), when that is activated, the machines run an inventory scan and report their SSL VPN IP address as their primary IP, which is what Landesk uses in the inventory list and to send scripts, push deployments and the like. If we used anything but Management Gateway Remote Control, that would also go to that IP address. This isn't a problem as long as the machines are connected, but once the SSL VPN disconnects, another inventory scan is not automatically run, so our inventory becomes full of machines that aren't listed under the correct IP addresses.
Anyone else have this problem?
Any ideas how to fix it?
My general preference would be for the physical NIC to always remain as the primary IP, but I figure that that's not possible, since once the SSL VPN is up, the machines can communicate directly to the Core over that SSL VPN/virtual NIC.