On Wednesday, May 11, 2022 at 6:11:39 PM UTC-6 slide wrote:
> Cross posting to the dev group to see if there is any feedback there. > > ---------- Forwarded message --------- > From: slide <Unknown> > Date: Friday, May 6, 2022 at 3:13:33 PM UTC-7 > Subject: WMI Windows Agents plugin > To: Jenkins User Mailing List <Unknown> > > > Hi Everyone, > > The WMI Windows Agents plugin uses a library called j-interop. This > library was last released in 2010. Microsoft has made some changes to the > DCOM protocol since this time. One particular change is highlighted in > https://issues.jenkins.io/browse/JENKINS-67604, currently you can > override this behavior in the registry, but in March of 2023, that will no > longer be possible. This means that the WMI Windows Agent plugin may become > unusable, unless someone who knows enough about DCOM internals can update > j-interop with support for the new features (j-interop supports DCOM 5.4, > the current version is 5.7 and has several additions/changes). With Windows > Server 2019 and Windows 10, SSH is a viable option for Windows agents. > > I would like to recommend deprecating the WMI Windows Agents plugin by > March 2023. I think this gives enough time for people to migrate to either > SSH or the Windows Cloud plugin (which uses a more modern remote management > interface, WinRM). Basically this would mean the option to "Let Jenkins > control this Windows agent as a Windows service" would no longer be > available. > > Any thoughts on this? > > I agree that we should deprecate the WMI Windows Agents plugin. SSH agents on Windows are working great for me. Mark Waite > -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/28c07a39-3724-497c-9ced-444a45b4e608n%40googlegroups.com.
