There are 2 ways of accomplishing this task. One is through Hardware Inventory (recommended) and the other is through Software Inventory.
Hardware Inventory:
The deployment kit creates an entry in ADD/Remove Programs that can be used to create a collection. Create a Query based collection with the following WQL information:
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 inner join SMS_G_System_ADD_REMOVE_PROGRAMS on SMS_G_System_ADD_REMOVE_PROGRAMS.ResourceID = SMS_R_System.ResourceId inner join SMS_G_System_ADD_REMOVE_PROGRAMS_64 on SMS_G_System_ADD_REMOVE_PROGRAMS_64.ResourceId = SMS_R_System.ResourceId where SMS_G_System_ADD_REMOVE_PROGRAMS.DisplayName = "Microsoft Office 2010 Deployment Kit for App-V" and SMS_G_System_ADD_REMOVE_PROGRAMS_64.DisplayName = "Microsoft Office 2010 Deployment Kit for App-V"
This will populate the collection with all the machines that have the APP-V Deployment Kit for Office 2010 installed.
Software inventory:
With this option you will need to inventory an executable to be able to get an inventory and know if its installed or not. For this to work you need to inventory for one of the files created by the deployment kit. One example would be virtualOwsuppmanager.exe which is located in the following path:
C:\program files\common files\microsoft shared\virtualization handler
You can use a WQL query to populate the collection like the following:
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 inner join SMS_G_System_SoftwareFile on SMS_G_System_SoftwareFile.ResourceId = SMS_R_System.ResourceId where SMS_G_System_SoftwareFile.FileName like "VirtualOWSSuppManager.exe"
This will populate the collection with all the machines that have the APP-V Deployment Kit for Office 2010 installed.