Skip to content

Latest commit

 

History

History
103 lines (73 loc) · 3.95 KB

SETUP-WINDOWS-AGENT.md

File metadata and controls

103 lines (73 loc) · 3.95 KB
Raw

Windows Agent with EC2 Fleet Plugin

This guide describes how to configure Windows EC2 Instance to be good for run as Agent for EC2 Fleet Jenkins Plugin. At the end of this guide you will get AWS EC2 AMI (Image) which could be used for Auto Scaling Group or EC2 Spot Fleet to run Windows agents.

Big thanks to @Michenux for help to find all details

Note Before this, please consider to use Windows OpenSSH https://github.com/jenkinsci/ssh-slaves-plugin/blob/master/doc/CONFIGURE.md#launch-windows-slaves-using-microsoft-openssh

Note This guide uses Windows DCOM technology (not open ssh) it doesn't work over NAT, so Jenkins Master EC2 Instance should be placed in same VPC as Agents managed by EC2 Fleet Plugin.

Run EC2 Instance with Windows

  1. Note Windows Password for this guide
  2. Login to Windows

Create Jenkins User

  1. Goto Local Users and Groups
  2. Click Users
  3. Create New with name jenkins
  • Set password and note it
  • Set Password never expires
  • Set User cannot change password
  • Unset User must change password at next logon
  1. Goto user properties, find Member Of add Administrators group

Login to Windows as jenkins user

Configure Windows Registry

  1. Run regedit

  2. Set HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem\LongPathsEnabled to 1

  3. Goto HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System

  4. Create/Modify DWORD-32 with name LocalAccountTokenFilterPolicy value 1

  5. Goto HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Lsa

  6. Create/Modify DWORD-32 with name LMCompatibilityLevel value 2

    • send NTLM authentication only

  7. Find key 76A64158-CB41-11D1-8B02-00600806D9B6

    • it’s in HKEY_CLASSES_ROOT\CLSID

  8. Right click and select Permissions

  9. Change owner to Administrators select apply to children

  10. Add Full Control to Administrators make sure to apply for children as well

  11. Change owner back to NT Service\TrustedInstaller select apply to children

  12. Run service Remote Registry

  13. Restart Windows

Configure smb

  1. Run as PowerShell as Administrator
  2. Run Enable-WindowsOptionalFeature -Online -FeatureName smb1protocol
  3. Run Set-SmbServerConfiguration -EnableSMB1Protocol $true

Configure Firewall

  1. Search for Windows Defender Firewall
  2. Click Advanced settings
  3. Goto Inbound Rules
  4. Add Remote Assistance TCP 135
  5. Add File and Printer Sharing (NB-Name-In) UDP 137
  6. Add File and Printer Sharing (NB-Datagram-In) UDP 138
  7. Add File and Printer Sharing (NB-Session-In) TCP 139
  8. Add File and Printer Sharing (SMB-In) TCP 445
  9. Add jenkins-master 40000-60000 TCP 40000-60000
  10. Add Administrator at Distance COM+ (DCOM) TCP C:\WINDOWS\System32\dllhost.exe
  11. For all created goto Properties -> Advanced and set Allow edge traversal

Install Java

  1. Open PowerShell
  2. Install Scoop Invoke-Expression (New-Object System.Net.WebClient).DownloadString('https://get.scoop.sh') scoop install git-with-openssh
  3. scoop bucket add java
  4. scoop install ojdkbuild8-full

Configure System Path for Java

  1. Goto Control Panel\System and Security\System
  2. Goto Advanced System Settings
  3. Goto Environment Variables...
  4. Add Java Path (C:\Users\jenkins\scoop\apps\ojdkbuild8-full\current\bin installed before by scoop) to System PATH

Create EC2 AMI

  1. Goto to AWS Console and create image of preconfigured instance

Before using this AMI for Jenkins Agent

  • Make sure you required traffic could go to Windows from Jenkins. You can find required ports above in Configure Firewall section

Troubleshooting