Site Maintenance this evening The site will be offline for hosting changes. Time TBC

+ Post New Thread
Results 1 to 13 of 13
Windows Server 2008 R2 Thread, Item Level Targetting in Technical; Hello all, I'm having real difficulty getting Item Level Targetting to work properly. My opinion of it is diminishing quickly ...
  1. #1

    Michael's Avatar
    Join Date
    Dec 2005
    Location
    Birmingham
    Posts
    9,262
    Thank Post
    242
    Thanked 1,568 Times in 1,250 Posts
    Rep Power
    340

    Item Level Targetting

    Hello all,

    I'm having real difficulty getting Item Level Targetting to work properly. My opinion of it is diminishing quickly as it just does what it feels like!

    Under the Curriculum OU, under Computer Config, I've created a new Scheduled Task as follows:

    Name: Shutdown Workstations
    Run: %SystemRoot%\System32\Shutdown.exe
    Arguments: -f -s -t 120

    On the Common tab, I've enabled Item Level Targetting and I've tried the following:

    Organizational Unit, specified the Curriculum OU and ticked 'Direct member only'.

    This shuts down all workstations, even if they're in a separate OU (not a sub OU). Any ideas why this is?

    I then tried IP Address Range and specified 192.168.0.100 to 192.168.0.200

    I have some workstations setup with static IPs outside of this scope 192.168.0.91, 92, 93 etc...

    This also seems to shutdown all workstations, even if they're outside of the scope (as above). Any ideas why this is?

  2. #2

    Join Date
    Feb 2007
    Location
    Four Oaks
    Posts
    283
    Thank Post
    37
    Thanked 10 Times in 9 Posts
    Rep Power
    21
    Use Item Level Targetting all the time in various ways - Ive never ticked the 'Direct member only' option though....try with out this option. Just selecting the OU has always worked for me.

  3. #3

    Michael's Avatar
    Join Date
    Dec 2005
    Location
    Birmingham
    Posts
    9,262
    Thank Post
    242
    Thanked 1,568 Times in 1,250 Posts
    Rep Power
    340
    I've tried it ticked and unticked, yet it still shuts down everything.

    I can re-create this problem on three different networks. It looks like a bug to me...

  4. #4
    Admiral208's Avatar
    Join Date
    Mar 2008
    Location
    Bridgwater
    Posts
    720
    Thank Post
    176
    Thanked 63 Times in 55 Posts
    Rep Power
    40
    if you apply the GPO to the just the curriculum OU, why are you using item level targeting? Which computers are you trying to shutdown? It wont apply to computers outside of the OU.

  5. #5

    Michael's Avatar
    Join Date
    Dec 2005
    Location
    Birmingham
    Posts
    9,262
    Thank Post
    242
    Thanked 1,568 Times in 1,250 Posts
    Rep Power
    340
    I've found a workaround, hope this helps someone else.

    Imagine there are 4 seperate OUs (not sub OUs), all with their own separate GPOs.

    OU 1, GPO 1
    OU 2, GPO 2
    OU 3, GPO 3
    OU 4, GPO 4

    Under OU 1, under Computer Config > Preferences, I've created a new Scheduled Task as follows:

    Name: Shutdown Workstations
    Run: %SystemRoot%\System32\Shutdown.exe
    Arguments: -f -s -t 120

    I then applied Item Level Targetting which clearly does not work in this case. For some weird reason, the Shutdown Workstations policy was appearing on workstations not in or linked to OU 1, GPO 1.

    The workaround is quite simple. Copy the Shutdown Workstations policy to the other remaining GPOs - GPO2, GPO3 and GPO4.

    Right click Shutdown Workstations and change the Action to 'Delete'. Just make sure the policy remains Enabled and not Disabled.

    Now either restart the workstation or run gpupdate /force and like magic it works.

  6. #6

    Michael's Avatar
    Join Date
    Dec 2005
    Location
    Birmingham
    Posts
    9,262
    Thank Post
    242
    Thanked 1,568 Times in 1,250 Posts
    Rep Power
    340
    Quote Originally Posted by Admiral208 View Post
    if you apply the GPO to the just the curriculum OU, why are you using item level targeting? Which computers are you trying to shutdown? It wont apply to computers outside of the OU.
    This is precisely my point. IT IS applying to workstations outside the OU. I have reported this to Microsoft.

  7. #7
    Admiral208's Avatar
    Join Date
    Mar 2008
    Location
    Bridgwater
    Posts
    720
    Thank Post
    176
    Thanked 63 Times in 55 Posts
    Rep Power
    40
    fine, but my question still stands. why are you using item level targeting in this case?

    This should be used to narrow down the number of computers in an OU that the policy is applied to. If you apply the gpo to an OU normally, you wouldnt use item level targeting?

  8. #8
    Admiral208's Avatar
    Join Date
    Mar 2008
    Location
    Bridgwater
    Posts
    720
    Thank Post
    176
    Thanked 63 Times in 55 Posts
    Rep Power
    40
    Also, can you run a gpresult on a computer outside of the ou to see if it is being applied?

  9. #9

    Michael's Avatar
    Join Date
    Dec 2005
    Location
    Birmingham
    Posts
    9,262
    Thank Post
    242
    Thanked 1,568 Times in 1,250 Posts
    Rep Power
    340
    fine, but my question still stands. why are you using item level targeting in this case?
    Because the policy was applying to workstations outside of OU1.

    Also, can you run a gpresult on a computer outside of the ou to see if it is being applied?
    I have done this and gpresults come back normal. The policy I set isn't there/visible which is correct, yet the task is been applied. It's really odd.

  10. #10
    Admiral208's Avatar
    Join Date
    Mar 2008
    Location
    Bridgwater
    Posts
    720
    Thank Post
    176
    Thanked 63 Times in 55 Posts
    Rep Power
    40
    OK, so the policy was applying to computers outside of the OU before you applied item level targeting to the GPO? You made it sound like the error was caused because you had item level targeting applied.

    can you run a group policy result in the GPMC to see where the computer is getting the shutdown task from.

  11. #11

    Michael's Avatar
    Join Date
    Dec 2005
    Location
    Birmingham
    Posts
    9,262
    Thank Post
    242
    Thanked 1,568 Times in 1,250 Posts
    Rep Power
    340
    Apologies for not being clearer. Yes the problem was there, so I then explored Item Level Targetting.

    I've ran the Group Policy result (just on computers outside the OU) and again, nothing comes up.

  12. #12
    Admiral208's Avatar
    Join Date
    Mar 2008
    Location
    Bridgwater
    Posts
    720
    Thank Post
    176
    Thanked 63 Times in 55 Posts
    Rep Power
    40
    could you turn the policy into a batch file and run that as a scheduled task?

  13. #13

    Michael's Avatar
    Join Date
    Dec 2005
    Location
    Birmingham
    Posts
    9,262
    Thank Post
    242
    Thanked 1,568 Times in 1,250 Posts
    Rep Power
    340
    I could, but I have found a workaround in post 5. Essentially I've created a conflict of policy, so the setting per GPO takes precedence.

    I have tested this running gpupdate /force and a normal restart and it does work properly. That's the main thing! Thank you for your suggestions though.

SHARE:
+ Post New Thread

Similar Threads

  1. ICT Technician / Teaching Assistant Level 3
    By steve in forum Educational IT Jobs
    Replies: 20
    Last Post: 31st January 2006, 03:31 PM
  2. Replies: 0
    Last Post: 13th January 2006, 10:55 AM
  3. Replies: 2
    Last Post: 12th January 2006, 09:32 AM
  4. Replies: 8
    Last Post: 2nd November 2005, 02:46 PM
  5. Wireless signal Levels
    By ChrisH in forum Wireless Networks
    Replies: 2
    Last Post: 19th July 2005, 09:08 AM

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •