Personal preference here, but I'd like to see deletes (of groups, operations etc) handled only after a confirmation of the action is given by the user. It might save tears if the user selects the wrong one first up (after that its fair game).

I wouldn't care if it was a popup on the same page or if you redirect to a confirmation page. Either would do the trick.

A minor fix that would remove any confusion about whether the alert is describing the current or past run of the operation list.

A determination needs to be made whether log files should display non-standard characters such as,

Check operations are not being included when an Operation list is copied.

The FIM auto-configuration would be made more helpful if operation list comments describing the purpose of the operation lists were added when the wizard was run.

If the Event Broker scheduler is in a 'Started' state, and it becomes unlicensed, the scheduler will maintain this state until the service is restarted

.

To reproduce this behaviour:

1. Start the EventBroker service
2. Ensure that the scheduler has started
3. Add a license that expired before the day of reading.
4. Ensure that the Event Broker instance is now unlicensed and that the scheduler has maintained this state.

The check operation added will overwrite the existing check operation.

A few issues were found when playing with operation list functions in IE9 to see what more expansive operation lists would look like in the browser. These include:

• If an operation is moved below an operation with children, all the children disappear (the root operation remains)
• I had an operation with 3 levels (root, child, then 2 children of the child). I "moved down" one of the 2 children, and it cleared all children, leaving only the root
• Operations cannot be promoted at any level, whether added initially as children, or demoted to become a child
• After performing the above tests in IE9, the operations functions menu became unresponsive and the browser could not contact the running Event Broker service. I was not able to replicate this after performing a far larger test using IE9, however (ie. adding more children, moving and demoting some operations).

While IE9 for the most part seems to have fields a bit closer together than in Chrome, the Create Group and LDAP Directory Agent pages have no spaces between key fields. See attached screenshots.

When you install or uninstall Event Broker on a machine with UAC active (eg. Windows 7), the MSI name in the Program Name field when installing, repairing, or uninstalling, is an unintelligible collection of letters and numbers (eg. 8eb628.msi). The publisher is correctly verifiable, but should this be the name of the Event Broker MSI rather than this name?