How to create a custom inventory to capture a user's mapped drives

Article:HOWTO2598  |  Created: 2006-03-02  |  Updated: 2009-08-11  |  Article URL
Article Type
How To


How do I create a custom inventory in order to capture what mapped drives users have?


  1. Go to <Installation Path>\Altiris\Notification Server\NSCap\Bin\Win32\X86\Inventory Solution and create an .ini (for this example, let's call it AeXInvSolnUsr5.ini) and modify it to contain the following contents:

    aexcustinv.exe /in UsrNetDrv.cit /out UsrNetDrv.nsi
    aexnsinvcollector.exe /hidden /nsctransport /v default /useguid

  2. Create a UsrNetDrv.cit with the following contents and place it on your Notification Server under <Installation Path>\Altiris\Notification Server\NSCap\Bin\Win32\X86\Inventory Solution:


    <InventoryClass name='Aex Network Connections' manufacturer='Altiris'
    description='Network Connections' version='1.0' platform='Win32'

    <xml xmlns:s="uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882"
    xmlns:rs="urn:schemas-microsoft-com:rowset" xmlns:z="#RowsetSchema">

    <s:Schema id="RowsetSchema">

    <s:ElementType name="row" content="eltOnly" rs:updatable="true">

    <s:AttributeType name="c0" rs:name="Name" rs:number="1"
    rs:basecolumn="Name" rs:keycolumn="true" mifAttrId='1'>

    <s:datatype dt:type="string" dt:maxLength="255"/>


    <s:AttributeType name="c1" rs:name="Remote Name" rs:number="2"
    rs:basecolumn="Remote Name" rs:keycolumn="true" mifAttrId='2'>

    <s:datatype dt:type="string" dt:maxLength="255"/>


    <s:AttributeType name="c2" rs:name="Local Name" rs:number="3"
    rs:basecolumn="Local Name" rs:keycolumn="true" mifAttrId='3'>

    <s:datatype dt:type="string" dt:maxLength="255"/>


    <s:AttributeType name="c3" rs:name="State" rs:number="4"
    rs:basecolumn="State" rs:keycolumn="true" mifAttrId='4'>

    <s:datatype dt:type="string" dt:maxLength="255"/>


    <s:AttributeType name="c4" rs:name="User Name" rs:number="5"
    rs:basecolumn="User Name" rs:keycolumn="true" mifAttrId='5'>

    <s:datatype dt:type="string" dt:maxLength="255"/>


    <s:AttributeType name="c5" rs:name="Providor" rs:number="6"
    rs:basecolumn="Providor" rs:keycolumn="true" mifAttrId='6'>

    <s:datatype dt:type="string" dt:maxLength="255"/>


    <s:AttributeType name="c6" rs:name="Resource Type" rs:number="7"
    rs:basecolumn="Resource Type" rs:keycolumn="true" mifAttrId='7'>

    <s:datatype dt:type="string" dt:maxLength="255"/>


    <s:AttributeType name="c7" rs:name="Persistent" rs:number="8"
    rs:basecolumn="Persistent" rs:keycolumn="true" mifAttrId='8'>

    <s:datatype dt:type="string" dt:maxLength="255"/>





    <%foreach wmiobject="o" namespace="ROOT\CIMV2" wql="Select * from


    c0="<%write "wmi:o.Name"%>"

    c1="<%write "wmi:o.RemoteName"%>"

    c2="<%write "wmi:o.LocalName"%>"

    c3="<%write "wmi:o.ConnectionState"%>"

    c4="<%write "wmi:o.UserName"%>"

    c5="<%write "wmi:o.ProviderName"%>"

    c6="<%write "wmi:o.ResourceType"%>"

    c7="<%write "wmi:o.Persistent"%>"






  3. Navigate to Tasks > Assets and Inventory > Inventory > Windows > Inventory Tasks, right-click, and clone the Re-create User Inventory task; call it Custom Network Inventory.
  4. Now go to the newly created Custom Network Inventory task and, on the right-hand side, click on Go to Program.
  5. Click on New and fill out the following two fields in here:
    1. Name: For arguments sake let's call it 'Mapped Drives Definition File'
    2. Command line: Type the following: 'AeXInvSoln.exe /hidden /s AeXInvSolnUsr5.ini'

      You may also want to copy any other settings contained from another one of the programs such as "Run with rights" and so on. Click on Apply and Update Distribution Points.
  6. Refresh the newly created task and ensure that the program selected is the Mapped Drives Definition File; click Apply.
  7. Now choose a test target collection and enable the newly created task.

    You will then need to update the configuration on the test client and wait till it runs the newly created inventory task.

Legacy ID


Article URL

Terms of use for this information are found in Legal Notices