I have it working with Microsoft Web Deploy v. 3.6, but I am required to upgrade to 4.0 due to the security issues found with web deploy 3.6 (CVE-2025-53772). The 11.2 Enterprise docs state Microsoft Web Deploy 3.6 should be used and gives no indication on whether or not upgrading this package allowed. Anyone have any insight to share?
Solved! Go to Solution.
Thanks Cody. I went ahead and tried it out on our dev server and it worked. For anyone looking, these are the steps I followed and our Enterprise setup specs:
Hey @MKF62
If it doesn't directly say that 4.0 is supported, there's a chance that it won't be supported. It's more of a chance that it would be supported as it's a more recent version, but if an internal coding change had happened or some type of structure difference, it may end up being incompatible.
I would reach out to Esri support and request to see if they have tried this or of any of their tickets have record of this working/not working. If there is a safe amount of people who have experience doing this, then I would say you're probably fine, but ensure that you have a ticket open just in case it goes south.
Cody
Thanks Cody. I went ahead and tried it out on our dev server and it worked. For anyone looking, these are the steps I followed and our Enterprise setup specs:
Hey @MKF62
Great work! Glad it was able to function normally and thank you for coming back with instructions!
Cody
That's great that it works with Web Deploy V 4.0.
One thing to keep in mind though, Web Deploy is not a product that Microsoft is 'actively' maintaining. It may not need any updates, but as a lot of companies have moved to other options for deployment, something to keep in mind when considering it as a solution. Microsoft seems pretty focused on their Azure Line of Products for deployment, and as such Web Deploy becomes a Legacy Tool, that I'm not sure how long it will even be available.
True, but it would be on ESRI to update the dependencies of ArcGIS Enterprise for Windows then as it is a required dependency if you want to run it on Windows servers. It’s not really in the customers’ hands at the moment unless a customer wants to move their deployment to Linux instead of Windows.