Network Mapping Feature in EPM

Version 8

    Verified Product Versions

    Endpoint Manager 2018.x

    Purpose

     

    Network Mapping is designed to help you understand your companies network. This may or may not be an accurate representation of your environment but will help you determine what is on the network and the bandwidth.

     

     

    Prerequisites

    • This is only available on 2018.1
    • CSEP is enabled on he subnet (will be covered in the process portion)
    • At least one 2018.x+ agent on the subnet

     

     

    Process

     

    The Network Map was removed from the 2018.3 console as the default but can be added by creating the DWORDHostNetworkMap in the Reg Key "HKEY_CURRENT_USER\Software\LANDesk\ManagementSuite\WinConsole". Setting it to 1 will turn on the network view in the console. If you would like to open the Network view without having to put it back in the console, the app is in the Managementsuite dir under NWMapApp.exe.

     

    Agent Settings

     

    By default, the agent settings for network mapping are turned on. There is not much here other than:

    • changing the Route Target- This will send the route info from the client to the target to the core. This could be the core or any other device on the network.
    • Frequency- This is how often the route occurs

    CSEP

     

    Under the Self-electing subnet services choose the network mapping and in the subnet trees to the right, right click on a subnet and enable.

     

     

    Network Map

     

    The map will show different layouts based on the traceroute

     

    You will see different colors for the line and this shows the response time of the ping. Green is good response time, yellow is some latency and red is big latency.

     

    Lastly, you will be able to drill down and have the ability to RC, review provisioning and looking at inventory. You will also see the type of OS for that machine and its IP.

     

     

    This network map uses multicast to determine the Rep for the subnet but that rep will perform the traceroute. This route is for the subnet and devices the core knows about within that subnet will be added to the map. This will not tell you devices that are not managed but are in that subnet. This is designed to show you what your network looks like for the devices managed by you the Ivanti admin; this will include agentless scanned devices. The drill down is real time but the latency check is done during the route check which is 7 days by default as you saw but can be changed. This means the map will change as often as your end-users moving around from wired to wireless and vice versa.