Re: software deployment via GPO



Hi,

Group Policy consists of two parts.

·Computer Configuration. Computer-related policies specify operating
system behavior, desktop behavior, application settings, security
settings, assigned applications options, and computer startup and
shutdown scripts. Computer-related policy settings are applied when the
machine is rebooted and during a periodic refresh of Group Policy.

·User Configuration. User-related policies specify operating system
behavior, desktop settings, application settings, security settings,
assigned and published applications options, user logon and logoff
scripts, and folder redirection options. User-related policy settings
are applied when users log on to the computer and during the periodic
refresh of Group Policy


Any setting placed under the Computer configuration will affect the
Computer object.
Any setting placed under the User configuration will affect the user
object.
So if you wish to deploy to a computer, you must set this setting
within the Computer configuration of the group policy at the same time,
the computer must have read and apply group policy permissions on the
group policy object. The computer object must also be placed below or
within the OU you have linked this group policy to.

Same thing goes with the user.

Good Luck

Harj Singh
Power Your Active Directory Investment
www.specopssoft.com


j_j_ford@xxxxxxxxxxx wrote:
Darren Mar-Elia (MVP) wrote:
I'm a little confused by your description. You say you're deploying the
package to computers but then you also say you're using user groups to
filter its effect. That's not going to work. If its a computer-assigned
package, then you have to control which computers will read the GPO, not
users. The reason gpresults says its empty is that you have nothing in the
per-user part of that GPO (at least, that's what I'm assuming from your
description). If you want to control which *users* get a package, then you
need to deploy that package per-user (under the User Configuration side of
the GPO).

Darren


Posting via google...

I guess where my confusion is at is in the ability to deploy to
computers. Yes, I would like to deploy to the computers. I was able
to get the deployment to work when I added the deployment to the Users
software policy.

I would like to deploy based on computers, but I guess I don't really
understand how to do that.

.



Relevant Pages

  • Re: Do Not Execute Group Policy for Admins Group
    ... The intent of policy loopback is to replace or merge user configuration ... The computer configuration settings from this list are applied to the ... > so that the group policy will only apply to a certain group of users ...
    (microsoft.public.win2000.group_policy)
  • Re: Computer vs. User configuration
    ... "It is not that you can not configure a Group Policy with settings enabled ... Your explanation of a top level GPO with no override filtering down to ... scenario I can imagine having both user and computer configuration settings ...
    (microsoft.public.windows.group_policy)
  • Re: make domain GP not apply to local computer?
    ... down the system which is "computer" configuration Group Policy. ... then a different GP can be set for the laptop computers to allow users to ... normal Group Policy user configuration settings in a merge or replace mode. ...
    (microsoft.public.windowsxp.security_admin)
  • RE: Several Problems; how to reset security and troubleshoot serve
    ... On the SBS security settings; I accept your response, ... On the Remote Assistance Issue I have check all of the settings as you ... What started me on the path of security problem was I had a simular problem ... Start the Microsoft Management Console Group Policy snap-in. ...
    (microsoft.public.windows.server.sbs)
  • Re: iNTERACTIVE LOGON welcome screen - make it go away
    ... I created a custom ADM file for these two settings ... and imported it into the GPO under the Computer Administritative templates. ... really great expertise in Group Policy often reply to posts including ... doing a gpupdate on that domain controller which ideally would be the ...
    (microsoft.public.windowsxp.security_admin)