Hi,
I'm looking for some guidance on how to best remove select individual Office features across our enterprise (on a mutt mix of 2010 32bit (on x32 and x64 OS'), 2013 32bit (on x32 and x64 OS') and 2013x64. I have been asked to remove InfoPath from all machines. I have deduced through research thus far that I can A) Use a /modify with config.xml or B) msiexec /p <path to msp file>. I did not have much luck learning how to create a config.xml file properly so I opted to use the MSP I created with OCT to remove the features and it has proven successful via a non suppressed Run line test of it on a system.
The problem I'm having now is with SCCM and deploying the application... option B above to systems. I believe the isasue I'm encountering is the "Detection Method" being the product code for the targeted suite in question, may be seeing that... Oh Hey, you already have Office 2xxx so I'm not going to run this program! Can someone enlighten me on a more simple approach?
The other caveat I'm having trouble wrapping my head around is that in general nobody should have MS Access either for sake of Enterprise DB solutions except for a small minority of departmental computers that must still use Access DB's. Since obviously it is simply On or Off with a feature I'm wondering how I can deploy this to remove Access from the vast majority while keeping it for a select few. I'd imagine I'd need to do some manual detective work to get some hostnames and then some Device Collection creation and segregation to deploy selectively to... the other thought is how I might be able to isolate these systems possibly with Software Metering to find out who has launched Access.exe in X amount of days. Any help on the technical and suggestions on all else would be greatly appreciated.
Thanks, Ryan.
Ryan Plieth
Update: I found out how to query and form a collection based on Recently Used App info:
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_CCM_RECENTLY_USED_APPS on SMS_G_System_CCM_RECENTLY_USED_APPS.ResourceID = SMS_R_System.ResourceId where DATEPART(MM, SMS_G_System_CCM_RECENTLY_USED_APPS.LastUsedTime) <= 12 and SMS_G_System_CCM_RECENTLY_USED_APPS.ExplorerFileName = "msaccess.exe"
So now I'm just hoping to get information on how to get the MSIEXEC /P .MSP file to actually deploy to systems that already have Office detected.