BUG: Group Policy Preferences - Scheduled Tasks

Hi,

Given this is reproducable in our environment, I'm going to go out on a limb and say the following is a bug. I'll include the steps below, but in a nutshell, we are finding policy objects populated with more than one Vista or later scheduled task is corrupting the policy file through the addition of duplicate entries.

I'll keep the following detail section short, because, well, it's just past 6pm on Friday, and I just want to get out of here.

Steps:

1. Open GPMC on either a Windows 7 machine or R2 domain controller (tried both just to rule the other out),
2. Create a new policy,
3. Disable the user settings,
4. Edit the policy object,
5. Expand Computer Configuration > Preferences > Control Panel Settings > Scheduled Tasks
6. Select New > Scheduled Tasks (Windows Vista or later),
7. General tab: Fill in the Name, Action = Replace, account name, password, "run whether user is logged on or not"  option selected, "run with the highest priviliges",
8. Triggers tab: Enter any "One time" time schedule that takes your fancy,
9. Actions tab: Enter any action you feel is appropriate - it makes no difference,
10. Conditions tab: Check the Wake the computer to run this task option,
11. Settings tab: Just skip it,
12. Common tab: Check the "Remove this item when no longer used" option, check the "Item-level targetting" option,
13. Common tab: Select the Targetting button, New Item:Computer, Computer Name = whatever you have handy to test on, Netbios radio button selected,
14. Ok button, and Ok button again to get back out to the main editing window,
15. Repeat steps 6 through to 14 to add a second scheduled task,
16. Close the policy editor so that you're not back out at the main GPMC screen.

You should end up with something resembling the following: http://public.bay.livefilestore.com/y1pOnr0-qf0ihv2gX4xiFowTC4hbxQY0y1LakHuPVRDd_DQ6WSKg7vuk_kOTJt_RliD7Kjc31p2oUJMh5B3H4G4Dw/gpmc_EditorScheduledTasks.PNG

Okay, so, what I'm seeing from this point on is as follows:
1. If you immediately inspect the Settings of this policy, instead of seeing correct ordering, you will see a duplicate of the first entry,
(http://public.bay.livefilestore.com/y1pRnNyvWKAZUeGihhBhJzaWlscin-L4gcQnCXHA-vEp5amlR1wgbJevvYpl7Mkomj1uVLAYqMO87RhOWkHuDIq-A/gpmc_SettingsDuplicates.png)
2. If you check the target computer, the correct number of entries appear in Task Scheduler,
(http://7mgp6a.bay.livefilestore.com/y1peSCvQExf6JhdDVW-pcq89zMYrrpVPhY-9r37vUD-94i42zV4w9p-O9KkMyPS8oQbTGM3jlvZYhRT9c_nMiRLO9h5xrVwTIey/gpmc_ClientTaskScheduler.PNG)
3. If you use GPMC to generate a resultant set of policy (under the Group Policy Results node) for that computer minus the user settings, you will get the following error:

An error occurred while generating report:
Index was out of range. Must be non-negative and less than the size of the collection. Parameter name: index
(http://7mgp6a.bay.livefilestore.com/y1pvjanolUi28OGoOTbY_58hpyi3_8k6Nvpu8CzBod0-3P3ATaGpwEU_ISuxE9l91YwAiUvxVGDr4McQlkydYu7YbdGFySJYjeb/gpmc_GPMCError.PNG)

Is this significant? I don't know, but I do know it sure as nuts shouldn't be happening. The nett result is you can't audit that machine if required, and that's just not very useful.

Cheers,
Lain