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.   Prerequis...

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.   Prerequisite...

  Release Management for Visual Studio 2013 (RM) is tightly integrated with TFS. In order to communicate with TFS, RM uses a service account to access different functionality of TFS. Here are the necessary minimal permissions that the account must have. If possible, to keep things simple, we recommend an account that is part o...

  Enable logs on Microsoft Deployment Agent: The first and most easy way to debug why an action/component is failing is to open the logs available through the deployment step of your release within Release Management (RM) client. To do this, open your release, access the View Log section, click on the Details button of the deployment...

There are times when you will want Release Management (RM) to interact with machines that are not part of the same domain. This post details the steps required to configure RM to work across untrusted domains.  Configuring the Microsoft Deployment Agent  Follow these steps to configure the Release Management Server and the Deployment...