Share via

MMS2013 Session Now on Channel 9 – Patching a Hyper-V Cluster with Orchestrator / Configuration Manager - Including Downloadable Runbook Exports!!!

  • Article

Good day all – if you were able to attend MMS2013 hope you had a great time, if not, no worries you are in luck. All MMS2013 sessions should now be available on Channel 9.

Check out my session ‘Complex Maintenance Using System Center 2012 Configuration Manager and Orchestrator: Patching a Cluster’ – https://channel9.msdn.com/Events/MMS/2013/UD-B341 .

During this session, I detail a sample Orchestrator / Configuration Manager Solution which is used to gracefully apply updates to a Windows Failover cluster. In this session, I demonstrate this live against a 2 node Hyper-V cluster (hosting 20 VM's, Live migration and all).

Finally if you like what you see, I have made the Runbooks available at the following location – https://gallery.technet.microsoft.com/Cluster-Patching-Runbooks-5bda907a

Enjoy – and as always, you can subscribe to my twitter feed using the button found on the upper right hand section of this page.

neilp

Comments

  • Anonymous
    January 01, 2003
    Hi..i was hope that you are checking this blog post as i am trying to get these runbooks to work so i can provide a Cluster Patching solution for our database team. However, i'm running into a road block with a couple of your Runbooks.

    First Issue - Configure Updates Runbook, the Trim Deployment ID Errors with "You cannot call a method on a null-valued expression" I think this has something to do with the $newstring variable.

    Second Issue (Maybe this has something to do with the First Issue), The Add Collection Rule fails with "Failed to add run "to collection '' "." is not a valid Resource Name. It appears as though it cannot add the Computer (Node) to the collection. The collection is created and the Update Group get deployed, but the Updates never get installed because i believe that the Node never gets added to the collection.

    Any help would be appreciated

  • Anonymous
    May 22, 2013
    Excellent presentation at MMS, and thanks for the runbooks :)

  • Anonymous
    May 08, 2015
    I would confirm that the previous task of "Get Deployment ID" is returning a result. It would make sense that if it's failing, it would pass a $null to the next task which is what that error references.

  • Anonymous
    August 27, 2015
    The user which is running the Get Deployment ID step must have opened the ConfMgr Console at least once on the target Primary site. Else you get the null value.