-
Adding an IP Scope
Desktop Central has different agents for different locations, for example a local office agent will not be the same as the remote office agent. Similarly every remote office has different agents as well. When you are managing computers one or more remote locations, you can have a defined set of IP ranges for different offices. This enables the Desktop Central Server to identify the agents with respect to the IP range.
So whenever a computer is moved from a local office to a remote location, IP scope is used to automatically detect and deploy the respective WAN agent. Desktop Central will check for the change in the IP address periodically and will deploy the appropriate agents whenever a change is detected.
Can someone please clarify for me how it is that a WAN agent changes the
distribution server it receives content from? From the documentation
it states in a few places that the Agent will be installed from the
Distribution server if it senses an IP Subnet change?
what I am understanding from that is that the DC Agent gets fully
installed at each different location the user visits? Or does the
agent just update some configuration files that contain the new
Distribution server settings?
My concern is that we have a lot of VPN users (1000+) that will
say start in location 1 in the morning and then go on the road for
the day and connect Via VPN to location 2, and come back in the
afternoon to location 3. if what I'm understanding is correct
the user would have the following happen.
The agent is about 16Megs in size
1. In the morning it would install the WAN agent for Location 1 (16Megs)
2. on the road via VPN, the WAN agent for location 2 would
install (16Megs)
3. In the Afternoon it would install the WAN agent for Location 3 (16Megs)
can someone confirm how the switch happens?
This is from the Documentation
thank you.