How does it work?
This section goes into the details of how the managed Windows agent launcher actually works.
Jenkins uses multiple protocols to install the actual agent as a Windows service and then start it. These protocols have been around for a quite some time.
Important
|
The installation process assumes that the JRE is installed and accessible on the agent. Please see Troubleshooting WMI Windows Agents if you need further help. |
-
It first uses CIFS (also known as "Windows file share protocol") to push files into the agent. When used by someone with administrative privileges, Windows file shares expose what’s commonly known as "administrative shares", which are hidden exported directories that cover every drive in the system.
-
It then uses DCOM to talk to WMI to install and start a service remotely.
Troubleshooting
Changelog
-
See GitHub Releases for recent versions
-
See this page for previous releases