Update Rollup 5 for System Center Orchestrator 2012 SP1 is now available

Update Rollup 5 for System Center Orchestrator 2012 SP1 is now available

  • Comments 3
  • Likes

download432Update Rollup 5 for System Center Orchestrator 2012 Service Pack 1 is now available. This update includes the following:

Issue 1: The Monitor Service activity does not let the configuration be saved if Monitor Service cannot resolve the hostname that is entered in the Computer Input property. If you try to save the configuration, you receive the following error message:

Connection to the selected computer has failed

Issue 2: The Compress Files activity does not include files that are in subfolders that match the filter when the Include files in sub-folders option is selected.

Issue 3: The Send SNMP Trap activity does not send the correct results for certain combinations of values.

Issue 4: The SNMP Trap Variables are not retained in the correct order after the Properties dialog box is closed and then opened again. 

For additional details and download instructions please see the following:

KB2904725 - Description of the fixes in Update Rollup 5 for System Center Orchestrator 2012 SP1 (http://support.microsoft.com/kb/2904725)

J.C. Hornbeck | Solution Asset PM | Microsoft GBS Management and Security Division

Get the latest System Center news on Facebook and Twitter:

clip_image001 clip_image002

System Center All Up: http://blogs.technet.com/b/systemcenter/
System Center – Configuration Manager Support Team blog: http://blogs.technet.com/configurationmgr/
System Center – Data Protection Manager Team blog: http://blogs.technet.com/dpm/
System Center – Orchestrator Support Team blog: http://blogs.technet.com/b/orchestrator/
System Center – Operations Manager Team blog: http://blogs.technet.com/momteam/
System Center – Service Manager Team blog: http://blogs.technet.com/b/servicemanager
System Center – Virtual Machine Manager Team blog: http://blogs.technet.com/scvmm

Windows Intune: http://blogs.technet.com/b/windowsintune/
WSUS Support Team blog: http://blogs.technet.com/sus/
The AD RMS blog: http://blogs.technet.com/b/rmssupp/

App-V Team blog: http://blogs.technet.com/appv/
MED-V Team blog: http://blogs.technet.com/medv/
Server App-V Team blog: http://blogs.technet.com/b/serverappv

The Forefront Endpoint Protection blog : http://blogs.technet.com/b/clientsecurity/
The Forefront Identity Manager blog : http://blogs.msdn.com/b/ms-identity-support/
The Forefront TMG blog: http://blogs.technet.com/b/isablog/
The Forefront UAG blog: http://blogs.technet.com/b/edgeaccessblog/

Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment
  • Hi, Thanks for all the informative blog entries.. Makes our lives easier :)
    just wanted to ask more on this one.. we have seen multiple instance of this update breaking our Runbooks with Error - Failed to CoCreate IOpalisServerExtension . Only solution found on Technet is to reinstall the Runbook Server. We would be grateful to know if you have seen this and if you know more about this issue ..

    Regards
    Ravindran

  • Hi Thanks for all the informative blog entries.. Makes our lives easier :)
    just wanted to ask more on this one.. we have seen multiple instance of this update breaking our Runbooks with Error - Failed to CoCreate IOpalisServerExtension . Only solution found on Technet is to reinstall the Runbook Server. We would be grateful to know if you have seen this and if you know more about this issue ..

    Regards
    Ravindran

  • I had to uninstall the Update as every 1 or 2 days I had to reinstall the RunbookServer cauing too much pain.. As soon as I removed the update, everything is back to normal.