You could rip out all of the craziness about the "reliability" of the data, 
based on the last hinv and the last eval, and just look at the actual data:
 select sys1.netbios_name0
 ,lgm.name0 [Name of the local Group]
 ,lgm.account0 as [Account Contained within the Group]
 , lgm.category0 [Account Type]
 , lgm.domain0 [Domain for Account]
 , lgm.type0 [Type of Account]
 from
 v_gs_localgroupmembers0 lgm
 join v_r_system_valid sys1 on sys1.resourceid=lgm.resourceid
order by sys1.netbios_name0, lgm.name0, lgm.account0 
The reliability of the data (based on last hinv vs. last ci eval) was an 
interesting thought ... but it is kind of confusing and overkill.
 


     On Wednesday, October 21, 2015 1:30 PM, "Murray, Mike" 
<[email protected]> wrote:
   

  <!--#yiv1269148547 _filtered #yiv1269148547 {font-family:Calibri;panose-1:2 
15 5 2 2 2 4 3 2 4;}#yiv1269148547 #yiv1269148547 p.yiv1269148547MsoNormal, 
#yiv1269148547 li.yiv1269148547MsoNormal, #yiv1269148547 
div.yiv1269148547MsoNormal 
{margin:0in;margin-bottom:.0001pt;font-size:11.0pt;font-family:"Calibri", 
sans-serif;}#yiv1269148547 a:link, #yiv1269148547 
span.yiv1269148547MsoHyperlink 
{color:#0563C1;text-decoration:underline;}#yiv1269148547 a:visited, 
#yiv1269148547 span.yiv1269148547MsoHyperlinkFollowed 
{color:#954F72;text-decoration:underline;}#yiv1269148547 
span.yiv1269148547EmailStyle17 {font-family:"Calibri", 
sans-serif;color:windowtext;}#yiv1269148547 .yiv1269148547MsoChpDefault 
{font-family:"Calibri", sans-serif;} _filtered #yiv1269148547 {margin:1.0in 
1.0in 1.0in 1.0in;}#yiv1269148547 div.yiv1269148547WordSection1 {}-->I went 
through this blog post. I’ve got the query working properly in SQL Management 
Studio, but when I run it in a report, it’s just blank. It returns ~16k rows in 
the query. Any ideas?    
https://walidhegazy.wordpress.com/2014/09/11/sccm2012-r2-collect-local-group-users-custom-report/
       Best Regards,    Mike Murray Desktop Management Coordinator - IT Support 
Services California State University, Chico 530.898.4357
[email protected]    


  


Reply via email to