Start Azure V2 VMs

This Graphical PowerShell runbook connects to Azure using an Automation Run As account and starts all V2 VMs in an Azure subscription or in a resource group or a single named V2 VM. You can attach a recurring schedule to this runbook to run it at a specific time. The asso

4.4 Star
38,075 times
Add to favorites
Windows Azure
E-mail Twitter Digg Facebook
Sign in to ask a question

  • VM Failed to start
    2 Posts | Last post November 13, 2017
    • Hi,
         the script runs correctly and the virtual machine starts. However, when I see the job log, the output is "VM failed to start". Do you kwnow why?
      Thanks in advance
    • I had this problem too. What I did was change the condition expressions for Notify VM Started and Notify Failed To Start to the following respectively. The issue was that the original condition .Status "Succeeded" is not part of the output from Start VM so it will always fail.
      $ActivityOutput['Start VM'].IsSuccessStatusCode -eq $true
      $ActivityOutput['Start VM'].IsSuccessStatusCode -ne $true
  • VM Failed to Start
    1 Posts | Last post November 09, 2017
    • We've been using this script for over a year now with great results. Over the past few months, however, I've been receiving the following error message: 
      ABC-Server failed to start. Error was:
          + CategoryInfo          : NotSpecified: (:) [Write-Error], WriteErrorException
          + FullyQualifiedErrorId : Microsoft.PowerShell.Commands.WriteErrorException
      Looks like the same error Etorrescobos describes in his question. The VM starts and stops just fine, it just logs this error. Any idea why? 
  • Parallel start
    4 Posts | Last post September 28, 2017
    • It seems it starts each VM sequentially, taking some time to finish and wasting Job Time. Could you change to Start all VMs at once?
    • Did you find a way to start them all at once?
    • it would be great if the action can happen in parallel
    • You have to create more schedeules for the same Runbook. If you create two schedeules in wihch you write different imput data (each VM name) you can run the same Runbook at the same time
  • Breaking change notice
    1 Posts | Last post March 24, 2017
    • I've been using this script for months and started receiving an error:
      Breaking change notice: In upcoming release, top level properties, DataDiskNames and NetworkInterfaceIDs, will be removed from VM object because they are also in StorageProfile and NetworkProfile, respectively.
      RunbookFlow : Resource group 'RESOURCE-GROUP' could not be found.
      ErrorCode: ResourceGroupNotFound
      ErrorMessage: Resource group 'RESOURCE-GROUP' could not be found.
      StatusCode: 404
      ReasonPhrase: Not Found
      OperationID : SOME_GUID_HERE
      At line:9 char:57
      + <#-- Enable activity tracing to see error location --#> RunbookFlow `
      +                                                         ~~~~~~~~~~~~~
          + CategoryInfo          : CloseError: (:) [Invoke-RunbookFlow], ComputeCloudException
          + FullyQualifiedErrorId : Orchestrator.GraphRunbook.Cmdlets.InvokeRunbookFlowCommand
      Odd enough, this script will run on some VM's but not on others.