I'm Rob Marshall, a consultant who specialises in the Microsoft System Center Configuration Manager product. I like to share, i do so by blogging and helping out when I can in the MS SMS newsgroups and participating in the ConfigMgr MVP program.
I was awarded and joined the program in 2009. It'd be an understatement to say it has to be one of the best experiences an IT engineer can have, if they really enjoy specialising in a product.
My biggest weapon for troubleshooting is, my formidable knowledge, no, only joking, you, the community. I find if I cannot answer a question, then I can usually find the answer from using Bing\Google, pouring over the documentation, and if that doesn't work, tinkering in mine or someone elses virtual lab.
The blogs pretty much about ConfigMgr, but it is also a platform for me to express my random urges to display something I've stumbled across, and that I imagine would entertain you or what not as equally as it did me.
Was just asked to create a ConfigMgr query to show which collections a client is a member of:
Note: Collections do not replicate upwards, so running this on your Central for a Tier 2\3 client will not show anything. Either run it on the assigned site server, or from a higher up site server where all the collections are managed ...
SELECT v_FullCollectionMembership.CollectionID, v_FullCollectionMembership.Name as [Client], v_Collection.Name AS [Collection Name], v_FullCollectionMembership.SiteCodeFROM v_FullCollectionMembership INNER JOIN v_Collection ON v_FullCollectionMembership.CollectionID = v_Collection.CollectionIDWHERE V_FullCollectionMembership.Name = '<MACHINE NAME>'
This can even go in to a report, create the report, create a prompt called @ClientName, edit the above '<MACHINE NAME>' text (don't forget to strip the apostrophes out too) and replace with @ClientName, then replace the existing default query in the new report with the modified SQL statement from above.
You could even link this report to the built-in "All resources in a specific collection" report, a good idea as that report then links to another report showing you the advertisements for that client which can then be drilled in to even further to give you the "Status of a specific advertisement". Very handy if you first want to know what collections the client is a member of (for deployment troubleshooting), then go through to the advertisement information.
This will probably work on SMS2003 as well, I don't think those views changed ...
(PS ... I hate the way community server messes with formatting, gets font sizes wrong, won't let you reformat easily, and generally makes a mare of things I post ... yes I even blame CS for my typo's, factually incorrect postings and everything else, grrr, double grrr)