Hi, I need to export some parameter of Reqeust object. I use Powershell in this way: add-pssnapin FIMAutomation $objects = Export-FIMConfig -CustomConfig ("/Request[CreatedTime > '2011-11-10T08:03:00']") -Uri "http://localhost:5725/resourcemanagementservice" -OnlyBaseResources When executing powershell freeze during Export-FimConfig (see image) What is the problem in your opinion? This is strange but on two different fim 2010 server do the same thing. Thx. Regards. Luka. update: the powershell.exe always consume 50% cpu during the script execution

I find that request which give me errora are from "Built-in Synchronization Account" Now I filter this requeste which freeze powershell.

I think you'll find that if you filter out all /ma-data and /mv-data objects you'll eliminate your problem. I have found that exporting these objects can sometimes take upwards of about an hour in my lab environment ... the script isn't actually freezing, it's just taking longer than you are expecting. Note that these objects are periodically updated and appear as updates/deletes/creates in the Request history ... and these updates also occur whenever you update creds in the FIM MA, or refresh the FIM MA schema. Also, the export script will chase references for sync activity. Bob Bradley (FIMBob @ http://thefimteam.com/) ... now using Event Broker 3.0 @ http://www.fimeventbroker.com/ for just-in-time delivery of FIM 2010 policy via the sync engine

Thx a lot Bob. Best Regards. Luka

Thx a lot Bob. Best Regards. Luka

I'm having the same problem as the original poster. What do I need to add to my code - as in -- How do I filter these entries out in my Powershell script? Thanks. [EDITED} I figured it out on my own - I needed to filter on "Creator" using the Object ID for the accounts. $date = [DateTime]::UtcNow.AddHours(-12).ToString("yyyy-MM-ddTHH:mm:ss.fff") Export-FIMConfig -CustomConfig("/Request[Target = /Group and Creator != 'fb89aefa-5ea1-47f1-8890-abe7797d6497' and Creator != 'e05d1f1b-3d5e-4014-baa6-94dee7d68c89' and CreatedTime > '$date']") -OnlyBaseResources | Convert-FimExportToPSObject | Export-CSV d:\Requests.csv Ryan

I'm having the same problem as the original poster. What do I need to add to my code - as in -- How do I filter these entries out in my Powershell script? Thanks. [EDITED} I figured it out on my own - I needed to filter on "Creator" using the Object ID for the accounts. $date = [DateTime]::UtcNow.AddHours(-12).ToString("yyyy-MM-ddTHH:mm:ss.fff") Export-FIMConfig -CustomConfig("/Request[Target = /Group and Creator != 'fb89aefa-5ea1-47f1-8890-abe7797d6497' and Creator != 'e05d1f1b-3d5e-4014-baa6-94dee7d68c89' and CreatedTime > '$date']") -OnlyBaseResources | Convert-FimExportToPSObject | Export-CSV d:\Requests.csv Ryan

I do this using the -customConfig option, e.g. as follows: $policy = Export-FIMConfig -customConfig "/Function","/SynchronizationFilter","/SynchronizationRule[not(starts-with(DisplayName,'AAA'))]",` "/SearchScopeConfiguration[not(starts-with(DisplayName,'AAA'))]","/HomepageConfiguration","/ObjectVisualizationConfiguration","/NavigationBarConfiguration[not(starts-with(DisplayName,'AAA'))]",` "/PortalUIConfiguration","/ConstantSpecifier","/EmailTemplate","/FilterScope",` "/ActivityInformationConfiguration",` "/Set[not(starts-with(DisplayName,'AAA')) and not(DisplayName='Lockout gate registration resources') and not(DisplayName='Administrators')]",` "/WorkflowDefinition[not(starts-with(DisplayName,'AAA'))]",` "/ManagementPolicyRule[not(starts-with(DisplayName,'AAA'))] "` -MessageSize 9999999 -AllLocales In other words I specify exactly which object types I want to export. Note that I have also used the "not(starts-with(DisplayName,'AAA'))" filter throughout the above ... this is my own convention so that I know to write "temporary" policy objects with an AAA prefix to avoid them ever being migrated by my scripts. Bob Bradley (FIMBob @ TheFIMTeam.com) ... now using Event Broker 3.0 for just-in-time delivery of FIM 2010 policy via the sync engine, and continuous compliance for FIM

I do this using the -customConfig option, e.g. as follows: $policy = Export-FIMConfig -customConfig "/Function","/SynchronizationFilter","/SynchronizationRule[not(starts-with(DisplayName,'AAA'))]",` "/SearchScopeConfiguration[not(starts-with(DisplayName,'AAA'))]","/HomepageConfiguration","/ObjectVisualizationConfiguration","/NavigationBarConfiguration[not(starts-with(DisplayName,'AAA'))]",` "/PortalUIConfiguration","/ConstantSpecifier","/EmailTemplate","/FilterScope",` "/ActivityInformationConfiguration",` "/Set[not(starts-with(DisplayName,'AAA')) and not(DisplayName='Lockout gate registration resources') and not(DisplayName='Administrators')]",` "/WorkflowDefinition[not(starts-with(DisplayName,'AAA'))]",` "/ManagementPolicyRule[not(starts-with(DisplayName,'AAA'))] "` -MessageSize 9999999 -AllLocales In other words I specify exactly which object types I want to export. Note that I have also used the "not(starts-with(DisplayName,'AAA'))" filter throughout the above ... this is my own convention so that I know to write "temporary" policy objects with an AAA prefix to avoid them ever being migrated by my scripts. Bob Bradley (FIMBob @ TheFIMTeam.com) ... now using Event Broker 3.0 for just-in-time delivery of FIM 2010 policy via the sync engine, and continuous compliance for FIM