Sunday, October 11, 2015

PowerShell Management Agent 5.5 refreshed

I'm happy to announce that I have released a refresh of the popular PowerShell Management Agent for FIM2010R2 (and yes, MIM2016).

This version is a code-refresh with a few bug fixes and a few additional minor features and I'll try to list them below -

  1. The setup program is gone and has been replaced by a PowerShell script. This should allow you to better control updates. The steps performed by this installation script are exactly the same as the old setup program did
  2. The entire logging feature has been replace by tracing. This means that you can now use DebugView from SysInternals / Microsoft or similar to view actions from this MA. The old logging mechanism is no longer included and has been removed from the MA. The information logged by the MA has also been reviewed and extended to allow better debugging.
  3. All errors from the PSMA are now logged to the event log. This does, however, require that you create an explict event log source. You can see in the Installation documentation how to create this.
  4. A parameter called 'ExportType' is now available to your export scripts. This allows you to determine in the Export script, whether it is a normal (Delta) or a Full Export that is being performed.
  5. A potential, however unlikely, looping condition in the import function has been fixed and also better memory handling / cleanup has been introduced.
  6. General optimization of the code has been done.

This version should be directly compatible with the 5.5.0.1425 build that has been out for more than a year. To upgrade, you should be able to download and just replace the DLL in the Extensions folder of your FIM Synchronization Service installation.

As always, I'm very thrilled that this MA is so popular and I want to keep it as current as possible, so please send me information on any bugs that you may find. However, I ask you kindly to not expect free support. For support questions, please use the FIM2010 forum on TechNet where I know that a lot of experts are ready to help and, yes, I do answer questions there whenever time allows.

Thank you for your continued support.


at

2 comments:

  1. Trond NystuenTuesday, October 20, 2015 8:27:00 PM

    I tried to install this, but got the message that the extension could not be loaded when creating the MA.

    Event log message:

    "System.IO.FileLoadException: Could not load file or assembly 'Microsoft.MetadirectoryServicesEx, Version=4.1.3.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)
    File name: 'Microsoft.MetadirectoryServicesEx, Version=4.1.3.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'
    at System.Reflection.RuntimeAssembly.GetExportedTypes(RuntimeAssembly assembly, ObjectHandleOnStack retTypes)
    at System.Reflection.RuntimeAssembly.GetExportedTypes()

    WRN: Assembly binding logging is turned OFF.
    To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
    Note: There is some performance penalty associated with assembly bind failure logging.
    To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].
    Forefront Identity Manager 4.1.3419.0"

    Got it working by replacing the dll with the 5.5.0.1425 version.

    Keep up the good work!

    ReplyDelete
  2. Søren GranfeldtTuesday, October 20, 2015 8:43:00 PM

    I've have already replaced this at a few sites, so I must be something specific to your system. Make sure it is not blocked and it is at least build 4.1.3508 hotfix level of your FIM2010 R2 installation to run this.

    ReplyDelete