Synchronization Service debugging options
Yesterday I was having issues with flowing the member attribute for a group from the MV to AD. The groups are managed by the portal (dynamic groups) and the attribute flow's are done through declarative
What I was seeing was the MV member attribute contained 4 users which the AD member attribute did not hold. When doing a preview full synchronization on the FIM CS object, or the AD CS object, twice I saw the Outbound SR displayed as "not applied" and hence
my outbound member flow as "not applied".
And there I was. It says not applied. Euhm why? So I'm wondering: are there any debugging options to see why it's not applied?
In fact I have two groups in the Portal which are synced towards AD. Both are dynamic. While the other one kept on behaving as it should, the second one just stopped applying the SR.
I ended up doing some manualy disconnect in MV/recreate in FIM/join in MV stuff to get the member attribute syncing again... Clearing the AD CS had no effect. But I really don't like this way of fixing. It's a bit blunt, and I have no idea why it worked.
Regards,
Thomashttp://setspn.blogspot.com
November 6th, 2010 7:16am
Thomas, I’m afraid, there are not that many options you have right now to troubleshoot issues like this.
Typically, this error is a result of a configuration mistake – at least the most common reason for running into it is.
The “80%”case is related to a problem with the DN.
Reviewing your configuration, using preview and also examining the tower are the best things you can do – last but not least, contact PSS.
We are aware of a need to improve the overall troubleshooting experience and adding new features in conjunction with it is work in progress.
Cheers,
Markus
Markus Vilcinskas, Knowledge Engineer, Microsoft Corporation
Free Windows Admin Tool Kit Click here and download it now
November 8th, 2010 12:49pm
Thomas, I’m afraid, there are not that many options you have right now to troubleshoot issues like this.
Typically, this error is a result of a configuration mistake – at least the most common reason for running into it is.
The “80%”case is related to a problem with the DN.
Reviewing your configuration, using preview and also examining the tower are the best things you can do – last but not least, contact PSS.
We are aware of a need to improve the overall troubleshooting experience and adding new features in conjunction with it is work in progress.
Cheers,
Markus
Markus Vilcinskas, Knowledge Engineer, Microsoft Corporation
November 8th, 2010 12:49pm
Markus,
Thanks for the tips. Regarding to "examining the tower", what do you mean with this? How do I do this? Preview I know, and that's an amazing help to troubleshoot this stuff.
Regards,
Thomashttp://setspn.blogspot.com
Free Windows Admin Tool Kit Click here and download it now
November 8th, 2010 3:13pm
Markus,
Thanks for the tips. Regarding to "examining the tower", what do you mean with this? How do I do this? Preview I know, and that's an amazing help to troubleshoot this stuff.
Regards,
Thomashttp://setspn.blogspot.com
November 8th, 2010 3:13pm
Clearing the AD CS had no effect. quad band cell phone But I really don't like this way of fixing. It's a bit blunt, and I have no idea why it worked.http://chncellphone.com
Free Windows Admin Tool Kit Click here and download it now
November 9th, 2010 1:42am
Clearing the AD CS had no effect. quad band cell phone But I really don't like this way of fixing. It's a bit blunt, and I have no idea why it worked.http://chncellphone.com
November 9th, 2010 1:42am
I will write an article on this - stay tuned...
Cheers,
MarkusMarkus Vilcinskas, Knowledge Engineer, Microsoft Corporation
Free Windows Admin Tool Kit Click here and download it now
November 10th, 2010 4:08am