{"id":963,"date":"2014-07-07T03:27:00","date_gmt":"2014-07-07T03:27:00","guid":{"rendered":"https:\/\/blogs.msdn.microsoft.com\/visualstudioalm\/2014\/07\/07\/how-to-deploy-to-standard-or-azure-environments-in-release-management-2013-with-update-3-rc\/"},"modified":"2022-07-13T06:47:21","modified_gmt":"2022-07-13T14:47:21","slug":"how-to-deploy-to-standard-or-azure-environments-in-release-management-2013-with-update-3-rc","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/devops\/how-to-deploy-to-standard-or-azure-environments-in-release-management-2013-with-update-3-rc\/","title":{"rendered":"How to deploy to Standard or Azure environments in Release Management 2013 with Update 3 RC"},"content":{"rendered":"


<\/span><\/span><\/p>\n

With Microsoft Release Management 2013 Update 3 RC, you can now use Windows PowerShell or Windows PowerShell Desired State Configuration (DSC) for deploying and managing configuration data. We now support deploying to On-premise environment (Standard) and Azure environments without having to setup Microsoft Deployment Agent.<\/span><\/span><\/p>\n

\n \u00a0<\/span>\n<\/p>\n

\n Prerequisites <\/span>
<\/span><\/span><\/span><\/strong>\n<\/h2>\n

\n
PowerShell (PS)<\/span><\/span><\/span><\/span>\n<\/h3>\n

\n You can use PS scripts to deploy application components to Standard or Azure servers. These scripts can be same as what you might have been already using to deploy to Microsoft Deployment Agent based servers.<\/span><\/span><\/span><\/span>\n<\/p>\n

\n
RM requires the PS version on target servers to be of version 4.0 or higher. If the Target Server has PS 3.0, upgrade it to PS 4.0.<\/span><\/span><\/span><\/span>\n<\/p>\n

\n \u00a0<\/span><\/span><\/span><\/span>\n<\/p>\n

\n Desired State Configuration (DSC) <\/span> <\/p>\n

<\/span><\/span><\/span>\n<\/h3>\n

\n Microsoft supports DSC (Desired State Configuration) as a first-class experience in Windows, RM leverages Windows DSC agent for deployment and configuration. <\/span><\/span><\/span><\/span>\n<\/p>\n

\n
DSC ships in the box with Windows 8.1 & Windows Server 2012 R2. DSC is also part of <\/span><\/span><\/span><\/span>Windows Management Framework<\/span><\/a><\/span><\/span><\/span> 4.0<\/span><\/a><\/span> which ships as an optional update and can be installed to Windows Server 2012, Windows Server 2008R2, Windows 7 and Windows 8.<\/span>
<\/span><\/span><\/span>\n<\/p>\n

\n \u00a0\n<\/p>\n

\n
Refer following links to get started with DSC scripts<\/span><\/span><\/span>\n<\/p>\n

\n \u00b7<\/span><\/span>\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 <\/span><\/span><\/span><\/span><\/span>High level concepts<\/span><\/a><\/span><\/span><\/span><\/span><\/span>\n<\/p>\n

\n \u00b7<\/span><\/span>\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 <\/span><\/span><\/span><\/span><\/span>Basic introduction<\/span><\/a><\/span><\/span><\/span><\/span><\/span>\n<\/p>\n

\n \u00b7<\/span><\/span>\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 <\/span><\/span><\/span><\/span><\/span>Documentation Homepage<\/span><\/a><\/span><\/span><\/span><\/span><\/span>\n<\/p>\n

\n \u00a0<\/span><\/span><\/span>\n<\/p>\n

\n 1. Managing Releases in Standard Environments using PS\/DSC<\/span><\/span><\/strong> <\/p>\n

<\/span><\/span><\/span><\/span>\n<\/h3>\n

\n Follow steps mentions in the blog to setup your on-premise environments as \u2018Standard Environment\u2019 in RM
<\/span><\/span><\/span>\n<\/h3>\n
\n<\/blockquote>\n

\n> How to setup environments for Agent-less deployments in Release Management 2013 with Update 3 RC<\/a><\/em><\/span><\/span><\/span><\/span>\n> <\/h4>\n

\n \u00a0<\/span><\/span><\/span>\n<\/h2>\n

\n Authoring deployments in Standard environment using PS\/DSC <\/p>\n

<\/em><\/span><\/span><\/span><\/strong>\n<\/h4>\n

\n Create a vNext Release Path to represent the stages that your release must go through. Choose the environment and approvers to use for each stage of your release.
<\/span><\/span><\/span>\n<\/p>\n

\n
\"clip_image002[6]\"<\/a> <\/p>\n

<\/span>\n<\/p>\n

\n \u00a0<\/span><\/span><\/span>\n<\/p>\n

\n Create a new vNext Component and specify how the component gets the files used during the deployment using one of the 3 options.
<\/span><\/span><\/span>\n<\/p>\n

\n
\"clip_image004[6]\"<\/a> <\/p>\n

<\/span>\n<\/p>\n

\n \u00a0<\/span><\/span><\/span>\n<\/p>\n

\n Create a Release Definition and use the vNext Release path that you have just added. <\/p>\n

<\/span><\/span><\/span>\n<\/p>\n

\n \"clip_image006[6]\"<\/a> <\/p>\n

<\/span>\n<\/p>\n

\n \u00a0<\/span><\/span><\/span>\n<\/p>\n

\n Add the vNext component that you have created to the Release Definition. <\/p>\n

<\/span><\/span><\/span>\n<\/p>\n

\n \"clip_image008[6]\"<\/a> <\/p>\n

<\/span>\n<\/p>\n

\n \u00a0<\/span><\/span><\/span>\n<\/p>\n

\n Define the deployment sequence for each of the stages you have defined in the vNext Release Path. <\/p>\n

<\/span><\/span><\/span>\n<\/p>\n

\n QA Stage:<\/span><\/span><\/span>\n<\/p>\n

\n \"clip_image010[6]\"<\/a> <\/p>\n

<\/span>\n<\/p>\n

\n \u00a0<\/span><\/span><\/span>\n<\/p>\n

\n Production Stage:<\/span><\/span><\/span>\n<\/p>\n

\n \"clip_image012[6]\"<\/a> <\/p>\n

<\/span>\n<\/p>\n

\n For each of the \u201cDeploy to Standard Environment\u201d action, provide the values to the configuration variables. <\/p>\n

<\/span><\/span><\/span>\n<\/p>\n

\n Details of each of the parameters passed<\/span><\/span><\/strong>: <\/p>\n

<\/span><\/span><\/span><\/span>\n<\/p>\n

\n
ServerName:<\/span><\/span><\/em><\/strong> This is the name of Standard Server i.e the on-premise machine where you want to deploy the application.<\/span><\/span><\/span><\/span>\n<\/p>\n

\n
UserName\/Password:<\/span><\/span><\/em><\/strong>\u00a0 <\/span>This is the Account and Password to connect to target Standard Server. This user needs to be a domain user and also member of local Administrator group on Standard Server.<\/span><\/span><\/span><\/span>\n<\/p>\n

\n
ScriptPath\/ConfigurationPath<\/span><\/span><\/em><\/strong>: The relative path for PS\/DSC Deploy and Configuration scripts with respect to the package path.<\/span><\/span><\/span><\/span>\n<\/p>\n

\n This script will install the component . It can be a native PowerShell script or a DSC script. If DSC, it should contain a \u201cDSC configuration\u201d and a command to create mof for that DSC configuration. <\/p>\n

Example:<\/span><\/span><\/span><\/span>\u00a0<\/span><\/span><\/span>\n<\/p>\n

\n
 <\/pre>\n
\n
\n
\n
\n
\n
\n
\n
configuration FileCopy{ <\/pre>\n
                <\/p>\n
    Node $AllNodes.NodeName<\/pre>\n
                <\/p>\n
     {<\/pre>\n
                <\/p>\n
         File CopyDeploymentBits<\/pre>\n
         {<\/pre>\n
                <\/p>\n
            Ensure = \"Present\"<\/pre>\n
                <\/p>\n
            Type = \"Directory\"<\/pre>\n
                <\/p>\n
            Recurse = $true<\/pre>\n
                <\/p>\n
            SourcePath = $applicationPath<\/pre>\n
                <\/p>\n
            DestinationPath = $Node.DeploymentPath<\/pre>\n
                <\/p>\n
         }<\/pre>\n
                <\/p>\n
     } <\/pre>\n
                <\/p>\n
} <\/pre>\n
                <\/p>\n
 <\/pre>\n
                <\/p>\n
FileCopy -ConfigurationData $ConfigData –Verbose<\/pre>\n<\/p><\/div>\n<\/p><\/div>\n<\/blockquote><\/div>\n<\/p><\/div>\n<\/p><\/div>\n<\/p><\/div>\n<\/div>\n
\n   
FileCopy<\/em> DSC configuration script with a command to generate *.mof at the end<\/span><\/span><\/span><\/span>\n<\/p>\n
\n  Note:<\/span><\/span><\/span>\n<\/p>\n