Downloads of v 12.0.21005.20160105:


Last Update:

06 Jan 2016

Package Maintainer(s):

Software Author(s):

  • Microsoft


admin visualstudio2013testagents Workwave-Engineering-Services test mstest Works-With-Remoting Works-Under-SYSTEM

Agents for Visual Studio 2013

  • 1
  • 2
  • 3

12.0.21005.20160105 | Updated: 06 Jan 2016



Downloads of v 12.0.21005.20160105:



Software Author(s):

  • Microsoft

  • 1
  • 2
  • 3
Agents for Visual Studio 2013 12.0.21005.20160105

  • 1
  • 2
  • 3

Some Checks Have Failed or Are Not Yet Complete

Not All Tests Have Passed

Validation Testing Passed

Verification Testing Failed


Scan Testing Successful:

No detections found in any package files


To install Agents for Visual Studio 2013, run the following command from the command line or from PowerShell:


To upgrade Agents for Visual Studio 2013, run the following command from the command line or from PowerShell:


To uninstall Agents for Visual Studio 2013, run the following command from the command line or from PowerShell:


NOTE: This applies to both open source and commercial editions of Chocolatey.

1. Ensure you are set for organizational deployment

Please see the organizational deployment guide

  • Open Source or Commercial:
    • Proxy Repository - Create a proxy nuget repository on Nexus, Artifactory Pro, or a proxy Chocolatey repository on ProGet. Point your upstream to Packages cache on first access automatically. Make sure your choco clients are using your proxy repository as a source and NOT the default community repository. See source command for more information.
    • You can also just download the package and push it to a repository Download

3. Enter your internal repository url

(this should look similar to

4. Choose your deployment method:

choco upgrade visualstudio2013testagents -y --source="'STEP 3 URL'" [other options]

See options you can pass to upgrade.

See best practices for scripting.

Add this to a PowerShell script or use a Batch script with tools and in places where you are calling directly to Chocolatey. If you are integrating, keep in mind enhanced exit codes.

If you do use a PowerShell script, use the following to ensure bad exit codes are shown as failures:

choco upgrade visualstudio2013testagents -y --source="'STEP 3 URL'"

Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
  Exit 0

Exit $exitCode

- name: Ensure visualstudio2013testagents installed
    name: visualstudio2013testagents
    state: present
    version: 12.0.21005.20160105
    source: STEP 3 URL

See docs at

chocolatey_package 'visualstudio2013testagents' do
  action    :install
  version  '12.0.21005.20160105'
  source   'STEP 3 URL'

See docs at

    Name: visualstudio2013testagents,
    Version: 12.0.21005.20160105,
    Source: STEP 3 URL

Requires Otter Chocolatey Extension. See docs at

cChocoPackageInstaller visualstudio2013testagents
   Name     = 'visualstudio2013testagents'
   Ensure   = 'Present'
   Version  = '12.0.21005.20160105'
   Source   = 'STEP 3 URL'

Requires cChoco DSC Resource. See docs at

package { 'visualstudio2013testagents':
  provider => 'chocolatey',
  ensure   => '12.0.21005.20160105',
  source   => 'STEP 3 URL',

Requires Puppet Chocolatey Provider module. See docs at

salt '*' chocolatey.install visualstudio2013testagents version="12.0.21005.20160105" source="STEP 3 URL"

See docs at

5. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

Private CDN cached downloads available for licensed customers. Never experience 404 breakages again! Learn more...

This package was approved by moderator gep13 on 07 Jan 2016.


Microsoft Visual Test Agent and Controller for running compiled tests on a node without installing all of Visual Studio.
By default this package installs only the Test Agent. Use the switch /ControllerInsteadofTestAgent to install the Test Controller instead.
If you need both on one node, run the package once with no options and then again with '/ControllerInsteadofTestAgent -Force'

#### Package Parameters
The following package parameters can be set:

* /ControllerInsteadofTestAgent - install the Test Controller instead of just the Test Agent.

These parameters can be passed to the installer with the use of -params.
For example: -params '"/ControllerInsteadofTestAgent"'.
To add Controller to a machine with Agent already installed: -params '"/ControllerInsteadofTestAgent"' -force.

$ErrorActionPreference = 'Stop'; # stop on all errors

$packageName= 'visualstudio2013testagents'
$ISOName = 'vs2013.5_agts_enu.iso'
$logPath    = "$env:temp\$($packageName)_$(Get-date -format 'yyyyMMddhhmm').log"
$toolsDir   = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"
$url        = "$ISOName"
$silentArgs = "/silent /log $logPath"

$checksum      ='C0D8789271E254E3B8307A78B6F5DC76532345C1'
$checksumType  = 'sha1'

$arguments = @{};
# /ControllerInsteadofTestAgent
$packageParameters = $env:chocolateyPackageParameters;

# Default the values
$ControllerInsteadofTestAgent = $false

# Now parse the packageParameters using good old regular expression
if ($packageParameters) {
    $match_pattern = "\/(?<option>([a-zA-Z]+)):(?<value>([`"'])?([a-zA-Z0-9- _\\:\.]+)([`"'])?)|\/(?<option>([a-zA-Z]+))"
    $option_name = 'option'
    $value_name = 'value'

    if ($packageParameters -match $match_pattern ){
        $results = $packageParameters | Select-String $match_pattern -AllMatches
        $results.matches | % {
      throw "Package Parameters were found but were invalid (REGEX Failure)"

    if ($arguments.ContainsKey("ControllerInsteadofTestAgent")) {
        Write-Host "Installing Test Controller instead of Test Agent because /ControllerInsteadofTestAgent was used."
        $ControllerInsteadofTestAgent = $true
} else {
    Write-Debug "No Package Parameters Passed in";

Write-Output "Logs for installers will be in $logPath"
Get-ChocolateyWebFile "$packageName" "$env:temp\$ISOName" $url -checksum $checksum -checksumType $checksumType

$VCDFullPath = $null
$ISOMountDrive = $null

If (([version](gwmi win32_operatingsystem).version) -ge [version]"6.3.9600")
{ #Use mount-disk for server 2012 R2 - works over remoting
  $mountresult = mount-diskimage -imagepath "$env:temp\$ISOName" -passthru
  $ISOMountDrive = ($mountresult | Get-Volume).DriveLetter + ":"
{ #Other OSes use virtualclonedrive package

  If (Test-Path 'C:\Program Files (x86)\Elaborate Bytes\VirtualCloneDrive\daemon.exe')
    $VCDFullPath = 'C:\Program Files (x86)\Elaborate Bytes\VirtualCloneDrive\daemon.exe'

  If (!($VCDFullPath))
    Throw "Could not find virtual clone drive's `"daemon.exe`" - it is required to mount the downloaded ISO, exiting..."
    & $VCDFullPath -mount "$env:temp\$ISOName"

  $ISOMountDrive = @(65..90 | ForEach-Object {[char]$_ + ":"}) | Where-Object {Test-Path "$_\testagent\vstf_testagent.exe"} | select -first 1

try {
    If (!$ControllerInsteadofTestAgent)
      Install-ChocolateyInstallPackage 'visualstudiotestagent' 'exe' $silentArgs "$ISOMountDrive\testagent\vstf_testagent.exe"
      Install-ChocolateyInstallPackage 'visualstudiotestagent' 'exe' $silentArgs "$ISOMountDrive\TestController\vstf_testcontroller.exe"
    start-sleep -seconds 5
    If ($VCDFullPath)
      Try {start-process "$VCDFullPath" -argumentlist "-unmount" -ErrorAction SilentlyContinue}
      Catch {#swallow dismount ISO errors
    If (([version](gwmi win32_operatingsystem).version) -ge [version]"6.3.9600")
      dismount-diskimage -imagepath "$env:temp\$ISOName"
    If (test-path env:ProgramFiles`(x86`)) {$PF = ${env:ProgramFiles(x86)}} Else {$PF = $env:ProgramFiles}
    Install-ChocolateyPath "$PF\Microsoft Visual Studio 12.0\Common7\IDE\CommonExtensions\Microsoft\TestWindow" 'Machine'
    Install-ChocolateyPath "$env:windir\Microsoft.NET\Framework\v4.0.30319" 'Machine'
catch {
    throw $_.exception

Log in or click on link to see number of positives.

In cases where actual malware is found, the packages are subject to removal. Software sometimes has false positives. Moderators do not necessarily validate the safety of the underlying software, only that a package retrieves software from the official distribution point and/or validate embedded software against official distribution point (where distribution rights allow redistribution).

Chocolatey Pro provides runtime protection from possible malware.

Version Downloads Last Updated Status
visualstudio2013testagents Update 5 (Install) 12.0.21005.20160101 334 Friday, January 1, 2016 Approved
visualstudio2013testagents Update 5 (Install) 12.0.21005.1 376 Monday, December 21, 2015 Approved

Includes Update 5. The Microsoft Agents do not provide an uninstaller, so neither does this package.

Discussion for the Agents for Visual Studio 2013 Package

Ground Rules:

  • This discussion is only about Agents for Visual Studio 2013 and the Agents for Visual Studio 2013 package. If you have feedback for Chocolatey, please contact the Google Group.
  • This discussion will carry over multiple versions. If you have a comment about a particular version, please note that in your comments.
  • The maintainers of this Chocolatey Package will be notified about new comments that are posted to this Disqus thread, however, it is NOT a guarantee that you will get a response. If you do not hear back from the maintainers after posting a message below, please follow up by using the link on the left side of this page or follow this link to contact maintainers. If you still hear nothing back, please follow the package triage process.
  • Tell us what you love about the package or Agents for Visual Studio 2013, or tell us what needs improvement.
  • Share your experiences with the package, or extra configuration or gotchas that you've found.
  • If you use a url, the comment will be flagged for moderation until you've been whitelisted. Disqus moderated comments are approved on a weekly schedule if not sooner. It could take between 1-5 days for your comment to show up.
comments powered by Disqus