The PowerShell Management Agent is very flexible allowing you to define your own schema (using a PowerShell script) and run scripts for Full Imports and Exports. The download includes complete documentation, so I won't write more information in this blog entry.
Please note that I'm not able to offer free support for this, however, you can sign up for official support for this Management Agent if you do so wish. Please contact me for more details on a support agreement.
Looks good! Simple but effective!
ReplyDeleteImportant to know is that the FIM Synchronization Service account is the account used to execute the scripts. The account must be entitled to reading the script file location and to execute powershell scripts.
Another thing: if the MA is unable to read the schema file, it displays:
"Unable to retreive schema. Error: An anchor attribute defined by the extension must not be of type Reference or Boolean. A multivalued attribute defined by the extension must not be of type Boolean."
This might be confusing for users not knowing that file simply can't be found or can't be read by the service account. You might want to add a check for that.
Best regards,
Pieter de Loos
Just must be on at least Rollup 2 and have .NET Framework 4.0 installed to use this MA. It should say so in the documentation.
ReplyDeleteAlso, all scripts are run as the FIM Synchronization service account and that account therefore must be able to run PowerShell scripts and read the scripts, incl. the one for the schema.
Hi,
ReplyDeleteI still get the "Unable to retreive schema. Error: An anchor attribute defined by the extension must not be of type Reference or Boolean. A multivalued attribute defined by the extension must not be of type Boolean." error even though dot net 4 and 4.5 is installed on the machine. I've checked the permissions and my FIMSynchService account is able to run the scripts. Anything else I can check?
Please refer to this page http://blog.goverco.com/p/psmatroubleshooting.html for common issue. Also, for normal support, please use the FIM2010 forum which I visit from time to time. I sadly don't have time to do free support with the more than 500+ installations of this worldwide.
ReplyDeleteFor your particular case, please verify that you dont have spaces in the path to the PS scripts, which is not supported currently.
I was able to work around this error by running the command "Set-ExecutionPolicy -Bypass". The -Bypass parameter is not well documented, and if you use -Unrestricted, it will allow the script to run only after you acknowledge a warning prompt, which the MA creation wizard cannot do.
ReplyDelete