Hi All, I'll start of with stating what I think I know about sms 2003 behavior in regards to this problem. In sms 2003 if you wanted to be able to open resource explorer, start remote tools, etc... you had to make sure that you included the system resource.resourceid and system resource.resourcetype on your general tab. In sccm 2007 if you do this you can launch these same tools, until you modify your query to include a join from any other wmi class. At that point the right-click actions or the actions in the action pane for that matter disappear. Can anyone confirm this behaviour? Should I file a bug for this? Kim Oppalfens

I don't really have one handy, but if you take the all clients query, than you can access the right-click actions. If you take the properties of this query and you add the workstation status.lasthardwarescan on the general tab then the right-click actions like start; resource explorer or start; remote tools disappear. Kim Oppalfens

Hi Kim, I just created a brand new query, and only displayed: System Resource - Name, System Resource - Resource Type, and System Resource - Resource ID. When I run the query, I can right-click and get the Distribute, Start, and Install Client options. So it works for me. What are you missing? Wally

That works for me as well, but the minute you add something from a class different than system resource you lose these right-click options. No more start or distribute not sure about the install client option though. Kim Oppalfens

Yes. There are no options to choose when another class is added as a display column in "Select" statement. However, you can add another class as a Criteria, just not display it, and it works fine. Here is the WMI query that adds Windows Directory (OS class) to the query.GOODselect SMS_R_System.Name, SMS_R_System.SMSAssignedSites, SMS_R_System.IPAddresses, SMS_R_System.IPSubnets, SMS_R_System.ADSiteName, SMS_R_System.OperatingSystemNameandVersion, SMS_R_System.ResourceDomainORWorkgroup, SMS_R_System.LastLogonUserDomain, SMS_R_System.LastLogonUserName, SMS_R_System.SMSUniqueIdentifier, SMS_R_System.ResourceId, SMS_R_System.ResourceType from SMS_R_System inner join SMS_G_System_OPERATING_SYSTEM on SMS_G_System_OPERATING_SYSTEM.ResourceID = SMS_R_System.ResourceId where SMS_G_System_OPERATING_SYSTEM.WindowsDirectory = "C:\\WINDOWS"BADselect SMS_R_System.Name, SMS_R_System.SMSAssignedSites, SMS_R_System.IPAddresses, SMS_R_System.IPSubnets, SMS_R_System.ADSiteName, SMS_R_System.OperatingSystemNameandVersion, SMS_R_System.ResourceDomainORWorkgroup, SMS_R_System.LastLogonUserDomain, SMS_R_System.LastLogonUserName, SMS_R_System.SMSUniqueIdentifier, SMS_R_System.ResourceId, SMS_R_System.ResourceType, SMS_G_System_OPERATING_SYSTEM.WindowsDirectory from SMS_R_System inner join SMS_G_System_OPERATING_SYSTEM on SMS_G_System_OPERATING_SYSTEM.ResourceID = SMS_R_System.ResourceId where SMS_G_System_OPERATING_SYSTEM.WindowsDirectory = "C:\\WINDOWS"That said, it is a problem that needs to be fixed. No such problem in SMS 2003.

I did validate with dev that this seems to be a regression of functionality. So Kim, go ahead and file a bug and we'll see what happens with it.