There is still the LDMS_Client.exe that has lots of other features, but one of them is bringing mapped drives back to the core as part of the inventory. You can learn more about it here:
Otherwise you'll need to look at adding the HKey pieces to the ldappl3.template file.
LDMS_Client doesn't play well with v9 at last check. My suggestion is to go the LDAPPL3 route for now, it will be easier to work with and remove going forward. LDMS_Client is not being supported presently and there is no support. It is not worth the headache, unless someone wants to pick this project back up and begin supporting it again... The source code is there as well. ;-)
Maybe worth adding an ER for this, it is quite trivial but should garner a few votes. :-)
Thanks for that guys, i have added the HKEY information to the ldappl3.template, but am unsure of how to push it out to the clients i have. There was a button in 8.8 that did the job "make available to all clients", cant see it in 9.0.
And another completly noobish question, the path that you use in ldapp3 is:
Key=HKCU, Network\E, Custom Data - MappedDrive, Drive E:
But if i look in the registry i cannot find a Network entry under HKCU (HKey_Current_User)
The button to make available to clients was in SLM prior to 9.0. It is now in Manage Software List and an be found in Reporting/Monitoring.
As for the Path and you not having a Network key under HKCU, that key will not exist if you don't have a mapped drive for the currently logged in user. Verify you have a mapped network drive and check again.
Also, I have done this in the past listing all drives from E through Z in the ldappl file. When the user runs the scan via the run key or manually running the scan, you will get this info. If the local scheduler runs the inventory via a schedule or when the IP changes, this runs as system and will not report back the mapped drives because the HKCU hive is not available to System for the currently logged in user.
Hope this helps.
1 of 1 people found this helpful
Getting mapped drive information is always a pain, because there are in the HKCU\Network, and only scanned by a local scan. I made my life easier. I created a batch that copies the mapped drive information from the HKCU to the HKLM, added that information to the Ldappl3, now I can scan the PCs as much as I need to and always have the drive info. Depending on how much the drive mappings change or are added, you could setup the batch file to run as needed as a policy.
Don't forget that the regisitry will only reveal mapped drives that are persistent. Any mappings from daily logon scripts, etc. don't appear in the registry.
Might want to add this request to this ER
Selfish Plug for My ERs
Core Synchronization - OSD !
Updated Inventory Attributes
Cumlative Patch List for LANDesk Products
Integrate a Console Extender into the Console
Hey, this might be a long shot but can you post that script?