[gptalk] Re: WMI Filters

  • From: jfvanmeter@xxxxxxxxxxx
  • To: gptalk@xxxxxxxxxxxxx, <gptalk@xxxxxxxxxxxxx>
  • Date: Fri, 26 Sep 2008 17:59:36 +0000

Hello everyone, 

if the Win32_Product is  very slow ,   would the win32reg_addremoveprograms 
have the same problem?

I was going to create a filter to apply my Office 2007 GPO, based on the 
following 

Select * from win32reg_addremoveprograms where displayname like  "%Microsoft 
Office Enterprise 2007%"

I've tested the filter in a virtual domain and it applies correctly to a 
standard XP workstation build. 

--
"When the legend becomes fact, print the legend." 


 -------------- Original message ----------------------
From: "Thomas Marantz" <TomMarantz@xxxxxxxxxxxxxxxx>
> Great thanks for all the info. 
> 
> You are correct, GP times have been too long. 
> 
> I may just use security filtering.
> 
>  
> 
> From: gptalk-bounce@xxxxxxxxxxxxx [mailto:gptalk-bounce@xxxxxxxxxxxxx] On 
> Behalf 
> Of Darren Mar-Elia
> Sent: Friday, September 26, 2008 10:23 AM
> To: gptalk@xxxxxxxxxxxxx
> Subject: [gptalk] Re: WMI Filters
> 
>  
> 
> If you are trying to exclude machines that have Office 2007 already installed 
> (or more specifically have Office 2003 installed), then something like this 
> might work, though Iâ??m not in front of a machine to test it:
> 
>  
> 
> SELECT * FROM Win32_Product WHERE Caption LIKE "%Microsoft Office%" AND 
> Caption 
> LIKE "%2003%"
> 
> That would likely evaluate to true only if Office 2003 were there. 
> 
> Also, keep in mind that for whatever reason, my experience with enumerating 
> Win32_Product is that its very slow if you have a fair number of apps on a 
> system. So, keep an eye on GP Processing time after implementing this as it 
> could go to minutes.
> 
>  
> 
> Darren
> 
>  
> 
>  
> 
> From: gptalk-bounce@xxxxxxxxxxxxx [mailto:gptalk-bounce@xxxxxxxxxxxxx] On 
> Behalf 
> Of Frank
> Sent: Friday, September 26, 2008 9:46 AM
> To: gptalk@xxxxxxxxxxxxx
> Subject: [gptalk] Re: WMI Filters
> 
>  
> 
> You want to prevent installation of Office 2007 onto workstations that have 
> Office 2003 installed already?
> 
> My understanding of WMI filters (as applied to a GPO) is that if the query 
> returns anything, then (you've got a "true" and) the condition is met, which 
> makes it tricky to negate something like the presence of a product, as 
> opposed 
> to something simple like "has more than 512mb of RAM".  --If I'm wrong, 
> please, 
> pretty please shed some light here!!!  (I beg of you!) 
> 
> Another thing you could do is use/create an MST onto 2007 that adds an 
> Install 
> Condition making sure there's no other Office version installed before 
> proceeding.  Otherwise perhaps basing your query around the Office 2003 
> Product 
> code might help.
> 
> f.
> 
> On Fri, Sep 26, 2008 at 12:16 PM, Thomas Marantz 
> <TomMarantz@xxxxxxxxxxxxxxxx> 
> wrote:
> 
> I have an Office 2007/2003 environment.
> 
> I have deployed Office 2007 compatibility pack for Office 2003 workstations.
> 
> I've been trying to get a Filter to block installation on Office 2007 
> workstations, here is what I haveâ?¦
> 
> Root\CIMv2
> 
> SELECT * FROM Win32_Product WHERE (Caption LIKE "Microsoft Office%2003%")
> 
>  
>
--- Begin Message ---
  • From: "Thomas Marantz" <TomMarantz@xxxxxxxxxxxxxxxx>
  • To: <gptalk@xxxxxxxxxxxxx>
  • Date: Fri, 26 Sep 2008 17:35:27 +0000

Great thanks for all the info.

You are correct, GP times have been too long.

I may just use security filtering.

 

From: gptalk-bounce@xxxxxxxxxxxxx [mailto:gptalk-bounce@xxxxxxxxxxxxx] On Behalf Of Darren Mar-Elia
Sent: Friday, September 26, 2008 10:23 AM
To: gptalk@xxxxxxxxxxxxx
Subject: [gptalk] Re: WMI Filters

 

If you are trying to exclude machines that have Office 2007 already installed (or more specifically have Office 2003 installed), then something like this might work, though I’m not in front of a machine to test it:

 

SELECT * FROM Win32_Product WHERE Caption LIKE "%Microsoft Office%" AND Caption LIKE "%2003%"

That would likely evaluate to true only if Office 2003 were there.

Also, keep in mind that for whatever reason, my experience with enumerating Win32_Product is that its very slow if you have a fair number of apps on a system. So, keep an eye on GP Processing time after implementing this as it could go to minutes.

 

Darren

 

 

From: gptalk-bounce@xxxxxxxxxxxxx [mailto:gptalk-bounce@xxxxxxxxxxxxx] On Behalf Of Frank
Sent: Friday, September 26, 2008 9:46 AM
To: gptalk@xxxxxxxxxxxxx
Subject: [gptalk] Re: WMI Filters

 

You want to prevent installation of Office 2007 onto workstations that have Office 2003 installed already?

My understanding of WMI filters (as applied to a GPO) is that if the query returns anything, then (you've got a "true" and) the condition is met, which makes it tricky to negate something like the presence of a product, as opposed to something simple like "has more than 512mb of RAM".  --If I'm wrong, please, pretty please shed some light here!!!  (I beg of you!)

Another thing you could do is use/create an MST onto 2007 that adds an Install Condition making sure there's no other Office version installed before proceeding.  Otherwise perhaps basing your query around the Office 2003 Product code might help.

f.

On Fri, Sep 26, 2008 at 12:16 PM, Thomas Marantz <TomMarantz@xxxxxxxxxxxxxxxx> wrote:

I have an Office 2007/2003 environment.

I have deployed Office 2007 compatibility pack for Office 2003 workstations.

I've been trying to get a Filter to block installation on Office 2007 workstations, here is what I have…

Root\CIMv2

SELECT * FROM Win32_Product WHERE (Caption LIKE "Microsoft Office%2003%")

 


--- End Message ---

Other related posts:

  1. Home
  2. gptalk
  3. Archive
  4. 09-2008