0

My build agents are not starting after I change the properties credentials to the domain account from the network service. I done this because the network service account cannot write to my drop folder.

Each time I add the network service to the drop folder share, it appears then disappears. http://msdn.microsoft.com/en-us/library/bb778394.aspx I followed this but some steps are different, i have xp and it doesn't show the share tab so i go through security tab

So I guess I'm asking two questions here;

  1. Agents are not starting after changing credentials.
  2. Network service not able to write to the drop folder.

Thanks in advance

ELSheepO
  • 305
  • 3
  • 9
  • 26

1 Answers1

1

Yes, Network Service won't have permissions to write to a drop location. That's pretty standard. You need to be using a domain account.

The TFS Build Service will need to run as a domain user so it can write to the drop location.

The domain account for the build agent will need to be in the TFS Project Collection group for build service accounts (internal to TFS). I can't remember what it's actually called but you need to be a collection administrator to update it.

The domain account will also need some login as batch/service permissions but that should be done automatically when you reconfigure the service. Do you use the TFS Admin console to reconfigure the agent or did you just set the credentials on the service? (You should use the TFS Admin console).

daughey
  • 639
  • 5
  • 10
  • I use the Admin console. I've changed the account on the application teir to a domain account, and changing the properties on the build service to domain\user the agent will not start up. If I change it to .\user and follow [this link](http://geekswithblogs.net/jehan/archive/2011/01/15/build-controller-status-unavailable-issue-in-tfs2010.aspx) the agent starts and the builds succed. Also got my network admin to create the drop folder, and everything works now. – ELSheepO Jun 28 '12 at 08:51