The LDAP Changes operation fails on execution, as no 'Server' attribute can be found in the operation element.

A message prompt is not generated if a non-existant operation list is added to a group.

To recreate this:

1. Create an operation list.
2. Open the Add operation list to group page.
3. In a separate page - delete an operation list.
4. and finally in the previous page add the deleted operation list to the group.

If the topic EB300:Installing the Event Broker Service is going to suggest that the package can be installed unattended, has anyone tested that this is actually possible?

There is no refresh button available when viewing the Event Broker logging. If the Internet Explorer's Refresh button is used, it goes back to the first page. The view the latest log entries must navigate to the "Last" Page again.

Html can be injected from existing log files stored locally on the service installation.

To demonstrate this behavior:

Include an entry into a log file with a source of "</div><label>This label will be visible in the logs.<label><div>

It's unclear in this state what the 4 hours refers to. See screen shot.

The Identity Broker changes-plug in should have a drop down box of adapters, much like the list of FIM MAs available in the FIM MA plug-in wizard.

"builtin" is not a word, replace with "built-in" as per Wiktionary http://en.wiktionary.org/wiki/built-in

An alert denoting a failed operation list will persist even after that operation list has been removed. This may cause confusion and at present causes errors if the action link in the fault is followed.

When modifying an existing Operation List schedule, the button label is still always "Create" - it should be "Update" (as for Check Operations).

Also, the button label when editing an Operation List is "Save" ... it should be always "Update" or "Save" throughout the product, not a mix.