Hi, I've been using this query in 2007 and it's working with the machines migrated from 2007 and 2012 but new machines will not show up. Something is amiss with the operatingsystem.resourceID and I can't figure out what.

Why are you querying a table, specifically system_resource_n_arr? Bad form, you should only ever query views and tables may change without warning.

Also, given that you are using inner joins here, if there is no match in the table, you won't get any data back. Thus, if you don't have any maintenance windows setup, you won't get any data back.

The best way to troubleshoot larger queries like this is to take it step by step. Start with one join and try it. If it works as expected, add the next join. Once the results go awry, you narrowed done your issue to the latest added join or join condition.

Why are you querying a table, specifically system_resource_n_arr? Bad form, you should only ever query views and tables may change without warning.

Also, given that you are using inner joins here, if there is no match in the table, you won't get any data back. Thus, if you don't have any maintenance windows setup, you won't get any data back.

The best way to troubleshoot larger queries like this is to take it step by step. Start with one join and try it. If it works as expected, add the next join. Once the results go awry, you narrowed done your issue to the latest added join or join cond

v_GS_OPERATING_SYSTEM is retrieved by hardware inventory like almost all other data.

My comment on querying tables still stands: it's a terrible practice to get into and will cause you issues at some point.

v_GS_OPERATING_SYSTEM is retrieved by hardware inventory like almost all other data.

My comment on querying tables still stands: it's a terrible practice to get into and will cause you issues at some

The simplest way to do this is find the data within CM12 Resource Explorer, once you do that the view name is almost always the same name as the node name v_gs_<node name>.

If the data is found on the computer properties then the view will be v_R_<something> or v_RA_<something> the names are obvious as to what they contain.

The simplest way to do this is find the data within CM12 Resource Explorer, once you do that the view name is almost always the same name as the node name v_gs_<node name>.

If the data is found on the computer properties then the view will be v_R_<something> or v_RA_<something> the names are obvious as to what they contain.

v_GS_OPERATING_SYSTEM is retrieved by hardware inventory like almost all other data.

My comment on querying tables still stands: it's a terrible practice to get into and will cause you issues at some

This blog might help.

http://www.enhansoft.com/blog/troubleshooting-inventory-flow