PLC/vPLC>> -deprecated--start-all-azure-vms--arm-and-asm--in-a-subscription>> 返回
项目作者： azureautomation

项目描述 ：
This runbook connects to Azure and starts all VMs (ASM and ARM) in the specified Azure subscription. You can attach a schedule to this runbook to run it at a specific time. A pretty simple runbook to start with Azure Automation.
高级语言： PowerShell
项目地址: git://github.com/azureautomation/-deprecated--start-all-azure-vms--arm-and-asm--in-a-subscription.git


(Deprecated) Start all Azure VMs (ARM and ASM) in a subscription

Updated at 30/11/2016 : This runbook is deprecated. You should use the new authentication method in Azure Automation by using this runbook for classic (ASM) VMs or this runbook for (ARM) VMs.

See more about the new authentication method in Azure Automation

This runbook connects to Azure and starts all VMs (ASM and ARM) in the specified Azure subscription. You can attach a schedule to this runbook to run it at a specific time.

Requirements

  1. An Automation variable asset called ‘AzureSubscriptionId’ that contains the GUID for this Azure subscription. To use an asset with a different name you can pass the asset name as a runbook input parameter or change the default value for the input
    parameter.
  1. An Automation credential asset called ‘AzureCred’ that contains the Azure AD user credential with authorization for this subscription. To use an asset with a different name you can pass the asset name as a runbook input parameter or change the default
    value for the input parameter.
  1. Version 1.0.3 or higher of all Azure modules in your Azure Automation account. This runbook uses the Get-AzureRmResourceGroup cmdlet available in the version 1.0.3 of AzureRM.Resources module.

Runbook content

TechNet gallery is retiring! This script was migrated from TechNet script center to GitHub by Microsoft Azure Automation product group. All the Script Center fields like Rating, RatingCount and DownloadCount have been carried over to Github as-is for the migrated scripts only. Note : The Script Center fields will not be applicable for the new repositories created in Github & hence those fields will not show up for new Github repositories.