The POWER of Ivanti Endpoint Manager

Recently I had to come up with a solution for a customer to collect the duplex setting on NICs in their environment. I wanted to highlight here just how powerful Ivanti Endpoint Manager can be to help you out with custom settings like this.

So, for this example of the “duplex” setting, here we go:

  • In your Ivanti Management Console, go to Tools > Reporting / Monitoring > Manage Software List;
  • Expand Custom Data and click on Registry Items;
  • Right-click Registry Items and click Add;
  • Add the lines below to match this screenshot:

 

  • Effectively, what we are doing here is creating an entry to capture the NIC name and Duplex entries; so you need to add the following entries one at a time:
    • First, all entries will be HKLM under Root Key;
    • Second, each of the keys I list below will have only two values, i.e. *SpeedDuplex and DeviceDesc;
    • Third, the key fields;
      • SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002bE10318}\0000
      • SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002bE10318}\0001
      • SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002bE10318}\0002
      • SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002bE10318}\0003
      • SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002bE10318}\0004
      • SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002bE10318}\0005
    • Lastly, match the \0000; \0001 etc. to the following Attribute Names:
      • For \0000 you will have two Attribute Name entries; being:
        • Custom Data – NIC Duplex – NIC 0000-1
        • Custom Data – NIC Duplex – NIC 0000-2
        • Effectively the \0000 will reference one NIC in the registry, so both the keys as listed in the second bullet will each have this entry.
      • For \0001 you will have two Attribute Name entries; being;
        • Custom Data – NIC Duplex – NIC 0001-1
        • Custom Data – NIC Duplex – NIC 0001-2
      • For \0002 you will have two Attribute Name entries; being;
        • Custom Data – NIC Duplex – NIC 0002-1
        • Custom Data – NIC Duplex – NIC 0002-2
      • And so on.
  • Effectively, each \000x entry above in the registry references a network adapter on a device. I think 5 should suffice to capture them all. You can start off and try with just \0001 as that seems to be the most common one I’ve seen.
  • Once done with above, click the “Make available to clients” button on the toolbar.

 

Yours should look similar to this:

 

 

The next time a device performs an inventory scan they will download the updated ldappl3.ini file from the server and process the custom registry entries above into the device’s inventory and you should see something like this:

 

 

For guidance, the *SpeedDuplex number shown in the query output above references as follows:

0 auto negotiate
1 10 Half duplex
2 10 Full duplex
3 100 Half duplex
4 100 Full duplex
5 1000 Half duplex
6 1000 Full duplex

 

** I manually set my test device to 1000 Full Duplex under the NIC properties and as you can see from the screenshot above, it shows 6.

 

You can now query against that as follows (note under Machine Components > go to Custom Data and find your entry. Select the NIC 0000-1 option and make sure you see the NIC name on the right. Don’t select it, but simply select “Exists” as the operator and click insert. Then bottom left add NIC 0000-2 as a display column). Save and run the query:

 

 

Et voila!

 

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s