Presently operation lists appear to be ordered according to the time they were created. This should be changed to alphabetical order to provide a more intuitive interface for the administrator.

I'm migrating an EvB2 config to EvB3. In EvB2 there's a command shell wrapper that calls the doconvert.exe plugin. I know I have access to powershell scripting from EvB3 but I'm not quite sure what doconvert.exe does. Converts xml to w7 logging or something? Is there an equivalent version of this for EvB3 and/or how else should I go about replicating the actions it took?

From ENVIRON-26, try and find a more descriptive hint for the Server field.

The current hint says "The full name of the server being connected to". It may have to mention that the non-standard port number should be included. If possible mention that a test tool can help diagnose the correct settings (eg ADSI Edit or LDP.exe).

Where is EventBrokerService.exe.config referred to for creating Identity Broker Agent, https://unifysolutions.jira.com/wiki/display/EB300/Identity+Broker.

The document does not state that I need to create on and file search could not find "EventBrokerService.exe.config" under either "<Program Files>\UNIFY Solutions" or "<Program Files (x86)>\UNIFY Solutions"

The MIIS Toolkit's Clear Run History feature does not seem to be compatible with FIM 2010. As such, the MIIS Clear Run History plugin will not work if it uses this mechanism. There is a version of this tool that comes with the plugin, however, and this should be tested for compatibility with FIM, or should be updated to perform correctly.

In the event that the feature is not compatible, a new mechanism should be instated to clear the run history. Estimate includes this work.

To overcome the issue of not being able to detect when a full sync is required following a policy/rule change on the FIM portal, a custom workflow is to be created. The workflow will be used to run a baseline operation list in Event Broker in the event a rule change occurs, and a standard delta operation in the event that a data change occurs. The workflow should be attached to the existing workflow which states that Administrators can change rules using the portal.

This involves the creation of further research, design and creation of workflow and UI components, as well as creation of a separate installer.

The UI component contains the configuration for the custom activity in the FIM workflow engine. The activity will be attached to a workflow object which will be invoked by attaching the respective policy to the existing policy defining what occurs following rule and data changes (Admins can change rules).

There are instances where a particular operation list needs to be tested, without the interference of global or MA startups/schedules. At present, each must be disabled one at a time before the desired op list can be tested. It would be nice if you were able to select multiple MAs/lists at a time for disabling/enabling

The operation list copy button should appear on the Operation\OperationList page, along with the other buttons next to the name of the operation list.

Please use appropriate permissions to determine the visibility of the button.

Thanks.

The following entities can have multiple instances created with the conflicting names:

• Agents
• Operation Lists
• Groups

When creating a Identity Broker agent, you get two rather bewildering "endpoint configuration" text boxes.

Now I know what values should go in there, but most people are not going to have any idea. I note that you get suggested values when you just submit, but a lot of people are going to baulk at this point.

Might it be a good idea to prepopulate with the default values?