Hi, I'm trying to create a collection that shows active directory groups + netbios name + last log on username. Where do I start? Thanks

Hi James, Do you mean a query?? Can you give an example of what you want to accomplish? Cheers,Bess, Kenneth - http://www.systemcenterforum.net

Hi, Either a collection or query will do. I'm trying to collect info which will contain the following. Active directory groups + Active directory user accounts + PC name (netbios name). The criteria for this will be: If a user is in a certain group, the PC name will be mapped to that particular user(last on log user). Do you know what I mean? Thanks.

This should help: http://blogs.technet.com/configurationmgr/archive/2009/09/09/report-to-find-last-logon-details-of-each-computer-using-configmgr-2007.aspx

Hi, Please take a look at this - http://blogs.technet.com/configurationmgr/archive/2009/09/09/report-to-find-last-logon-details-of-each-computer-using-configmgr-2007.aspx Can this do the trick for you? Cheers,Bess, Kenneth - http://www.systemcenterforum.net

Perhaps you mean like this? http://myitforum.com/cs2/blogs/skissinger/archive/2006/10/25/Target-Computers-by-Users_2700_-usergroup-membership.aspx The above was for SMS2003, and before Asset Intelligence and Top Console User. Here's a similar collection query if using Console User: select SMS_R_SYSTEM.ResourceID,SMS_R_SYSTEM.Namefrom SMS_R_System inner join SMS_G_System_SYSTEM_CONSOLE_USER on SMS_G_System_SYSTEM_CONSOLE_USER.ResourceID = SMS_R_System.ResourceId where SMS_G_System_SYSTEM_CONSOLE_USER.SystemConsoleUser in (select UniqueUserName from SMS_R_User where SMS_R_User.usergroupname Like "%MyDomain/Some Group Name%") There are some drawbacks with using this, as well as advantages. It's up to you to decide if the advantages outweigh the disadvantages. One of the advantages is that you don't have to train (much) your helpdesk folk. They can drop a username into a group, and their task is done. Another advantage is regarding 3rd party tools. Almost every single 3rd party tool (like Roger Zander's Client Center) look at advertisements in WMI as targeted to the computer resourceid, like the above would result in. The method of having just the usergroup name in the Collection works fine for targeting users in the usergroup. It does--it works great! the problem is when you ever have to troubleshoot or want to use a 3rd party tool to look at advertisements deserved you are kind of stuck with clispy. Clispy is great--don't get me wrong--but it's not easy to browse through sometimes. And triggering a WMI rerun of a user-targetted advertisement isn't fun either. The main disadvantage is in timings: User Discovery has to occur, and collection refresh has to occur, before the new group membership is reflected in the results of the query. The other disadvantage is that you have to be very careful how you name your groups. Because of how you have to use wildcards and LIKE, the group "%Adobe Acrobat Professional 9%" could also end up containing targets if you also name a group "Adobe Acrobat Professional 9.2", because the "like" clause won't see the .2 at the end--it's like Professional 9, so therefore, the computers drop into that collection. Another potential disadvantage is the high potential for disconnect between .systemconsoleuser and UniqueUsername. It could happen where the domain name may or may not be appended; in that case it's not exactly the same from systemconsoleuser=uniqueusername, so it may not behave the way you expect--that will be environment specific. Also, since this method isn't one that was originally thought of when SMS or ConfigMgr was designed, it's kind of a kludge, and finding people that can help you troubleshoot might be tricky. So there you go: it's possible, but really think about the long term implications of following this road. You may want to consider targeting users in usergroup via the normal method, which is the collection query results in 1 entry in the Collection: the usergroup name. Standardize. Simplify. Automate.

My original purpose of trying to achieve this was to come up with a report that displays computer netbios names + AD user names + AD groups. They all have to be linked of cause. Ideally, I want to link the computer netbios names data with AD groups. I've managed to modify sms_def.mof by using this link http://blogs.technet.com/smsandmom/archive/2007/08/30/how-to-extend-your-hardware-inventory-using-the-sms-def-mof-file.aspx Not too sure what else I need to do. Thanks

So what do you want to create? A collection or a report?

A report would be best.

Can anyone help me with this at all?