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.

The MaxReceivedMessageSize is being surpassed for large imports - ~500,000 entities and upwards.

A quick fix is to simply edit the MaxReceivedMessageSize to be its maximum value:

maxReceivedMessageSize = "2147483647"

However, this may only be hiding a more ingrained systematic problem - Why is the IDB Service sending a SOAP message that would surpass the recommended configuration?.

A determination needs to be made about the correct course of action with regards to this behaviour.

I have the same issue with the lack of a smallint/short validator as documented in IDB-70. There is mention of a workaround, but no details. Can someone help me out?

Looking at https://unifysolutions.jira.com/wiki/display/SUBIDB/Downloads, I only see an x86 version of the Management Studio.

Is there a 64-bit version? If not, can one be created?

What's the impact of using an x86 version in an x64 environment?

Can Identity Broker be configured to send e-mail log notifications of errors?