Skip to end of metadata
Go to start of metadata

Allows you to setup agents on Windows machines over Windows Management Instrumentation (WMI)

Plugin Information

View WMI Windows Agents on the plugin site for more information.

Usage and troubleshooting

Split out of Jenkins core. See Windows agents fail to start via DCOM for warnings. Installing Jenkins as a Windows service also contains some information about running agents on Windows.


Version 1.4 (Dec 20, 2018)

  • The plugin was renamed to "WMI Windows Agents Plugin" to reflect what it actually does
  • PR #9 - escape the "-tcp" argument in the Windows service XML command 
  • JENKINS-42752 - cleanup usages of the old "slave" term in the Web UI

Version 1.3.1 (Mar 14 2017)

This release solves the critical regression in Jenkins 2.50 (JENKINS-42724)

  • Make the plugin independent from the jenkins-slave.xml sample in the core [JENKINS-42746]

Notes: 1.3 is burned, because it has been released from the wrong branch. The functionality of the artifact is actually the same.

Version 1.2 (Aug 10 2016)

Version 1.1 (Jun 10 2015)

  • Now on 1.554.3.
  • Restoring a lost help file.
  • German localization.

Version 1.0 (Jan 03 2013)

  • initial release


  1. looks like it doesn't work on 2008R2 & 2012 ...

  2. I am not sure if this i the right place, but I want to make a request for a very small change.

    The windows slave based around jenkins-slave.exe, was wriiten for Net Framework 2.0, a framework which is not available by default on Windows Server 2012 (probably 8.* as well). While there is an option to install the .Net Framework 3.*, a framework compatible with version 2.0, there is another option available for Jenkins-slave.exe which make the exe work with newer Framework versions (inplicit, making the exe available by default on all actual Windows versions).

    Is it possible to make this adjustment?

    The idea is to change only the Jankins-slave.exe.config file:

    <!- see ->
        <generatePublisherEvidence enabled="false"/>

          <supportedRuntime version="v4.0" />
          <supportedRuntime version="v2.0" />



    This will make the same exe available for .Net Framework 4.0, implicit with Windows Server 2012.

  3. Hey there

    Version 1.3.1 of this plugins use version jcifs 1.3.17 which contains some security problems (see, which is not very good for the security of our company.

    Is it possible to update to 1.3.19 of jcifs?

    That would be very kind of you.

    Marcel Meschenmoser

  4. Do you support openjdk 1.8.0_171 ?