Provisioning AD Groups - DN not set...
I am working on provision AD groups via the FIM portal. My issue is with the outbound sync rules. If I statically set the initial value of the dn to "CN=TestGroup,OU=Groups,OU=FIM Object,DC=lab,DC=loc" everything works fine. When I change it to be "CN="+<accountName>+",OU=Groups,OU=FIM Objects,DC=lab,DC=loc" I get the following error in the sync service:Microsoft.MetadirectoryServices.ProvisioningBySyncRuleException: The DN must be set before calling CSEntry.CommitNewConnector.I have tried accountName and also DisplayName and both give the same result, even though both are populated on the group in the portal. I have the "initial value" checkbox checked. This is FIM RC1 with the latest updates.Any thoughts?
December 23rd, 2009 1:10am

I resolved this. I was not flowing the accountName or displayName from the portal to the metaverse, so the metaverse had no value to use. Makes sense now, but was baffling me before...
Free Windows Admin Tool Kit Click here and download it now
December 23rd, 2009 1:30am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics