Deployment agents that rely on shadow accounts do not work with Release Management Server for Visual Studio 2013
Assume that you have three deployment agents. These deployment agents rely on the following shadow accounts:
Server1/LocalAccount1 Server2/LocalAccount1 Server3/LocalAccount1
In this scenario, you cannot configure the deployment agents in Microsoft Release Management Server for Visual Studio 2013.
This issue occurs because the deployment agents cannot be configured if they rely on shadow accounts.
To resolve this issue, add the Service User accounts in Release Management. To do this, follow these steps:
Create a Service User account for each deployment agent in Release Management. For example, create the following: Server1\ LocalAccount1 Server2\ LocalAccount1 Server3\ LocalAccount1 Create an account in Release Management, and then assign to that account the Service User and Release Manager user rights. For example, create Release_Management_server\ LocalAccount1. Run the deployment agent configuration on each deployment computer. Note
This is a "FAST PUBLISH" article created directly from within the Microsoft support organization. The information contained herein is provided as-is in response to emerging issues. As a result of the speed in making it available, the materials may include typographical errors and may be revised at any time without notice. See
for other considerations.
Article ID: 2905742 - Last Review: 11/13/2013 14:18:00 - Revision: 1.0
Release Management Client for Visual Studio 2013, Release Management for Visual Studio 2013, Release Management Server for Team Foundation Server 2013
Keywords: kbprb kbtshoot kbsurveynew KB2905742