did you look at the SQL views in CM12 ? 
http://eskonr.com/2013/10/download-sccm-configmgr-2012-r2-sql-views/

Eswar Koneti
www.eskonr.com

From: [email protected]
To: [email protected]
Subject: RE: [mssms] SQL query to get driver (not driver package) content 
source path?
Date: Mon, 4 Nov 2013 21:14:23 +0000









Yeah, I am looking for a  report I can publish and get some subscriptions on. I 
could do that with PowerShell and Excel or maybe SharePoint but I would really 
prefer SSRS as that’s where all my other reports are housed.
 

Daniel Ratliff

 


From: [email protected] [mailto:[email protected]]
On Behalf Of Trevor Sullivan

Sent: Monday, November 04, 2013 3:10 PM

To: [email protected]

Subject: RE: [mssms] SQL query to get driver (not driver package) content 
source path?


 
Why not use the SMS_Driver WMI class? Does it have to be SQL?
 
Cheers,
Trevor Sullivan
 


From: 
[email protected] 
[mailto:[email protected]] On Behalf Of Daniel Ratliff

Sent: Monday, November 4, 2013 12:51 PM

To: [email protected]

Subject: [mssms] SQL query to get driver (not driver package) content source 
path?


 
I hope I am just completely missing it here, but is there a SQL view in 
ConfigMgr 2012 (SP1 CU2 specificially) to list the driver source path? I have 
an old query I used for ConfigMgr 2007 but the view no longer exists.

 
The closest thing I can find it v_package and v_driverpackage but that is only 
for the driver packages, not the drivers themselves.

 
Daniel Ratliff

 
 


The information transmitted is intended only for the person or entity to which 
it is addressed

and may contain CONFIDENTIAL material. If you receive this material/information 
in error,

please contact the sender and delete or destroy the material/information.
 
 


The information transmitted is intended only for the person or entity to which 
it is addressed

and may contain CONFIDENTIAL material.  If you receive this 
material/information in error,

please contact the sender and delete or destroy the material/information.





                                          

Reply via email to