In a scenario where multiple imports occur within a connector group and the system time enters an exclusion period whilst there are still operations which are queued, Which has precedence over whether or not an import operation will occur?

The connector group queue or the dailyExclusion.

The contact search should allow for filters to be set as large searches can time out.

The following fields can be filtered on:

• City
• ClientCode
• CompanyName
• ContactName
• Country
• Department
• Email
• ExcludeCategoryIDs (multiple separated by semi-colon)
• FirstName
• FolderId
• IncludeCategoryIDs (multiple separated by semi-colon)
• JobTtle
• LastName
• PhoneNumber
• PostalCode
• State

The following options can be considered:

1. Multiple values for the same field are OR'd, different fields are AND'd. This would be achieved with multiple requests for each filter and field, with different fields union'd and the intersection of each field being the result.
2. Multiple values for the same field only.
3. Multiple values for FolderId only.
4. One value for FolderId only.

Currently the default provisioning script relies on "good" data being passed to it. Some changes that should be made:

• Check that all required fields (Person Number, given names, sn, termination state etc) are present
• Include an easy configuration option at the top to specify a particular PersonNumber or department so it's clear how LITE can be tested gradually.
• Include userPrincipalName in script

Hi Product Team,

On some import change imports from MA to Adapter, the import on the adapter keeps status is marked as running regardless if it has been completed

Screenshot attached

Schedules not running as shown to Tony.
May be related to TATTS-25, however the configurations were changed as advised.

Logs to be uploaded shortly.

I’m troubleshooting an issue at TAFE where the Unify web service for managing user profiles is throwing HTTP400 errors currently and was hoping you might be able to provide some guidance on where to look next.

On Richard’s advice I’ve done a WCF trace capture from the Identity Broker side and have found the following error occurring:
System.Net.Sockets.SocketException (0x80004005): An existing connection was forcibly closed by the remote host
at System.Net.Sockets.NetworkStream.Read(Byte[] buffer, Int32 offset, Int32 size)

I’ve looked through the Sharepoint logging and not found anything indicating what could be happening – therefore was hoping that you might be able to advise if there is a way to capture logs/debug the Unify solution that has been deployed within Sharepoint.

This is a continuation of the CIT / SSICT implementation.

Updates pushed into Identity Broker from FIM aren't presented to NIM as updates.

Here is an extract of the NIM DirXML logs that shows the error message:

5/06/2012 15:04:36.12v: 0 CIT Driver L3 PT:UnifyPublicationShim: polling
5/06/2012 15:04:36.12v: 0 CIT Driver L3 PT:UnifyPublicationShim: createWebServiceInterface: URL: http://192.168.16.230:59990/IdentityBroker/NIMDriver.svc?wsdl
5/06/2012 15:04:36.12v: 0 CIT Driver L3 PT:UnifyPublicationShim: createWebServiceInterface: Creating service
5/06/2012 15:04:36.13v: 0 CIT Driver L3 PT:UnifyPublicationShim: createWebServiceInterface: Creating interface
5/06/2012 15:04:36.14v: 0 CIT Driver L3 PT:UnifyPublicationShim: createWebServiceInterface: Returning port
5/06/2012 15:04:36.69v: 0 CIT Driver L3 PT:UnifyPublicationShim: javax.xml.ws.soap.SOAPFaultException: Specified method is not supported.

Placeholder connectors with no key set will fail during export due to a ArrayOutOfBoundsException.

Instead, the service should not start if there is no key.

I know we've had issues with this one in the past, but as FIM/TeamCity are two prominent examples of it seeming possible and we generally only target 2008 R2 + these days we should take another look.

Custom actions may also have been a problem before because of 2008 certification, but 2012 only suggests the following is not allowed:

Nested install custom actions (type 7, 23, and 39)

EDIT: This would be in the form of a checkbox where people can opt out.

IdB provides meaningless GUIDs instead of name when reporting errors in UI. Need to provide name of connector or adapter.

Example:
Adapter import all entities for adapter e14dde8a-73ff-4723-acbd-b34f5cb38ac0 failed with reason EMAIL_ADDR is not a valid LDAP attribute name Parameter name: attributeName. Duration: 00:00:01.1860000