When running the Identity Broker service using IE8, the buttons across the top are not currently appearing correctly. See attached screenshot.

Upgrade schedule interface to allow for multiple daily and date exclusion periods.

Change the daily exclusion behaviour (in the service) such that an end time that is before a start time will run through to the following day (unit test where possible). Include documentation and tooltips.

The CSV connector has the ability to have a threshold set:

<csvFile path="d:\Aurion\Reports\employees.csv" useThreshold="True" addThreshold="6" deleteThreshold="50"/>

Does this threshold limit apply to other types of Aurion connectors and if so, what's the xml config for them?

Thanks

After uninstalling Identity Broker, I attempted to reinstall it with the database upgrade option. An error appears stating that a constraint could not be dropped. The installer may need to log a better message or not attempt the upgrade if the same database version is found.

The x64 service installer registers the Windows service to start Unify.Service.Connect32.exe rather than Unify.Service.Connect.exe.

I noticed on that the attribute used in our WCF trace configuration switchValue is not mentioned on MSDN http://msdn.microsoft.com/en-us/library/ms229547(v=VS.90).aspx.

Please investigate and either provide similar functionality, or provide alternative.

Thanks.

I configured a CSV logger to point to a drive that did not exist (eg. E:\Logs). On an attempt to perform any Identity Broker operation (such as a connector full import), the service stopped. No messages are logged to the event viewer or Management Studio status messages, and no log file is created on the machine. This does not happen if a directory does not exist, as the logger will create it.

In change detection, add current minimum DateTime to change report.

Remove similar behaviour that has been duplicated in every other transformation.

On occasion (I know this has occurred at the Department of Finance at the very least) when rebooting the operating system, the Identity Broker service fails to start as the services coordinator attempts to start it before SQL Server.

I briefly (read, spent 5 minutes) looked at resolving this somehow, but it became difficult to resolve on the basis putting a dependency to SQL Server service on the Identity Broker service wouldn't work when SQL Server was on another server.

The outcome of this improvement, if possible, is to resolve this potential source of service failure.

Test multi-value concatenation in FIM using a LDIF file import.

Create a default dn generator using the the schema key, using the concatenation from above for multi-values.