Known Issues
- Last Updated: May 4, 2022
- 1 minute read
- MOVEit Transfer
- Version 2022
- Documentation
This section outlines known issues and typical workarounds for MOVEit Transfer.
|
ID |
Category |
Known Issue in MOVEit Transfer |
|---|---|---|
|
31190 |
REST API |
Some virtual folder operations do not extend to the REST API. Workaround: For full parity, use the WebUI or MOVEit Automation. |
|
35331 |
Key Rotation |
If disk capacity is less than the largest file in your filestore and you run key rotation, your key rotation process will fail to convert that file. |
|
22448 |
Key Rotation |
Key rotation functionality does not extend directly to environments that use Azure Blob Service for their filestore. Workaround: Azure Storage has its own encryption scheme and key management infrastructure. |
|
51533 |
Outlook Add-In |
If Internet Explorer is configured with Enhanced Security Configuration (ESC) and you run MOVEit Add-in for Microsoft Outlook, the add-in pane fails to load. For example, this issue might occur if you run MOVEit Add-in for Microsoft Outlook with older versions of Windows that still include Internet Explorer. (Note that Windows Server enables IE ESC by default.) Workaround: Run the MOVEit Add-in for Microsoft Outlook from a machine that does not bundle Internet Explorer, such as a non-server version, or add the resource needed by MOVEit Add-in for Microsoft Outlook to launch as a trusted site. You can also disable IE ESC. |
| 57441 | Client Cert | If an SSL Client Certificate is used to authenticate against Transfer
on Windows Server 2022, and the client uses TLS 1.3, IIS error 403.7
returns. This occurs in cases where the client connection defaults to
TLS 1.3 before the Client Cert can be
used. Workaround: Firefox: Enable post-handshake authentication in browser. Edge/Chrome: Disable TLS 1.3. |