tag:blogger.com,1999:blog-4684874465987951601.post4545283731840991294..comments2024-03-27T23:30:46.579-07:00Comments on Chaminda's DevOps Journey with MSFT: Deploying to an Untrusted Domain–TFS 2015 Release Management ServiceChaminda Chandrasekarahttp://www.blogger.com/profile/10785099125374685765noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-4684874465987951601.post-9695940246757196502016-09-13T20:29:56.431-07:002016-09-13T20:29:56.431-07:00Hi Sorry for delayed reply... Make sure too add th...Hi Sorry for delayed reply... Make sure too add the shadowuser to administrators group and then reconfigure the agent. This should take the agent to green.Chaminda Chandrasekarahttps://www.blogger.com/profile/10785099125374685765noreply@blogger.comtag:blogger.com,1999:blog-4684874465987951601.post-59508851665562078272016-08-17T10:52:02.475-07:002016-08-17T10:52:02.475-07:00Thanks for posting this. I was perplexed at how th...Thanks for posting this. I was perplexed at how the web-based Release Management was going to work until it clicked that the Build and Deployment agent functionality has been unified.<br /><br />The agent I tried to install on my workstation connected as expected after following the posted steps, but the agent marked "red" instead of "green" in the TFS Agent pool. <br /><br />The local agent logs show the following message " System.Net.Sockets.SocketException: A connection attempt failed ... " which I suspect may be related to accessing the TFS instance over a DirectAccess VPN. Cronje van Heerdenhttps://www.blogger.com/profile/01036721930456476057noreply@blogger.com