There might be the scenario where you will be looking for computers which doesnt have particular application installed on.Create a new collection and copy the below  simple WQL query which list you all computers there by you can advertise the application package onto it. select SMS_G_System_SYSTEM.Name from  SMS_R_System inner join SMS_G_System_SYSTEM on SMS_G_System_SYSTEM.ResourceID = SMS_R_System.ResourceId where SMS_G_System_SYSTEM.Name…

There are some warnings under component system for MP_control_manager bcz of client machine are not approved and MP is rejecting the policys that are requesting from the client (MP has rejected a policy request from GUID:d0400dcb-68a9-4b64-92af-daa70db2a53a because it was not approved. The operating system reported error 2147942405: Access is denied.) It might be difficult in…

this post is just to make the application deployment easier.when you deploy any application to a collection,you might see faliure,no status and waiting.I had similar issues(number count was more).This collection gives you list of systems with faliure/no status/waiting status for particular advertisement.if you need more ,just customise it. Collection: select sys.ResourceID,sys.ResourceType,sys.Name,sys.SMSUniqueIdentifier,sys.ResourceDomainORWorkgroup,sys.Client from sms_r_system as sys inner…

If you are looking for a collection to query all the machines only from a particular OU not the SUB OU .Let say ,I have Top OU called Workstations\comp(120 systems) in eskon.net domain and in turn it has 3 sub OU's OU1(10 systems),OU2(20 systems),OU3(49 systems). Here is the simple query to get machines only from TOP OU called workstations.…

some times its hard to know the systems which are having issues in reporting their inventory and even some systems doesnt reporte anything to the site server though the client is installled on it. Here is the collection which gives you all computers which doesnt report inventory for x days(taken 15days). select SMS_R_System.ResourceID,SMS_R_System.ResourceType,SMS_R_System.Name,SMS_R_System.SMSUniqueIdentifier,SMS_R_System.ResourceDomainORWorkgroup,SMS_R_System.Client from SMS_R_System…

Query based versus Direct membership: Direct membership rules should be created when you want to target a very specific user or SMS client. Direct membership rules are not automatically updatable; therefore, any change of targeted resources is a manual process. If a targeted resource(workstation) is removed from the site database, the associated direct membership rules…