Skip to main content

UDMG 3.2.x Maintenance

Stonebranch provides UDMG maintenance through updated installation packages.

This page lists the product installation package maintenance history for UDMG 3.2.x.

Product Packaging​

A package maintenance level is incremented when the package changes or the package installation changes.

Stonebranch changes product version, release, or modification identifiers at its discretion when it deems an appropriate number of enhancements or capabilities have been introduced to warrant the change.

Packaging Methods​

The UDMG 3.2.x packages are provided in formats appropriate for the target platforms.

See Installation and Configuration Roadmap for information on installing UDMG.

Package Maintenance Levels​

This section identifies the changes included in UDMG 3.2.x.

Release 3.2.1 - February 2, 2026​

New Features​

Change IDScopeTitleDescription
#49174UDMG ServerWindows Support

UDMG can be deployed on Windows hosts, with a Windows-compatible installer and runtime support.

Compatible OS versions:

  • Windows Server 2016
  • Windows Server 2019
  • Windows Server 2022
  • Windows Server 2025
#49027UDMG ServerForward Proxy

UDMG can now route Remote FTP Server and Remote SFTP Server Endpoints to a Forward Proxy configured at the Domain level.

Supported proxy protocols:

  • SOCKS5: UDMG asks the proxy to open a TCP connection to the target host/port and tunnels through it.
  • HTTP/HTTPS: UDMG establishes a tunnel through an HTTP proxy using the CONNECT method to the target host/port.

Known Issues​

Change IDScopeTitleDescription
#53645Web Transfer Client (WTC)Large WTC Uploads May Leave Temporary Multipart Files on Disk

When transferring files larger than 32 MB through the WTC, a temporary multipart-* file may remain on the system temp folder even after a successful transfer.

This can gradually consume disk space.

These files will be left in:

  • /tmp (Linux)
  • C:\Windows\Temp (Windows)

The actual path depends on the host system temp folder configuration.

info

The recommended workaround is to monitor the temp directory and ensure appropriate cleanup.