The ability to inventory mapped network drives was a common customer ask in ConfigMgr 2007 and SCCM Expert and some other folks provided free scripts and MOF edits to take care of this. But can this be done in ConfigMgr 2012?
Mapped network drives and printers are a per-user setting so you need to run a script or process under the user’s context to grab that data and store it somewhere that the hardware inventory process can get to. The obvious place to store the data is WMI. There may be other scripts out there that do this and if you have a better way to do this in ConfigMgr 2012 please let me know, but I chose to use a script provided by CTS for ConfigMgr 2007 and it worked just fine in my lab. Credit to Alvin Morales and JC Hornbeck for the blog article:
Obviously in ConfigMgr 2012 we won’t perform the MOF edits shown in the article, we make the change in the ConfigMgr 2012 console itself. But the VB script provided (mapdrives.vbs is what they called it) is required. Given the requirements that need to be met for this to work as a ConfigMgr package (run with user rights, run only when a user is logged on, set it to re-run on a schedule, etc) this may work better as a logon script. You could also modify the VB script to inventory mapped printers as well. You could further modify the script to force a hardware inventory once it’s done, or just wait for the next scheduled inventory to occur.
Once you have created the package and deployed it to your clients, you can verify it worked by using WBEMTEST to connect to root\CIMV2 and look in CX_mappeddrives.
In the ConfigMgr 2012 console you’ll need to add the new class for hardware inventory. So, Administration/Client Settings/Default Client Settings (or select a custom device settings group)/Hardware Inventory/Set Classes. Click Add and use the Connect option to specify a client that now has the information stored in WMI and select the CX_mappeddrives class name.
Once the client has retrieved machine policy and submitted hardware inventory, you should be able to see the mapped drive data in Resource Explorer:
and you can confirm in the database: