There is an issue in the SMS reporting of mapped drives through Hardware Inventory.
Basically, mapped drives are recorded in root\cimv2\win32_LogicalDisk (with all drives) and a dirivitive class ..\win32_MappedLogicalDisk (but this contains very sketchy data so it would be best either joing with where, the two tables or filtering the whole LogicalDisk table.
THE ISSUE
root\cimv2\Win32_LogicalDisk can be queried and will display the mapped drives...however....SMS does not query this class, instead transends this class into it's own reporting class, root\cimv2\sms\sms_LogicalDisk. The provider for the transition doesn't support the Network Drive Types, even though it is only an integer value, and is not out of range. At the minute, I do not know why this is.
The win32_LD class is in the HINV, but has no properties, and has repoting set to false. I have been carrying out some tests with SMS reporting this mapped drive, and found that even when I populate the WIN32 instance of the SMS reporting class, Mapped drives still do not get reported.
I am working on this, and will try and get you an answer by the end of the week. As far as I am concerned, there is no reason why this is not being reported, as it is just lifting values, that are all valid.
I will get back to you.....let me know if you find the answer...but your problem is not creating a SQL report...as mapped drives do not appear in your logical disk table what so ever. The SQL bit will be easy, but we have to get them there first.....
OR
have a look at your LOGICAL_DISK_DATA table in your database...can you see mapped drives in there, if so, then I have a strange problem that is individual to me, I think you will find you wont.
We will concentrate on getting the machine mapped drives, rather than user specific, then we can look at getting the users mapped drives.
Neil J Cotton
UCLan Ba-SYS Development and Project Manager
NJC Technical Productions
Software Development | Network Consultancy | Wireless Network Provissions
Member of the IETF CAPWAP Work Group