Generated management agents cannot be created successfully in FIM. The MA is visible in the drop down on the Create Management Agent screen, but attempting to configure it results in an "8023090D" error. No other information is available in the Windows event log.

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.

PJ: See BCE-80 for initial discovery and comments for current progress.

We are using an instance of the PowerShell connector to create unique AD accounts which are then to be reimported to FIM to allow the normal FIM Active Directory connector to drive standard inbound/outbound flow rules.

Given we can't easily implement a delta import mechanism for AD, and that the only changes we're interested in checking are the ones made by Identity Broker itself, is it OK to perform say the following lines at the end of the ADD.PS1 script?

$entity['sAMAccountName'] = $sAMAccountName
$entity['mailNickname'] = $mailNickname
$entity.Commit()

The LoggingEngineConfigurationViewInformation currently validates out negative numbers, which is the mechanism for keeping log files indefinitely.

A check box should be added to the UI to allow for keeping log files indefinitely. Determine whether the log writers should be changed to use this new boolean option, or whether the negative value should be kept at that level.

Update the logging pages on documentation.