Matthew,

No problem.

I'm not sure that FilterForDisconnection will work, as it will just create a simple disconnector - not explicit.

ResolveJoinSearch  might be more appropriate https://msdn.microsoft.com/en-us/library/microsoft.metadirectoryservices.imasynchronization.resolvejoinsearch.aspx 

Set an AD attribute of those that you want to drop or make precedent - then code the rule.

Regards,

Jon. 

-----Original Message-----
From: Discussion for MS IDM tools liks ILM and FIM [mailto:[log in to unmask]] On Behalf Of Akers, Steve
Sent: 28 April 2015 09:32
To: [log in to unmask]
Subject: Re: How to cause a disconnect

We also have the need to occasionally manually disconnect but have had the same thoughts about whether this could be automated or not (it doesn't happen that often so as yet we've just stuck with a manual process to date). 

It sounds like a complex filter rule, the kind of thing I'd perhaps expect to need a bit of code for, I haven't tried it myself but there is a "FilterForDisconnection" method that you can call for each MA, might be worth exploring :

https://msdn.microsoft.com/en-us/library/microsoft.metadirectoryservices.imasynchronization.filterfordisconnection.aspx

If you can somehow cause the old object to be disconnected in code then in theory the new object should automatically join (depending on your join rules).

Steve

-----Original Message-----
From: Discussion for MS IDM tools liks ILM and FIM [mailto:[log in to unmask]] On Behalf Of Matthew Slowe
Sent: 28 April 2015 09:17
To: [log in to unmask]
Subject: Re: How to cause a disconnect

On Mon, Apr 27, 2015 at 05:02:22PM +0000, Jon Bryan wrote:
> Matthew,
> 
> Been messing with something similar in the SharePoint Sync client - helping a colleague. 
> 
> Assuming that the connectors are both coming from the same source and that you want the new connector to join - Make the "wrong" or old connector an "Explicit Disconnector" on the contributing MA.
> 
> Then the new connector should join, as the join criteria should be met. Else use the joiner to force the join.
> 
> If it all goes wrong and you want to re-connect the old object - use the joiner looking for explicit disconnectors on that MA - once you have the right one change the disconnector type back to normal disconnector.
> 
> If you want the MV entry to go, look at the object deletion rule to identify which MA's must become disconnected to delete the MV object.
> 
> Hope this helps,
> 

Hi Jon,

I should have said "automatically" -- we've been doing it manually for a while but would like to automate it [assuming the Dilbert Automation Curve doesn't apply!].

So yes -- can a systematic JOIN operation cause an already JOINed Connector to become disconnected so that the new JOIN can occur?

Ta,
foo

> -----Original Message-----
> From: Discussion for MS IDM tools liks ILM and FIM 
> [mailto:[log in to unmask]] On Behalf Of Matthew Slowe
> Sent: 22 April 2015 12:13
> To: [log in to unmask]
> Subject: How to cause a disconnect
> 
> Afternoon all,
> 
> If the MV attribute that a CS object originally JOINed based on changes then the default behaviour is for the object to stay joined. However if there is a new CS object which now matches instead, it's unable to (ambiguous-import-flow-from-multiple-connectors).
> 
> Is there a way for this new object to take precedence over the original one and force a disconnect to allow the new join to work?

--
Matthew Slowe | Server Infrastructure Officer IT Infrastructure, Information Services, University of Kent Room S21, Cornwallis South Canterbury, Kent, CT2 7NZ, UK
Tel: +44 (0)1227 824265 

www.kent.ac.uk/is | @UnikentUnseenIT | @UKCLibraryIt