Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 11 replies
  • Subscribers 1 subscriber
  • Views 8267 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

How to apply policies to all sub-groups?

faygate

Been wondering for weeks why my client computers haven't been picking up my policies and it turns out that even if you set the policy at the top of the group any sub-groups underneath do not automatically get the same policies. Fine if you've got a small setup, not so great if you're syncing with a complicated Active Directory structure.

Does anyone know how to do this in Enterprise Console 4.0 or even with an SQL script? Can't find an option anywhere which I think is a bit lame.

:1719


This thread was automatically locked due to age.
Parents
  • 0
    QC wrote:

    Understandable. But equally understandable is to expect that a sub-group for which you have created/set a special policy retains this policy. An old argument and while in theory you can have it all (well, almost all) the price is complexity with which you'd have to cope.

    Keep in mind that while the current behaviour may be a nuisance (ex-)changing policies not something you do on a regular basis. And as long as you don't have dozens or hundreds of groups (and the the question is - what for?) it's not a Herculean task.

    Please don't make assumptions about other people's Active Directory structure.  Different companies set up their Active Directory structure in different ways.  My company decided to set it up similar to this:

    Systems

    Systems
   ^--> Desktops
          ^--> Office 1
          ^--> Office 2
          ^--> Office ...
          ^--> Office N
   ^--> Laptops
          ^--> Office 1
          ^--> Office 2
          ^--> Office ...
          ^--> Officen
   ^--> Servers
          ^--> Office 1
          ^--> Office 2
          ^--> Office ...
          ^--> Office N

    If I want to create a new "Desktops" policy, the current product requires me to change the Policy on every single "Office" group under the Desktop section.  This becomes non-trivial after X numbers of offices.  

    My assumption would be that a policy defined at an upper level filters all the way down unless it is specifically overridden at a lower level.  This would still allow you to manually specificy a policy for a particular group.

    :1904
Reply
  • 0
    QC wrote:

    Understandable. But equally understandable is to expect that a sub-group for which you have created/set a special policy retains this policy. An old argument and while in theory you can have it all (well, almost all) the price is complexity with which you'd have to cope.

    Keep in mind that while the current behaviour may be a nuisance (ex-)changing policies not something you do on a regular basis. And as long as you don't have dozens or hundreds of groups (and the the question is - what for?) it's not a Herculean task.

    Please don't make assumptions about other people's Active Directory structure.  Different companies set up their Active Directory structure in different ways.  My company decided to set it up similar to this:

    Systems

    Systems
   ^--> Desktops
          ^--> Office 1
          ^--> Office 2
          ^--> Office ...
          ^--> Office N
   ^--> Laptops
          ^--> Office 1
          ^--> Office 2
          ^--> Office ...
          ^--> Officen
   ^--> Servers
          ^--> Office 1
          ^--> Office 2
          ^--> Office ...
          ^--> Office N

    If I want to create a new "Desktops" policy, the current product requires me to change the Policy on every single "Office" group under the Desktop section.  This becomes non-trivial after X numbers of offices.  

    My assumption would be that a policy defined at an upper level filters all the way down unless it is specifically overridden at a lower level.  This would still allow you to manually specificy a policy for a particular group.

    :1904
Children
No Data