Running the following PS extract: $policy = Export-FIMConfig -policyConfig -portalConfig -MessageSize 9999999 -URI $URI -customconfig "/SearchScopeConfiguration[starts-with(UsageKeyword, '%super')]" onlyBaseResources ...which results in the following error: Export-FIMConfig : Failure on making enumeration web service call. Filter = /SearchScopeConfiguration[starts-with(UsageKeyword, '%super')] Error= System.ArgumentException: An item with the same key has already been added. at System.ThrowHelper.ThrowArgumentException(ExceptionResource resource) at System.Collections.Generic.Dictionary`2.Insert(TKey key, TValue value, Boolean add) at System.Collections.Generic.Dictionary`2.Add(TKey key, TValue value) at Microsoft.ResourceManagement.Automation.ExportConfig.EndProcessing() At G:\FIMTasks\ExportPolicy-Filtered.ps1:26 char:31 + $policy = Export-FIMConfig <<<< -policyConfig -portalConfig -MessageSize 9999999 -URI $URI -customconfig "$Filter" –onlyBaseResources + CategoryInfo : InvalidOperation: (:) [Export-FIMConfig], InvalidOperationException + FullyQualifiedErrorId : ExportConfig,Microsoft.ResourceManagement.Automation.ExportConfig This is due to the duplicate Resource Type binding to the search scope resource type. Is it safe to rename one of the bindings? All references to it should be to the attribute name and not the binding itself...Brad Turner, ILM MVP - Ensynch, Inc - www.identitychaos.com [If a post helps to resolve your issue, please click the "Mark as Answer" or "Helpful" button at the top of that post. By marking a post as Answered or Helpful, you help others find the answer faster.]

Hey Brad, I would first ask, why do you need duplicate bindng ?Live ID product planning

It is like that by default.Brad Turner, ILM MVP - Ensynch, Inc - www.identitychaos.com [If a post helps to resolve your issue, please click the "Mark as Answer" or "Helpful" button at the top of that post. By marking a post as Answered or Helpful, you help others find the answer faster.]