title: TeamCity Agent has "lost" its environment path
body: <p>I've been happily working with a TeamCity Build server for a while now, but all of a sudden things went wrong...</p>
  
  <p>It seems the build agent no longer has anything in it's <code>path</code>. So, for example, if my build script (I use NANT) calls xcopy to copy files, this has suddenly started failing because xcopy can not be found - so the build will fail unless I change it to <code>c:\windows\system32\xcopy</code>. </p>
  
  <p>I can manually browse to the build agent folder and run the nant script from there, and it all works (because the path is set correctly).</p>
  
  <p>I've not upgraded TeamCity, so I'm baffled as to why this could have borked. I don't override anything in the environment parameters of the builds in TeamCity. I've not changed anything in  the build settings either. The <em>only</em> thing I've done to this PC that contains the build agent is to install the RC of Visual Studio 2012.</p>
  
  <p>Any ideas?</p>
  
  <p><em>EDIT</em></p>
  
  <p>Further investigation - I've found the agent settings in TeamCity - in there the environment variable called "path" is just set to  <code>C:\Program Files (x86)\Nmap</code> (Recently installed). This is odd and quite possibly the cause of the issue. I just need to work out how to make TeamCity revert to the "real" path.</p>