Hello, I don't know if someone has already asked this question before, but is there a way, whatever way it is, to bulk modify users in the FIM portal. That is select multiple users and change an attribute for them. For example select 5 users and change their department attribute to the same value. Also is there a way to copy a user like the way we do in Active Directory? Regards,MM

At the moment your best best is powershell.http://www.wapshere.com/missmiis

Hi Marie-Ange, I don't think that the portal gives you that possibility, but you might use a PowerShell script to do that. As an example, here's a script that sets the "Department" attribute of all users to "IT": $URI = "http://localhost:5725/ResourceManagementService" # load FIM snapin, ignore errors if already loaded Add-PSSnapin FIMAutomation -ErrorAction SilentlyContinue # get all users $objects = Export-FIMConfig -uri $URI -CustomConfig "/Person" -OnlyBaseResources # gets the value of a single-valued attribute from an exported object function GetAttributeValue($exportObject,[string] $name) { $attribute = $exportObject.ResourceManagementObject.ResourceManagementAttributes | Where-Object {$_.AttributeName -eq $name} if ($attribute -ne $null -and $attribute.Value) { $attribute.Value } } foreach ($object in $objects) { $objectID = GetAttributeValue $object "ObjectID" $displayName = GetAttributeValue $object "DisplayName" $objectType = GetAttributeValue $object "ObjectType" $attributeValue = GetAttributeValue $object $attributeName Write-Host "Setting department for '$displayName'" $importChange = New-Object Microsoft.ResourceManagement.Automation.ObjectModel.ImportChange $importChange.Operation = 1 $importChange.AttributeName = "Department" $importChange.AttributeValue = "IT" $importChange.FullyResolved = 1 $importChange.Locale = "Invariant" $importObject = New-Object Microsoft.ResourceManagement.Automation.ObjectModel.ImportObject $importObject.ObjectType = $objectType $importObject.TargetObjectIdentifier = $objectID $importObject.SourceObjectIdentifier = $objectID $importObject.State = 1 $importObject.Changes = (,$importChange) $importObject | Import-FIMConfig -uri $URI -ErrorVariable Err -ErrorAction SilentlyContinue if ($Err) {Throw $Err} } Paolo Tedesco - http://cern.ch/idm

You would actually achieve far better performance by using Run On Policy Update (ROPU) - I'll be talking about this in one of my TEC presentations: Create a Set (calculated or manual) of the objects you wish to affect Create an Action Workflow that makes the changes you wish to execute, enable "Run On Policy Update" a.k.a "Run Mapping" by the PG Create a Transition-In policy using your Set and executing your new WF As soon as you click Submit on the policy, it will trigger the WF to execute against all members of the set and it will use all of the system resources to do it. ROPU is massively multi-threaded and will span all of your FIM Service instances. For 5 users this may not be worth it, but when updating thousands of objects it is your best bet to scale the operation.Brad Turner, ILM MVP - Ensynch, Inc - www.identitychaos.com

Paolo, wouldn't that be a perfect example for "Using PowerShell to bulk update users in the FIM portal"? :-) Cheers,MarkusMarkus Vilcinskas, Knowledge Engineer, Microsoft Corporation

Hi Markus, thanks for the hint! I generalized the script a little and posted it here. Cheers, PaoloPaolo Tedesco - http://cern.ch/idm

Perfect, Paolo, thank you! I have added your script to the ScriptBox catalog page. Cheers,MarkusMarkus Vilcinskas, Knowledge Engineer, Microsoft Corporation

Thanks paolo,this might help although the requirement for our customer was to daily perform bulk update tasks for any set of user from the portal and these updates might be done by the HR department to update a set of users.As I understood from all answers there is no such capability in the portal even with custom development.The powershell script, though, is really helpful for us as IT.Regards MM

Brad and others, While I'm sure the powershell script would work and be fine for onesies and twosies...what Brad has proposed worked fabulously for me. I needed to change the Domain attribute of 383 users and his instructions worked well as a starting point. I would say Step 2 needs more flushing out for those of use that aren't programmers by nature. I finally figured out that I had to target the domain attrib with my string for the domain name i wanted in the function evaluator activity. Once I completed all the steps, and created the MPR, 383 people without a domain attribute suddenly started having them. Vwalah. good one Brad!