< Back

Get-AzureRmAutomationDscOnboardingMetaconfig

Tue Jan 29, 2019 9:32 pm

NAME Get-AzureRmAutomationDscOnboardingMetaconfig



SYNOPSIS

Creates meta-configuration .mof files.





SYNTAX

Get-AzureRmAutomationDscOnboardingMetaconfig [-ResourceGroupName] <String> [-AutomationAccountName] <String> [-ComputerName <String[]>]

[-DefaultProfile <IAzureContextContainer>] [-Force] [-OutputFolder <String>] [-Confirm] [-WhatIf] [<CommonParameters>]





DESCRIPTION

The Get-AzureRmAutomationDscOnboardingMetaconfig cmdlet creates APS Desired State Configuration (DSC) meta-configuration Managed Object Format

(MOF) files. This cmdlet creates a .mof file for each computer name that you specify. The cmdlet creates a folder for the .mof files. You can run

the Set-DscLocalConfigurationManager cmdlet for this folder to onboard these computers into an Azure Automation account as DSC nodes.





PARAMETERS

-AutomationAccountName <String>

Specifies the name of an Automation account. You can onboard the computers that the ComputerName parameter specifies to the account that this

parameter specifies.



Required? true

Position? 1

Default value None

Accept pipeline input? True (ByPropertyName)

Accept wildcard characters? false



-ComputerName <String[]>

Specifies an array of names of computers for which this cmdlet generates .mof files. If you do not specify this parameter, the cmdlet

generates an .mof file for the current computer (localhost).



Required? false

Position? named

Default value None

Accept pipeline input? True (ByPropertyName)

Accept wildcard characters? false



-DefaultProfile <IAzureContextContainer>

The credentials, account, tenant, and subscription used for communication with azure



Required? false

Position? named

Default value None

Accept pipeline input? False

Accept wildcard characters? false



-Force [<SwitchParameter>]

Forces the command to run without prompting you for confirmation, and to replace existing .mof files that have the same name.



Required? false

Position? named

Default value False

Accept pipeline input? False

Accept wildcard characters? false



-OutputFolder <String>

Specifies the name of a folder where this cmdlet stores .mof files.



Required? false

Position? named

Default value None

Accept pipeline input? True (ByPropertyName)

Accept wildcard characters? false



-ResourceGroupName <String>

Specifies the name of a resource group. This cmdlet creates .mof files to onboard computers in the resource group that this parameter

specifies.



Required? true

Position? 0

Default value None

Accept pipeline input? True (ByPropertyName)

Accept wildcard characters? false



-Confirm [<SwitchParameter>]

Prompts you for confirmation before running the cmdlet.



Required? false

Position? named

Default value False

Accept pipeline input? False

Accept wildcard characters? false



-WhatIf [<SwitchParameter>]

Shows what would happen if the cmdlet runs. The cmdlet is not run.



Required? false

Position? named

Default value False

Accept pipeline input? False

Accept wildcard characters? false



<CommonParameters>

This cmdlet supports the common parameters: Verbose, Debug,

ErrorAction, ErrorVariable, WarningAction, WarningVariable,

OutBuffer, PipelineVariable, and OutVariable. For more information, see

about_CommonParameters (http://go.microsoft.com/fwlink/?LinkID=113216).



INPUTS

None

This cmdlet does not accept any input.





OUTPUTS

Microsoft.Azure.Commands.Automation.Model.DscOnboardingMetaconfig







NOTES









Example 1: Onboard servers to Automation DSC



PS C:\\>Get-AzureRmAutomationDscOnboardingMetaconfig -ResourceGroupName "ResourceGroup03" -AutomationAccountName "Contoso17" -ComputerName

"Server01", "Server02" -OutputFolder "C:\\Users\\PattiFuller\\Desktop"

PS C:\\> Set-DscLocalConfigurationManager -Path "C:\\Users\\PattiFuller\\Desktop\\DscMetaConfigs" -ComputerName "Server01", "Server02"



The first command creates DSC meta-configuration files for two servers for the Automation account named Contoso17. The command saves these files

on a desktop.



The second command uses the Set-DscLocalConfigurationManager cmdlet to apply the meta-configuration to the specified computers to onboard them as

DSC nodes.







RELATED LINKS

Online Version: https://docs.microsoft.com/en-us/powers ... metaconfig