This is what's I've done.  But to add computers into the filter, I:

        1. click Add
        2. click Object types
        3. check off Computers
        4. type in "single computer name only" <- this part makes me grr
        5. click OK
        6. repeat the above steps for "each" computer name

For username objects, I can type in several at a time.  This is what I'm
asking about as far as doing a more efficient way.  And it looks like a
separate OU may be it.  Most of my updates are things everyone will get.
But not everyone is on the same version of Office.  So service packs or
updates like the compatibility pack only get deployed to certain computers
that have older versions of office.

-- 
Mike Gill


> -----Original Message-----
> From: Joe Heaton [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, January 02, 2008 9:31 AM
> To: NT System Admin Issues
> Subject: RE: Simple GPO/Application Deployment Question
> 
> That's the way I've done it here Ken.  The Security groups don't have
> to be users, you can make one with computers as the members.  (Last two
> sentences for OP, not Ken...)
> 
> Joe Heaton
> 
> -----Original Message-----
> From: Ken Schaefer [mailto:[EMAIL PROTECTED]
> Sent: Monday, December 31, 2007 9:07 PM
> To: NT System Admin Issues
> Subject: RE: Simple GPO/Application Deployment Question
> 
> I wouldn't be created new OUs for this purpose. It typically goes
> against OU design principles.
> 
> To the OP - why don't you create a Domain Local security group to put
> your computer objects into. Use the security group to filter the GPO.
> 
> That's not to say a "Test OU" isn't a good idea - it can be. But place
> your test machines in there, and then use security groups to filter the
> various GPOs applied to the computers or VMs in the Test OU.
> 
> But I would NOT create an OU just to test this piece of software
> 
> Cheers
> Ken
> 
> -----Original Message-----
> From: Liu, David [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, 1 January 2008 11:29 AM
> To: NT System Admin Issues
> Subject: RE: Simple GPO/Application Deployment Question
> 
> Or, create another OU, dunp computers you want to have update applied &
> link the GPO
> 
> 
> 
> 
> From: Mike Gill [mailto:[EMAIL PROTECTED]
> Sent: Monday, December 31, 2007 7:15 PM
> To: NT System Admin Issues
> Subject: Simple GPO/Application Deployment Question
> 
> 
> I've set up the Office Compatibility update to deploy to those users
> who do not have Office 2007 on our network.  I chose to deploy this
> update based on computer name instead of user.  When I do this, I can
> only select one computer name at a time in the Security Filter.  My
> network is small, but this becomes tedious.  Is there a good practical
> reason I'm not seeing that allows me to select multiple objects at once
> except when it comes to computer names?  There are just a lot of clicks
> involved this way and I would think Admins of a larger network would
> find a better way.
> 
> --
> Mike Gill
> 
> 
> 
> 
> 
> 
> 
> 
> ~ Upgrade to Next Generation Antispam/Antivirus with Ninja!    ~
> ~ <http://www.sunbelt-software.com/SunbeltMessagingNinja.cfm>  ~
> 
> ~ Upgrade to Next Generation Antispam/Antivirus with Ninja!    ~
> ~ <http://www.sunbelt-software.com/SunbeltMessagingNinja.cfm>  ~
> 
> No virus found in this incoming message.
> Checked by AVG Free Edition.
> Version: 7.5.516 / Virus Database: 269.17.13/1207 - Release Date:
> 1/2/2008 11:29 AM
> 
> 
> No virus found in this outgoing message.
> Checked by AVG Free Edition.
> Version: 7.5.516 / Virus Database: 269.17.13/1207 - Release Date:
> 1/2/2008 11:29 AM
> 
> 
> ~ Upgrade to Next Generation Antispam/Antivirus with Ninja!    ~
> ~ <http://www.sunbelt-software.com/SunbeltMessagingNinja.cfm>  ~
> 



~ Upgrade to Next Generation Antispam/Antivirus with Ninja!    ~
~ <http://www.sunbelt-software.com/SunbeltMessagingNinja.cfm>  ~

Reply via email to