SCCM 1610 - Software Updates - Office 2016 Questions

[CHiLL]

I'm creating a Task Sequence to deploy Windows 10 Education 1607 x64 along with Office 2016 Professional Plus (not click-to-run). Whilst I've created the Task Sequence to do this - I'm a little confused to how to deploy Office 2016 Software Updates.

 

I have Software Update groups created and the ADR set up - that's not the problem. The problem is targetting specific machines with this version of Office. I understand how the OS Software Updates works - Create a device collection to target just that OS and deploy your OS Software Updates to that device collection - done. However, I don't want to target an OS device collection. I want to target only machines that have Office 2016 Professional Plus on.

 

What is the best way to do this? With a device collection for only Office 2016 Professional Plus installations? If so, what targeting method should I use? One to look for the installation folder? WMI/WQL? Something like this?

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 where SMS_G_System_ADD_REMOVE_PROGRAMS.DisplayName = "Microsoft Office Professional Plus 2016"

 

I just want to avoid our clients that don't have Office 2016 Professional Plus installed to download and attempt to process these updates.

[sparkeh]

What is the best way to do this? With a device collection for only Office 2016 Professional Plus installations?

Yeah that's how I do it.

 

Not tested your query but it looks like the right kind of thing

[CHiLL]

Yeah that's how I do it.

 

Not tested your query but it looks like the right kind of thing

Cheers. One other question;

I have a collection for all our Windows x clients. For OS Software Updates, is it worth just using this one collection? Or should I create a duplicate collection specifically for Software Updates? I'd prefer to avoid duplicating my collections, but don't want to risk breaking or effecting our main one. I hope that makes sense.

[sparkeh]

Cheers. One other question;

I have a collection for all our Windows x clients. For OS Software Updates, is it worth just using this one collection? Or should I create a duplicate collection specifically for Software Updates? I'd prefer to avoid duplicating my collections, but don't want to risk breaking or effecting our main one. I hope that makes sense.

Well I kinda think that is down to personal preference. One of the things about sccm is that there are usually multiple ways to skin a cat.

 

Targeting your updates at one big collection won't cause any problems, however, when I had 3 OS's I had a collection for each version to make it neater. Now I have just Win 10 I do still have a separate collection just for targeting software updates.

 

Hope that helps?