Mover 发行说明Mover release notes

本文介绍 Mover 迁移工具中的累积功能和增强功能。This article discusses cumulative features and enhancements in the Mover migration tool.

后端 v1.19.22(2020 年 12 月 16 日)Backend v1.19.22 (December 16, 2020)

  • 修复。Fix. Box限制了Mover客户端的某些功能后,用户无法授权新的Box(单用户)连接器。Users could not authorize new Box (Single User) connectors after Box restricted some features from Mover's client. 此问题已修复。This issue is fixed.
  • 修复。Fix. 某些用户在尝试转移到某些SharePoint Online文档库时收到错误消息“找不到文档库”。Some users received the error "document library could not be found" when attempting transfers to certain SharePoint Online Document Libraries. 此问题已修复。This issue is fixed.
  • 修复。Fix. 重试受影响的操作时,从OneDrive Consumer传入或传入OneDrive Consumer的传输受到限制。Transfers from or into OneDrive Consumer that were throttled had issues when re-trying the affected operations. 有关这些传输的授权相关错误消息将出现在用户日志中。An authorization related error message would appear on the User Log for these transfers. 现在,重试已获得适当的授权。Re-tries now have proper authorization in place. 此问题已修复。This issue is fixed.

后端 v1.19.21.5(2020 年 12 月 10 日)Backend v1.19.21.5 (December 10, 2020)

此版本解决了与Egnyte Connector检索组有关的问题。This release fixes an issue with Egnyte Connector retrieving groups.

  • 修复。Fix. 在尝试为Egnyte检索组时,由于创建无限循环,迁移将失败。While trying to retrieve groups for Egnyte, migration would fail as it created an infinite loop. 群组检索现已成功。Retrieval of groups is now successful.

后端 v1.19.21.1(2020 年 12 月 4 日)Backend v1.19.21.1 (December 4, 2020)

此版本解决了Box连接器授权的问题。This release fixes an issue with Box connector authorization.

  • 修复。Fix. 一些用户报告了授权新Box连接器或重新授权现有Box连接器的问题。Some users reported issues authorizing new Box connectors or re-authorizing existing Box connectors. 这是由于Box阻止了我们对当前Box客户端的授权尝试。This is due to Box blocking our authorization attempts for our current Box client. 已创建新的Box客户端来绕过此问题,并且Box连接器的授权应再次起作用。New Box clients have been created to bypass this issue and authorization of Box connectors should be working again.

后端 v1.19.20(2020 年 12 月 1 日)Backend v1.19.20 (December 1, 2020)

  • 可访问性:“用户日志”视图现在对页面中的所有元素使用不同的ID。Accessibility: The User Log view now uses a different ID for all elements in the page.

前端 v1.19.2(2020 年 12 月 1 日)Frontend v1.19.2 (December 1, 2020)

  • 修复。Fix. 辅助功能:在“转移向导”的“选择源”步骤中加载文件夹之前,已激活“开始复制”按钮。Accessibility: 'Start copy' button was getting activated before loading of folders in 'Select Source' step in the Transfer Wizard. 如果用户调用“开始复制”,则将通过从源和目标的根目录复制所有项目来触发传输。If the user invoked 'Start Copy', the transfer would get triggered by copying all items from the root of the source and destination. 已修复了一个问题,可以在激活“开始复制”按钮之前等待文件夹完全加载。A fix has been made to wait for folders to be fully loaded before activating the Start Copy button.
  • 修复。Fix. 可访问性:使用多个制表符在“传输向导”中浏览文件夹列表,这对于具有运动障碍的用户来说,导航变得更加困难。Accessibility: Navigating through the list of folders in the Transfer Wizard using multiple tab stops was making navigation harder for users with motor impairments. 已添加修复程序,以使用键盘上的箭头键浏览列表。Fix has been added to navigate the list using the keyboard arrow keys.
  • 辅助功能:“转移摘要”面板现在将在包含交易信息的顶部详细信息表中为每个值显示一个工具提示。Accessibility: The Transfer Summary panel will now display a tooltip for every value in the top details table containing the transaction information.
  • 辅助功能:通过按下过滤器搜索框中的向下和向上箭头键,现在可以使用键盘访问Migration Manager的“活动过滤器”自动建议。Accessibility: The Migration Manager "Active filters" auto-suggestions are now accessible with the keyboard by pressing the down and up arrow keys from the filter search box.
  • 辅助功能:在“迁移管理器”的“活动过滤器”部分中,“信息”按钮具有包含过滤说明的工具提示。Accessibility: In the Migration Manager, Active Filters section, the info button had a tooltip with filtering instructions. 但是,即使工具提示处于焦点位置,讲述人也不会阅读内容。However, the narrator would not read the content, even if the tooltip was in focus. 为了使内容可访问,消除了工具提示,而是添加了指向文档页面的正确链接:https://aka.ms/MoverMigrationManagerFilters。To make the content accessible, the tooltip was eliminated and, instead, a proper link to the documentation page was added: https://aka.ms/MoverMigrationManagerFilters.

后端 v1.19.19(2020 年 11 月 26 日)Backend v1.19.19 (November 26, 2020)

  • 在传输期间,可能存在无法恢复的故障。During a transfer there might be a failure that is unrecoverable. 这意味着传输完全失败,并且任何重新运行都无法解决它,例如,超过了存储配额。It means the transfer completely failed and any rerun would not fix it, such as, Storage Quota Exceeded. 但是,在我们的302处理期间发生这种情况时,该处理的状态优先。However, when this happens during our 302 processing, the status of this processing take precedence. 不幸的是,这意味着原来的不可恢复状态现在丢失了。Unfortunately, this means that the original unrecoverable state is now lost. 已修复此问题。This has been fixed. 如果传输失败并且它是不可恢复的状态,那么现在将保留该状态并将其适当地显示给用户。If the transfer failed and it is an unrecoverable state, this state will now be preserved and displayed appropriately to the user.

后端 v1.19.18(2020 年 11 月 10 日)Backend v1.19.18 (November 10, 2020)

  • 修复。Fix. 现可在 Microsoft Word 中正确转移和呈现 Box 备注中包含的图像。Images included in Box notes are now correctly transferred and rendered in Microsoft Word.
  • 修复。Fix. 现在可在运行从 Google 到 Office 365 的传输时正确迁移元数据 “创建时间”。The metadata "Created time" is now correctly getting migrated when running a transfer from Google to Office 365.
  • 对 Office 365 连接器的 SharePoint Online 站点的检索尝试已得到增强和扩展。Retrieval attempts of SharePoint Online sites for an Office 365 connector have been enhanced and expanded.
  • 已调整迁移作业限制,从而提高了传输到 Office 365 的可靠性。Migration job limits have been adjusted, resulting in improved reliability for transfers going into Office 365.

后端 v1.19.17(2020 年 11 月 3 日)Backend v1.19.17 (November 3, 2020)

  • 修复。Fix. 当目标不支持直接上传时,从代理到目标的传输将失败。When destinations did not support direct upload, transfers from the Agent to the destination would fail. 现在,可以检测到直接上传目标,并且当目标不支持直接上传时,其处理已得到纠正。Direct Upload destinations are now detected and handling has been corrected when the destination does not support direct upload.

  • 修复。Fix. 在成功和失败的情况下,将直接上传添加到用户日志筛选器。Added direct uploads to user log filters, both on success and failure. 这修复了日志记录中的一个缺陷:使用直接上传功能(现在是默认设置)的代理不会将其日志条目包含在用户日志中。This fixes a defect in logging where Agents using the Direct Upload feature (which is now the default) would not have their log entries included in the user logs. 这将为代理用户启用正确的反馈。This will enable correct feedback for users of the Agent.

前端 v1.19.1(2020 年 10 月 28 日)Frontend v1.19.1 (October 28, 2020)

此版本修复了以下客户问题:This release fixes these customer issues:

  • 修复。Fix. 在迁移管理器中编辑包含大量项目的源路径或目标路径时,侧面板最多只显示 100 个项目,其余内容将显示为空白。When editing a source or destination path in Migration Manager with lots of items, the side panel would only render up to 100 items and the rest would appear blank. 文件选取器现在将显示所有内容。The file picker now displays all content.

  • 修复。Fix. 当客户以管理员身份为电子邮件帐户输入特定格式时,即使使用有效的电子邮件地址,电子邮件验证也可能失败。When a customer entered a certain format for an email account as an admin, the email validation could fail even with a valid email addresses. 已修复此问题。This has been fixed.

后端 v1.19.10(2020 年 10 月 15 日)Backend v1.19.10 (October 15, 2020)

前端 v1.19.0(2020 年 10 月 15 日)Frontend v1.19.0 (October 15, 2020)

后端 v1.19.15(2020 年 10 月 14 日)Backend v1.19.15 (October 14, 2020)

  • 对 rateLimit 提供程序做了改进。Improvement to ratelimit provider. 通常情况下,大规模迁移的移动速度会更快。In general, large migrations should now move faster.
  • 已删除电子邮件身份验证。Email auth removed. 此操作不再受支持。This is no longer supported.

后端 v1.19.14(2020 年 10 月 8 日)Backend v1.19.14 (October 8, 2020)

  • 修复。Fix. 修复了注册电子邮件不请求“答复”操作的问题,因为现在正在从“无答复”地址发送 Mover 电子邮件。Fixed sign up emails to not request a "reply" action since Mover emails are now being sent from a "no-reply" address. 现在,用户将被定向到公共文档。Users are now being directed to the public documentation.
  • 修复。Fix. 减少并在某些情况下消除了“无法加载迁移”作业错误。Decreased and in some cases eliminated "failed to load migration" job errors.

后端 v1.19.13(2020 年 10 月 1 日)Backend v1.19.13 (October 1, 2020)

  • 通过提高我们的缓存系统的可靠性来提高整体系统的稳定性。Improve stability of the overall system by improving the reliability of our caching systems.
  • 在创建从 Office 365 到 Office 365 的迁移之后,如果用户试图自动发现迁移任务,并且如果它未能检索源租户的用户和 SPO 网站,则该应用将报告一个奇怪的错误。Right after creating a migration from Office 365 and into Office 365, if the user tried to autodiscover migration tasks and if it failed to retrieve the source tenant's users and SPO sites, the app would report a strange error. 已修复此问题,并可报告正确的错误。This has been fixed with a proper error being reported instead.

后端 v1.19.11(2020 年 9 月 24 日)Backend v1.19.11 (September 24, 2020)

  • 修复。Fix. 一些客户在新创建的向 Office 365 的迁移中自动发现任务时遇到问题。Some customers were having issues autodiscovering tasks in newly created migrations into Office 365. 客户现在应该能够自动发现任务。Customers should now be able to autodiscover tasks.

代理 v1.3.5(2020 年 9 月 22 日)Agent v1.3.5 (September 22, 2020)

  • 已针对所有安装类型发布了新代理。A new Agent has been released for all install types. 版本 1.3.5 是所有客户所需的更新。Version 1.3.5 is a required update for all customers. 此版本更新用于连接到 Bifrost 的固定证书。This release updates the pinned certificates used for connecting to Bifrost. 自 2020 年 9 月 26 日起,任何较旧的代理都将无法连接到 Bifrost,也无法传输文件。As of September 26, 2020, any older Agents will not connect to Bifrost and not be able to transfer files.

后端 1.19.9(2020 年 9 月 15 日)Backend v1.19.9 (September 15,2020)

  • 修复。Fix. 以前,诸如“修改者”之类的作者信息不会发送到目标位置。Previously, authorship information such as "Modified By" was not sent to the destination. 现在,来自 Google 源的元数据已包含在传输中,并显示在 Office 365 目标位置。Metadata from Google sources is now included in the transfer and displayed at the Office 365 destination.

  • 修复。Fix. 在传输过程中,作为失败跳过的项目(不支持在源中导出或在目标位置导入的项目)仅在用户日志中显示为失败,而不在报告(如迁移错误报告)中显示为失败。During transfers, items skipped as failures (unsupported items for export in the source or import in the destination) were showing as failures only in the user logs but not in reports, such as the Migration Error Report. 这些失败现在也出现在报告中。These failures also now appear in the reports.

  • 修复。Fix. 当用户取消作业时,该作业将经历一个要取消的过程。When a user cancels a job, the job goes through a process to be cancelled. 以前,如果作业在取消过程完成之前完成,则会自动启动重新运行传输。Previously, if the job finished before the cancel process completed, the rerun transfer was automatically initiated. 已修复此问题。This has been fixed. 如果作业正在取消中,则不会触发自动重新运行传输。An automatic rerun transfer is not triggered if a job is in the process of being cancelled.

  • 通过增强缓存系统的可靠性,整体系统的稳定性得到了改善。Improvement has been made in the overall system's stability through enhancements to the reliability of our caching systems.

  • 修复。Fix. 在从共享驱动器进行 G Suite 传输期间,一些用户收到“文件受限制”错误。During a G Suite transfer from a shared drive some users received a "File is restricted" error. 通过允许传输将这些文件移动到目标位置,已修复了此问题。This has been fixed by allowing the transfer to move those files over to the destination.

后端 1.19.8(2020 年 9 月 9 日)Backend v1.19.8 (September 9, 2020)

  • 在授权连接器时强制要求授权用户是 Office365 全局管理员或 SharePoint 管理员Enforce that authorizing user is Office365 Global Admin or SharePoint Admin when authorizing a connector

后端 1.19.7(2020 年 9 月 1 日)Backend v1.19.7 (September 1, 2020)

  • 提高了从代理连接器(文件共享)到 Office 365 连接器的数据传输速度。Improved data transfer speeds from the Agent connector (file shares) into an Office 365 connector. 客户需要将代理更新到版本 1.3.4.0。Customers will need to update the Agent to version v1.3.4.0.

  • 如果网站将 SharePoint Online 选项 ThicketSupportDisabled 设置为 false,进入某些 Office 365 网站的传输可能无法移动某些文件夹。Transfers going into some Office 365 sites may fail to move certain folders if the sites have the SharePoint Online option ThicketSupportDisabled set to false. 若要更正此问题,客户可以在遇到问题的 SharePoint Online 网站中将 ThicketSupportDisabled 设置为 trueTo correct this issue, customers can set ThicketSupportDisabled to true in the SharePoint Online sites experiencing the issues. 或者,他们可以联系 Mover 支持人员以对其传输应用解决方法。Alternatively, they can contact Mover support to apply a workaround to their transfers. 解决方法是在文件夹名称后自动附加下划线 ()。The workaround consists in automatically appending an underscore () to the folder names. 由于此 SharePoint Online 选项而可能失败的文件夹的名称以以下项结尾:The folders that may fail due to this SharePoint Online option have names ending in:

    • .files.files
    • _files_files
    • -Dateien-Dateien
    • _fichiers_fichiers
    • _bestanden_bestanden
    • _file_file
    • _archivos_archivos
    • -filer-filer
    • _tiedostot_tiedostot
    • _pliki_pliki
    • _soubory_soubory
    • _elemei_elemei
    • _ficheiros_ficheiros
    • _arquivos_arquivos
    • _dosyalar_dosyalar
    • _datoteke_datoteke
    • _fitxers_fitxers
    • _failid_failid
    • _fails_fails
    • _bylos_bylos
    • _fajlovi_fajlovi
    • _fitxategiak_fitxategiak

备注

如果 SPO 选项 ThicketSupportDisabled 已设置为 true,则不应请求解决方法,因为这可能导致数据重复。The workaround should NOT be requested if the SPO option ThicketSupportDisabled has been set to true as this may cause data duplication.

  • 当由于路径长度限制而无法将项目传输到 Office 365 时,项目将在用户日志中显示为黄色,并在迁移错误报告中显示为错误。When a transfer into Office 365 fails on items due to path length limitations, the items would show up yellow in the user logs and as errors in the migration error report. 但是,与这些失败的条目相关的消息为空。However, the messages related to these failed entries were blank. 通过确保在这些失败中添加正确的错误消息,已修复此问题。This has been fixed by ensuring that a proper error message has been added to these failures.

后端 v1.19.6(2020 年 8 月 31 日)Backend v1.19.6 (August 31, 2020)

  • 提高了传输到 Office 365 的稳定性。Improved stability for transfers going into Office 365.
  • 针对遇到问题的客户改进了 Mover 应用的注册体验。Improved sign-up experience into the Mover app for customer having issues.

后端 v1.19.5(2020 年 8 月 26 日)Backend v1.19.5 (August 26, 2020)

  • 改进了遥测以解决客户问题。Improved telemetry to tackle customer issues.

后端 v1.19.4(2020 年 8 月 20 日)Backend v1.19.4 (August 20, 2020)

  • 提高了传输到 Office 365 的稳定性。Improved stability for transfers going into Office 365.

前端 v1.18.2(2020 年 8 月 6 日)Frontend v1.18.2 (August 6, 2020)

  • 使用应用时,系统将会向in发送通知,让你知道您的请求已成功还是发生错误。While using the App, notifications are sent to let you know if your request has been successful or if an error has occurred. 提高了通知的高度和文本大小,以改善可见性和认知度。The height and text size of notifications have been increased to improve visibility and awareness.

  • 系统将会显示您是否正在尝试使用缺少 SharePoint Online 许可证的租户授权 Office 365。A message will display if you are trying to authorize Office 365 with a tenant that lacks SharePoint Online licenses.

  • 在“转移向导”中连接至 G 套件源连接器时,不会看到 Google 预扫描警告。You will not see Google pre-scan warnings when connecting to a G Suite source connector in the Transfer Wizard.

  • 所有未成功通知均会保持开放状态,以供用户读取。All non-success notifications will stay open for the user to read. 成功通知将在 5 秒之后自动关闭。Success notifications will automatically close after 5 seconds.

后端 v1.19.3(2020 年 8 月 6 日)Backend v1.19.3 (August 6, 2020)

生命周期结束通知和错误修复。End of life notification and bug fix.

  • Amazon WorkDocs 和 NetDocuments 的连接器已达到生命周期。The connectors for Amazon WorkDocs and NetDocuments have reached end of life. 该连接器已于 2020 年 7 月 1 日弃用,现有用户已收到通知。The connectors were deprecated July 1, 2020, and existing users notified. 这些连接器不再可用。These connectors are no longer available.

  • 在迁移至 Office 365 过程中,如果迁移作业无法提交,则错误条目不会被添加到用户日志或迁移错误报告。When a migration job failed to submit during a migration into Office 365, error entries were not being added to the user log or migration error report. 此问题已修复。This has now been fixed. 失败迁移作业中包含的所有文件已在用户日志和迁移错误报告中具有错误条目。All files contained in the failed migration job now have an error entry in the user log and the migration error report.

后端 1.19.2(2020 年 7 月 31 日)Backend v1.19.2 (July 31, 2020)

改进了迁移报告,修复了 bug。Migration Report improvements and bug fixes.

  • 授权 G Suite 管理员源连接器时,该模板显示预扫描警告。When authorizing the G Suite Admin source connector, the template showed the prescan warning. 由于已不再需要预扫描(因为已集成到常规扫描和传输过程中),因此已在 UI 中删除连接器授权模板中的警告。As prescan is no longer needed due to its integration into the regular scan and transfer process, the warning from the connector authorization template in the UI has been removed.

  • 对 Office 365 连接器授权或重新授权时,选取器将显示当前已登录到 Microsoft 的帐户。When authorizing or reauthorizing an Office 365 connector, a picker will show accounts that are currently signed into Microsoft. 这改进了用户体验,因为如果用户已登录 Microsoft,则无需手动输入凭据。This improves the user experience as it prevents them from manually entering their credentials if they are already logged into Microsoft.

  • 进行了一项修复,将 OneNote 笔记本与带“.one”扩展名的文件夹区分开。A fix has been made to distinguish OneNote notebooks and folders with ".one" extension. 之前,从 Office 365 源运行传输时,带 .one 扩展名的文件夹无法将文件夹的内容传输到目标中,因为应用会将它看做是 OneNote 笔记本。Previously, when running a transfer from an Office 365 source, folder names with .one extension would fail to transfer the folders' content to the destination as the app would consider it as OneNote notebook.

  • 进行了一项修复,解决了登录 Mover 时遇到的问题。A fix has been made to correct an issue when signing into Mover. 之前,即使授权看起来没问题,一些用户也没法使用其 Microsoft 帐户进行登录。Some users were unable to sign in with their Microsoft account even though authorization seems to have gone fine. 应用程序在尝试加载 UI 后,会将他们重定向回到 Mover 登录页面,但不显示任何错误消息。The application would redirect them back to the Mover login page after trying to load the UI, without any error messages. 此行为已得到修复;这些用户现可使用其 Microsoft 帐户进行登录。This behavior has been fixed; these users can now sign in with their Microsoft accounts.

  • 进行了一项修复,解决了迁移报告指标不一致的问题。A fix has been made to correct discrepancies in the migration reports metrics. 今后,将在此报告中添加更多字段,帮助用户更好地了解正在进行的迁移。In the future, more fields will be added to this report to give users a better understanding of ongoing migrations.

  • 当用户尝试对 Office 365 连接器授权时,如果租户缺少 M365 许可证,连接器授权将失败,UI 中将显示“无法检索 SharePoint Online 网站列表。When the user tries to authorize the Office 365 connector, and if the tenant lacks M365 licenses, the connector authorization will fail, and the error message "Couldn't retrieve SharePoint Online site list. 我们怀疑你的租户缺少 SharePoint Online 许可证”错误消息。We suspect your tenant lacks SharePoint Online licenses" will be displayed in the UI.

  • 当某传输自动重新排队后,它的状态现将显示为“已重新排队”,而不是“已排队”。When a transfer gets automatically re-queued, its status will now show as "Re-Queued" as opposed to "Queued". 该传输从自动重新排队中运行后,将显示为“正在重新运行”。When it is running from an automatic re-queue, it will show as "Rerunning".

  • 之前,通过已设置 job_limit 或 auto_job_limit(迁移标尺)的 Web UI 保存迁移的权限映射时,会导致这些字段回退到 null 且设置丢失。Saving the permission map for a migration via the web UI that had a job_limit set or auto_job_limit set (migration scaler) caused those fields to set back to null, and the settings were lost. 此问题现已解决。This issue is now fixed.

  • 现在将 Google 云端硬盘应用从多父级行为模型迁移到单父级行为模型期间,用户可使用 Google 云端硬盘创建驱动器文件的快捷方式。Google Drive now lets users create shortcuts to their drive files as part of migrating the Google Drive app from multi-parenting to single-parenting behavioral models. 快捷方式是链接到用户驱动器上其他文件的文件。Shortcuts are files that link to other files on the user's drive. Mover 当前不支持将这些文件移动到目标。The Mover app currently does not support moving those files to a destination. 完成后,传输状态行将显示为黄色,表示某些文件不受支持且重新重新也没法解决此问题。When completed, the transfer status row will display yellow, indicating that some files are unsupported and that rerunning won't fix it.

后端 v1.19.0(2020 年 7 月 14 日)Backend v1.19.0 (July 14, 2020)

推出令人兴奋的全新功能,助你轻松从 G Suite 和 Box 实现迁移。Exciting new features for migrations out of G Suite and Box.

  • 过去,如果要从 G Suite 迁移,需要在运行常规扫描或传输前进行“Google 预扫描”以避免重复数据。For migrations out of G Suite, requesting a "Google Pre-scan" was required before running the regular scans or transfers in order to prevent data duplication. 现在,“Google 预扫描”过程现已集成到我们的常规迁移扫描和传输过程中,无需再向我们的支持团队请求进行“Google 预扫描”。The Google Pre-scan process has now been integrated into our regular migration scan and transfer processes, eliminating the need to request a Google Pre-scan from our support team. 有关详细信息,请参阅:https://aka.ms/MoverGSuiteFor more information, please refer to: https://aka.ms/MoverGSuite
  • 如果是从 Box 迁移,则 Box 中的所有笔记将自动转换成目标账户中的 Microsoft Word 文档。For migrations out of Box, all Box Notes will now be automatically converted to Microsoft Word documents in the destination. 有关详细信息,请参阅:https://aka.ms/MoverBoxFor more information, please refer to: https://aka.ms/MoverBox

后端 v1.18.1(2020 年 7 月 8 日)Backend v1.18.1 (July 8, 2020)

  • 弃用通知Deprecation notices
    • 2020 年 7 月 1 日后,将不再支持 Amazon WorkDocs 和 NetDocuments 连接器。Starting July 1, 2020, Amazon WorkDocs and NetDocuments connectors have been deprecated. 这意味着用户无法授权新的 Amazon WorkDocs 或 NetDocuments 连接器。This means that users will not be able to authorize new Amazon WorkDocs or NetDocuments connectors. 但是,在 2020 年 8 月 1 日生命周期结束前,用户仍可使用现有的 Amazon WorkDocs 和 NetDocuments 连接器。However, users will still be able to use existing Amazon WorkDocs and NetDocuments connectors until their end-of-life date of August 1, 2020. 建议用户尽快停止涉及这两种连接器的现有迁移工作。Users are encouraged to wrap up existing migrations involving these two connectors as soon as possible.
  • 错误报告改进Error reporting improvements
    • 改进了来自“代理”连接器的“用户日志”中显示的错误消息。Improved error messages displayed in the User Log coming from the Agent connector.
  • 稳定性修复Stability fixes
    • 现在,得益于性能优化,大规模传输到 Office 365 完全失败(迁移管理器中的红色行)的可能性更低。Large transfers into Office 365 are now less likely to fail completely (red row in the Migration Manager), as a result of performance optimizations.

后端 v1.18.1(2020 年 7 月 1 日)Frontend v1.18.1 (July 1, 2020)

  • 辅助工具修复Accessibility fixes
    • 删除了“传输向导”的“授权新连接器”链接中的双制表位。Removed double tab stops in Authorize New Connector links in the Transfer Wizard.
    • 修复了“迁移管理器”的统计信息。现在,可在所有缩放级别和所有屏幕大小的设备中正确显示。Fixed Migration Manager stats to display properly in all zoom levels, and in devices of all screen sizes.
    • 现在,当处于焦点时,应用程序中的所有链接会显示大纲。Enabled outlines on all links throughout the application when they have focus. 这将帮助使用键盘的用户在应用程序中导航时定位当前处于焦点中的元素。This will help users locate the current element in focus when navigating the application using the keyboard.
    • 删除了当用户没有迁移内容时,“迁移管理器”中的“即将推出”视频。Removed "Coming Soon" video in the Migration Manager when the user has no migrations.
    • 删除了用户关闭帐户时提供反馈的提示。Removed prompt to provide feedback when users close their accounts. 用户在完成迁移后自然会删除其帐户。It's natural for users to delete their accounts when their migrations are done. 他们也可以联系支持人员提供反馈。Alternatively, they can contact support to provide feedback.
    • 为使用高对比度浏览器模式浏览应用程序的用户添加了精简版本的“使用 Microsoft 登录”按钮。Added a light version for the "Sign in with Microsoft" button for users browsing the application using a high-contrast browser mode.
    • 为使用高对比度浏览器模式浏览应用程序的用户修复了 Mover 徽标。Fixed the Mover logo for users browsing the application using a high-contrast browser mode.
    • 现在,在高对比度浏览器模式下,导航栏会在活动和重点项上显示标记。Navigation bars will now show a marker on the active and focused items in high-contrast browser mode.

前端和后端 v1.18.0(2020 年 6 月 25 日)Frontend & Backend v1.18.0 (June 25, 2020)

  • 错误报告改进Error reporting improvements
    • 在迁移到 Office 365 过程中,我们将跳过处理大小超过 15 GB 的源文件并将其标记为“成功跳动”。During a migration into Office 365, we would skip processing of source files over 15 GB and mark them as successfully skipped. 此更改已推出一段时间,现在不再处理它们和报告处理错误。This changed for a while to instead process them and report on the processing errors. 虽然 Office 365 现在支持 100 GB 大小的文件,但尚不支持迁移大小超过 15 GB 的文件。While Office 365 supports 100 GB files now, migration of files over 15 GB is not yet supported. 因此,我们已转而继续采用之前的方式,即跳过大小超过 15 GB 的文件。So we have reverted back to the previous approach of skipping files larger than 15 GB. 待完全支持 100 GB 大小的文件迁移到 Office 365 时,我们将发布通知。Support for 100 GB files will be announced once they are fully supported for migrations into Office 365.
    • 虽然,当从不存在的源目录运行迁移时,传输过程会正确地失败且用户日志中记录一行黄色信息。When running a migration from a non-existent source directory, the transfer would fail appropriately and the user log would have a yellow row in it. 但是,用户日志中该行记录有时会没有任何错误消息。However, this row in the user log would sometimes contain no error message. 已修复此问题。现在,该行中会包含相应错误消息,描述不存在的源目录的详细信息。This has been fixed so that a proper error message is included detailing that the source directory does not exist.
    • 在迁移到 Office 365 的过程中,可能出现某一文件可以正确上传,但无法提交处理其同批次其他文件的情况。During a migration into Office 365, while a file may be uploaded properly, its batch may fail to be submitted for processing. 这种情况下,该文件会在 UI 中显示为“失败”,但用户日志却不会记录任何显示该文件失败情况的条目。In these cases, the UI would show the file as failed, but the user log would not contain any entries showing that the file failed. 已修复此问题,方法是通过在(批处理)迁移工作从传输失败到提交的整个过程中,确保每个文件都存在用户日志。This has been fixed by ensuring that there always exists a user log entry per file when a migration job (batch) within a transfer fails to submit.
    • 现在,在“迁移管理器”表中,如果因为源帐户或目标帐户不支持某文件而导致跳过,或者不允许下载某文件,将会显示为失败而不是常规增量跳过。In the Migration Manager table, if there are skips because the file is unsupported on the source or destination, or if we are not allowed to download the file, then it will now show up as a failure and not as a regular incremental skip. 现在,除上述不受支持文件问题外所有步骤均已成功的事务,会以状态代码 227 - “某些文件不受支持”结尾,且在“迁移管理器”中的相应行将显示为黄色。Transactions that were mostly successful but only had these unsupported file issues, will end with status code 227 "Some files are unsupported" and the row will appear yellow in the Migration Manager.
  • 新增功能New features
    • 现在,在“帐户页面”上的“管理员面板”中,用户可以批量向其帐户添加管理员。On the Account Page, in the Admin Panel, a user is now able to add managers to their account in bulk. 用户可以输入多个电子邮件地址(用逗号隔开)作为帐户管理员。The user can enter a list of comma-separated email addresses to be added as account managers.

前端 v1.16.2(2020 年 6 月 12 日)Frontend v1.16.2 (June 12, 2020)

  • 现在,“迁移管理器”表中每行包含“信息”图标,这样,用户便可以更直观地知道点击此图标即可获取该行的更多信息。The Migration Manager table now includes an "information" icon in each row to make it more intuitive for users to know that additional information on the row can be viewed by clicking on that icon. 点击此图标将打开“传输摘要”侧面板。This action will open the Transfer Summary side panel.
  • 在“迁移管理器”中,打开表格中给定条目的传输摘要”侧面板时,侧面板中的“传输日志”将在初始加载后大约 10 秒钟后清空。In the Migration Manager, when opening the Transfer Summary side panel for a given entry in the table, the Transfer Logs table within the side panel would empty itself about 10 seconds after its initial load. 已修复此问题。现在,当有新数据时,“传输日志”表会保持可见且将新数据更新进表中。This has been fixed now and the Transfer Logs table should remain visible and will be updated with new data as it becomes available.
  • 修复“迁移管理器”屏幕问题。Fixing a Migration Manager screen issue. 当用户不再将鼠标焦点置于侧面板上时,面板将关闭。When the user no longer has the mouse focus on the side panel, the panel will close.
  • 修复连接器实际存在时Fixing the incorrect display of "Connectors don't exist anymore!" 错误显示“连接器不存在”。when in fact the connectors do exist.

后端 v1.16.4(2020 年 6 月 3 日)Backend v1.16.4 (June 3, 2020)

全新后端版本,提供了多项稳定性改进。A new backend release with some stability improvements. 由于使用率不足并希望专注于我们的产品,我们计划将 FTP、SFTP 和 WebDAV 连接器设置为专用。We are setting FTP, SFTP, and WebDAV connectors as private due to lack of usage and to focus our product.

  • 某些用户在查看“传输用户日志和扫描报告”时遇到问题。Some users were having problems viewing transfers user logs and scan reports. 有时,会以中间格式传送文件。The files were sometimes being delivered in an intermediate format. 已修复此问题,方法是确保在传送给用户前完全处理文件。This has been fixed by ensuring the files are completely processed before being delivered to users.
  • 现在,FTP、SFTP 和 WebDAV 连接器被标记为“专用”。The FTP, SFTP, and WebDAV connectors are marked as private. 因此,用户将无法再对这些类型的连接器进行新的授权。So users will no longer be able to authorize new connectors of those types. 2020 年 7 月 1 日前,可继续使用现有 FTP、SFTP 和 WebDav 连接器。Existing FTP, SFTP and WebDav connectors will continue to work until July 1, 2020. 对于这一调整,我们已通过电子邮件通知现有用户。Current users have been notified regarding this via email.

前端 v1.16.1.1(2020 年 6 月 1 日)Frontend v1.16.1.1 (June 1, 2020)

此次发布的前端版本重点改进了应用程序针对键盘和屏幕阅读器用户的辅助功能。This frontend release focuses on improving accessibility to our application for keyboard and screen reader users.

  • 删除了 UI 中创建(旧)Mover 帐户的选项。The option to create a (legacy) Mover account has been removed from the UI. 也就是说,用户现在需要通过“使用 Microsoft 帐户登录”功能进行登录。That is, users will now be required to use the "Sign In with Microsoft Account" feature instead. 以后将不再支持旧的 Mover 帐户。In the future, legacy Mover accounts will not be supported anymore.
  • 改进了应用程序中针对键盘和屏幕阅读器用户的辅助功能。Improved accessibility in the app for keyboard and screen reader users.
    • 现在,键盘用户可以使用 Tab 键以及向上、向下、向左和向右键,在“迁移管理器”中导航“迁移操作”下拉菜单中的所有项。Keyboard users will be able to navigate through all Migration Actions dropdown menu Items in the Migration Manager using the tab key, and the up, down, left and right arrow keys. 他们将能够导航到先前无法使用键盘导航到的菜单项,例如用于选择要在表格中显示的列以及显示顺序的“自定义”和“重新排序”列子菜单。They will be able to navigate to previously not keyboard-accessible menu items such as the Customize and Reorder columns submenus that allows them to select which columns to display on the table and in what order. 此外,屏幕阅读器用户在与“迁移操作”下拉菜单交互时将得到更好的提示。In addition to this, screen reader users will get better prompts when interacting with the Migration Actions dropdown menu.
    • 现在,键盘用户能够导航“迁移管理器”表。Keyboard users will now be able to navigate the Migration Manager table. 他们可以对表格进行排序,打开行的“传输摘要”侧面板,并应用标记筛选器。They will be able to sort the table, open the Transfer Summary side panel for rows, and apply tag filters. 与表格交互时,屏幕阅读器用户可获得更出色的体验,包括正确的 ARIA 标签和可对表格中元素执行的操作的说明。Screen reader users will have a much improved experience when interacting with the table, including proper ARIA labels and descriptions for actions they can take on elements on the table.
    • 在“传输向导”中,当选择“授权新连接器”(源或目标)时,现在可使用键盘访问“连接器类型选取器”。In the Transfer Wizard, when selecting Authorize New Connector (either source or destination), the Connector Type Picker is now accessible using the keyboard. 每个连接器类型上的“授权”按钮现在都有增强的 ARIA 标签,可更好地通知屏幕阅读器用户该按钮所执行的操作。The Authorize buttons on each connector type now have enhanced ARIA labels that will better inform screen-reader users what the button does.
    • 在“传输向导”屏幕上,连接器选取器(源和目标)在某些屏幕尺寸下,显示的某些连接器类型或连接器名称会被截断。In the Transfer Wizard screen, the connector picker (both source and destination) would show some connector types or connector names truncated on some screen sizes. 已为这些项目添加了工具提示,现在用户可以查看完整名称,而不只是截断的版本。Tool tips have been added on these items so now users will be able to view the names in full and not just the truncated version.
    • 在“传输向导”屏幕上,改进了“管理/连接”下拉列表。现在,讲述人将朗读正确按钮的正确文字。In the Transfer Wizard screen, the Manage/Connect drop down has been improved so the Narrator says the proper text for the correct button.
    • 现在,在“迁移管理器”屏幕上,使用 Tag 键即可将焦点导航到“信息”图标,并会自动显示筛选器的帮助程序工具提示。In the Migration Manager screen, the helper tool tip for Filters will now be automatically be shown when focusing into the "information" icon, which is now accessible by tabbing into it.
    • 最终用户将可以在“转移向导”中(连接到单用户连接器时)和“迁移管理器”中(编辑特定计划的源或目标时)导航进入和退出“文件选取器”。End users will be able to navigate into and out of the File Picker both in the Transfer Wizard (when connecting to a single user connector) and in the Migration Manager (when editing source or destination on a specific schedule).

后端 v1.16.3.1(2020 年 5 月 29 日)Backend v1.16.3.1 (May 29, 2020)

此后端版本部署不会对客户产生任何影响。A backend release deploy that should have no impact on customers.

后端 v1.16.2(2020 年 5 月 28 日)Backend v1.16.2 (May 28, 2020)

该 Mover 后端新版本,包含令人兴奋的预览版新功能(Box 笔记到 OneNote 笔记本的转换功能),以及对客户问题和稳定性的修复。New release of our Mover backend that includes an exciting new feature for preview (Box Notes to OneNote notebooks conversion) as well as a fix to a customer issue and stability fixes.

  • 新增对从 Box 笔记转换为 OneNote 笔记本的支持。Support added for converting Box Notes to OneNote notebooks. 如果从 Box 迁移到 OneDrive 消费者版,订阅 OneDrive for Business(单用户)或 Office 365 的用户可以将 Box 笔记转换为 OneNote 笔记本。Migrations from Box to OneDrive Consumer, OneDrive for Business (Single User) or Office 365 will be able to convert Box Notes to OneNote notebooks. 此功能现在处于公共预览阶段,客户将需要支持协助才能启用。This feature is now in public preview and will require support assistance to enable it for customers.
  • 在传输过程中,如果已在目标中存在(且已在源中更改的)某项的更新第一次尝试传输时失败,则后续尝试将会一直失败,并出现不可预知的错误。During a transfer, if an update of an item that already existed in the destination (and was changed in the source) failed on its first attempt, subsequent attempts will always fail with unpredictable errors. 已解决此问题。现在,后续(内部)尝试传输上述文件可以正常完成,并有可能成功完成。This has been addressed and subsequent (internal) attempts on these cases are done properly now and will have a chance of completing successfully.
  • 部分用户在“迁移管理器”表中遇到了这样的问题:某些实际上已运行的计划有时会多次显示为“未运行”状态。Some users were experiencing an issue in which the Migration Manager table would show some schedules with status "Not Run" when they were indeed run, sometimes multiple times. 已纠正此问题,将不会再发生此种情况。This has been corrected and will not happen going forward. 修复了存在问题的计划,现在可正确显示状态。Problematic schedules have been fixed to reflect the proper status.

后端 v1.16.1(2020 年 5 月 25 日)Backend v1.16.1 (May 25, 2020)

此后端版本,提供了多项稳定性改进。Backend release with stability improvements. 虽然,此版本中没有面向客户的更改。There are no customer facing changes. 但是,将有助于清除迁移作业监控服务中的积压工作。But this will help clear some backlogs in our migration job monitoring service.

后端 v1.15.11(2020 年 5 月 14 日)Backend v1.15.11 (May 14, 2020)

此后端版本改进了某些用户体验。Backend release improving experience to some of our users.

  • 普通规模迁移的“迁移管理器”表的填充速度将更快,同时,大型迁移(数千名用户)的相应速度也会得到显著提升。The Migration Manager table will get populated a bit faster for the average migration, while large migrations (1000s of users) will see a considerable speed improvement.
  • 在“迁移管理器”概述中,包含已扫描/迁移过很多次的很多用户的某些迁移有时会无法填充表。In the Migration Manager overview, some migrations with many users that have been scanned/migrated a large number o times would sometimes fail to populate the table. 已通过优化迁移的填充方式修复了此问题,以便提高性能。This has been fixed by optimizing how migrations get populated in order to increase performance.

前端 v1.15.4(2020 年 5 月 13 日)Frontend v1.15.4 (May 13, 2020)

大型前端版本,对用户体验几乎没有影响,主要为库升级。A large frontend release, with little UX impact, but library upgrades.

  • 更新 Fabric UI 后对 UI 进行了细微更改。Minor UI changes from updating Fabric UI.

后端 v1.15.10(2020 年 5 月 12 日)Backend v1.15.10 (May 12, 2020)

此后端版本改进了某些用户体验。Backend release to improve experience to some of our users.

  • 下载 zip 格式的用户日志时,每个日志的文件名都包括对源和目标目录的引用,但却不包含和用户更为相关的信息。When Downloading User Logs in zip format, the file name for each log includes a reference to the source and destination directories, but not of more relevant information to the user. 现在,通过将各文件名称的结构更改为:{endDate}_{sourcePath}_{txid}.moverlog.{extension},已改进此问题。This is now improved by changing the structure of individual file names to be: {endDate}_{sourcePath}_{txid}.moverlog.{extension}. 这样,当对文件进行分类时,文件名称会以事务结束日期作为前缀,从而方便用户操作。This makes the files behave better when sorting them as they are prefixed by the transaction end date. 此外,源路径已清理为仅显示更相关的部分。As well, the source path is now cleaned up to only show more relevant parts. 不再包含对目标目录的引用,因为当已包含源目录时,该引用往往会不相关。Reference to the destination directory is not included anymore as it tends to be irrelevant when the source directory is already included.
  • 在“迁移管理器”视图中复制计划时,某些计划会失败,出现“未能复制N计划”的提示,其中N是失败计划的数量。When duplicating a schedule in the Migration Manager view, certain schedules were failing with "Failed to duplicate N schedules", where N is the number of failed schedules. 已修复此问题,现在用户可以复制所有计划。This is now fixed and the user is able to duplicate all schedules.

后端 v1.15.9(2020 年 5 月 7 日)Backend v1.15.9 (May 7, 2020)

此后端版本旨在解决客户关心的 0 字节文件迁移到 Office 365 的问题,同时新增了多项增强功能,虽然目前暂时不会对用户产生影响,但可在未来提升最终用户的体验。A backend release went out addressing a customer concern about 0-byte files into Office 365, and with many more enhancements that don't currently have a direct user impact but will enable future improvements for our end users.

  • 进入 Office 365 的迁移不再跳过 0 字节的文件,所有文件都将成功传输到目标。Migrations going into Office 365 will not skip 0-byte file anymore and will be successfully transferred to the destination. 但是,进入 OneDrive 消费者版或 OneDrive for Business 的迁移(单用户)仍将跳过 0 字节文件,因为这些服务仍然限制非管理员传输创建 0 字节的文件。However, migrations going into OneDrive Consumer or OneDrive for Business (Single User) will still skip 0-byte files as those services still restrict non-administrator transfers from creating zero-byte files.

前端 v1.15.3(2020 年 5 月 1 日)Frontend v1.15.3 (May 1, 2020)

此前端部署版本可以加速批量操作。A frontend deployment to speed up bulk operation.

  • 如果选择了大量用户,在“迁移管理器”中对用户执行批量操作时速度会很慢。Doing bulk operations on users in the Migration Manager would be slow when a lot of users were selected. 通过使用新版本的 Mover API,相关批量操作的速度已得到提升。Speed improvements to these operations have been introduced by using a new version of the Mover API.

前端 v1.15.2.1(2020 年 4 月 29 日)Frontend v1.15.2.1 (April 29, 2020)

小型部署版本,旨在修复一处前端问题。A small deploy fixing a frontend issue. 此外,还测试将部分基础结构迁移到 Azure。But also testing part of our infrastructure move to Azure.

  • 当用户尝试从“文件选取器”为连接器创建文件夹时,会显示“未知错误”。When trying to create a folder from the File Picker view for a connector, "Unknown error" is displayed to the user. 已修复此问题,现在可正常创建文件夹。This is now fixed and folder creation is working properly again.

后端 v1.15.8.1(2020 年 4 月 28 日)Backend v1.15.8.1 (April 28, 2020)

此版本旨在解决客户在迁移过程中遇到的问题。Release to address customer issues with migrations.

  • 下载 zip 格式的用户日志时,如果源和目标目录过长(其)系统无法打开(已下载的)zip 文件,因为(zip 文件中的)文件名长度限制为 255 个字符。When Downloading User Logs in zip format, if the source and destination directories are too long (their) system cannot open the (downloaded) zip file because there is a filename length limitation of 255 characters (in zip files). 已修复此问题,现在,(即使源目录和目标目录很长)也可以下载并打开 zip 文件。This is now fixed, they can download and open zip file (even when source and destination directories are very long).
  • 完成对迁移/计划的扫描后,将在“迁移管理器” UI中生成可供下载的扫描程序报告。When scanning is done on a migration/schedule the scanner reports are generated and available for download in the Migration Manager UI. 生成的报告中包括通用路径报告,该报告在页眉末尾缺少一个新行字符,从而导致行格式设置与标题同一行中的第一条公共路径记录格式不正确。The generated reports include a Common Path report which was missing a new line character at the end of the headers, causing a malformed row formatting with the first common path record in the same row as the header. 已修复此问题,以确保以正确的 CSV 格式提供该报告并确保其可读。A fix has been implemented to ensure the report is presented in proper CSV format and is readable.

后端 v1.15.7(2020 年 4 月 23 日)Backend v1.15.7 (April 23, 2020)

此后端版本旨在满足客户在迁移方面的需求。Backend release to address a customer migration.

  • 在 Dropbox 中列出包含文件夹时,不再与任何人共享的“团队文件夹”会导致传输失败。In Dropbox, Team Folders that are no longer shared with anyone would make a transfer fail when listing the containing folder. 已修复此问题,现在可正确处理未共享的“团队文件夹”。This has now been fixed and unshared Team Folders are handled properly.

后端 v1.15.6(2020 年 4 月 23 日)Backend v1.15.6 (April 23,2020)

此后端版本提供多处客户修复。Backend release with customer fixes.

  • 现在,管理员可以通过输入自己的密码而不是托管用户的密码来删除托管用户的帐户。Managers are now able to delete the account of a managed user by entering their own password instead of the managed user's password.
  • 新增对从 Dropbox(管理员)连接器遍历和传输已存档“团队文件夹”的支持。Add support to traverse and transfer archived Team Folders out of the Dropbox (Administrator) connector.

前端 v1.15.1(2020 年 4 月 21 日)Frontend v1.15.1 (April 21, 2020)

  • 现在,“连接器授权”窗口(用户可在其中选择要授权的连接器),(在手机、平板和台式机上)均能显示完整的连接器名称,而不会截断它们。Connector Authorization window where the user selects what connector to authorize now displays the full connector names without truncating them (on mobile phones, tablets and desktop).

后端 1.15.5.1(2020 年 4 月 21 日)Backend 1.15.5.1 (April 21, 2020)

此后端版本包含多项客户修复以及对更多 Dropbox 和 Google Drive (G Suite) 使用场景的支持。A backend release that includes customer fixes, expanding support for Dropbox and Google Drive (G Suite) scenarios.

  • 修复前,在 Dropbox 中,没有所有者的共享文件夹会在包含文件夹中导致传输失败。In Dropbox, shared folders without an owner were making transfers fail at the containing folder. 现在,已修复此问题,方法为让传输仅遍历这些存在问题的文件夹以外的所有内容(而非其包含文件夹)。This is now fixed by letting the transfers traverse everything except those problematic folders (as opposed to their containing folders). 共享文件夹没有所有者的原因可以是,原始所有者不再是 Dropbox 商业版帐户。Shared folders can have no owner because the original owner is no longer part of the Dropbox business account. 可通过用户日志中的对应条目,正确告知用户。Users are properly informed of this through the corresponding entry in the user log.
  • 在 Dropbox 中列出包含文件夹时,已存档的“团队文件夹”会导致传输失败。In Dropbox, archived Team Folders would make a transfer fail when listing the containing folder. 已修复此问题,现在可正确处理已存档的“团队文件夹”。This has now been fixed and archived Team Folders are handled properly.
  • 之前,从 Google Drive 或 G Suite(管理员)传输 Google 文档时,大小限制为 10MB。Transferring Google Documents out of Google Drive or G Suite (Admin) was previously restricted to documents at most 10MB in size. 此限制已不存在,用户可以将更大的 Google 文档导出到他们的 Office 365 帐户中。This restriction is no longer in place and users should be able to export larger Google Documents into their Office 365 counterparts.
  • 用户无法在单用户连接器的根位置创建文件夹。There was an issue where users could not create folders at the root of a Single User connector. 已修复此问题,用户现在可以在单用户连接器的根位置创建文件夹。This has been fixed and users should be able to create folders at the root of Single User connectors now.
  • 用户删除帐户后,连接器不会立即被删除。Connectors were not being deleted immediately when the user deleted their account. 而只能在“帐户保留策略”监视器清除连接器时,才会被删除。Instead, connectors would get deleted when the account retention policy monitor would clean them up. 已修复此问题,现在连接器会被立即删除。This has been changed so that connectors are deleted right away.

后端 v1.15.4(2020 年 4 月 9 日)Backend v1.15.4 (April 9, 2020)

此后端版本旨在解决处理 Dropbox 团队文件夹的问题。Backend release to address handling of Dropbox Team folders. 目前,我们正在加紧工作以配合“团队文件夹”的最新相关功能,但此版本已紧急修复阻止客户处理“团队文件夹”的问题。This is a work in progress to catch up with the latest features related to Team Folders, but it fixes urgent issues to unblock customers.

  • 修复了 Dropbox 团队文件夹的处理问题,以及子文件夹中的独有权限。Fixed handling of Dropbox Team Folders and unique permissions within subfolders. “团队文件夹”将列在 Dropbox(管理员)连接器的根位置,以及每个拥有访问权限的用户的下方。Team Folders will be listed on the root of the Dropbox (Admin) connector, as well as under each user that has access to them. 但是,为避免重复数据,将不会传输列在用户下方的“团队文件夹”。However, to prevent data duplication, Team Folders will NOT be transferred if they are listed under a user. 仅当直接从 Dropbox(管理员)连接器的根目录遍历“团队文件夹”时,才会进行传输。Team Folders are only transferred when traversing them directly from the root of the Dropbox (Admin) connector. 此外,现已能够正确导出“团队文件夹”及其子文件夹的权限,包括限制权限。Also, permissions for Team Folders and its subfolders are properly exported now, including restrictive permissions.

后端 v1.15.3(2020 年 4 月 8 日)Backend v1.15.3 (April 8, 2020)

小型关键后端版本,用于支持从 G Suite(管理员)进行迁移。Small but critical backend release for migrations out of G Suite (Admin). 请仔细阅读影响声明。Please read the impact statement carefully.

  • 修复了特定情况下从 G Suite(管理员)迁移时最后会出现重复数据的问题。Fixes a specific case in migrations from G Suite (Admin) that would end up in data duplication. 该问题同文件夹有关,即当“所有者”根目录中的文件夹共享给其他用户(“访客”),而“访客”没有将共享文件夹装载到根文件夹,而是树中更深层的位置。The case relates to folders in an "owner" root that were shared with other users ("guest") and "guest" mounted the folder not in their root folder but somewhere deeper in their tree. 这种情况下,传输不会遵循“用户优先级”列表,从而导致同时为“所有者”和“访客”传输同一文件夹。In this case, the transfer would not obey the user priority list resulting in the folder being transferred for both "owner" and "guest". 此问题于 2019 年 3 月 1 日回归,现已被修复。This regression was introduced on March 1, 2019 and is fixed now. 全面影响仍在评估中。Full impact is still being assessed. 受影响的迁移无需重新运行“Google 预扫描”。现在,重新运行传输时会正确跳过存在问题的文件夹。There is no need to re-run Google Prescans for affected migrations; instead, re-running the transfers will now skip the folder in question appropriately. 受影响的客户可(根据标识)手动删除重复数据作为补救措施。Remediation for affected customers is to manually removed the duplicated data (upon identification).

后端 v1.15.1(2020 年 4 月 2 日)Backend v1.15.1 (April 2, 2020)

此后端版本包括 bug 修复和稳定性改进。A backend release that includes bug fix and stability improvements.

  • 通过“使用 Microsoft 帐户登录”功能新建 Mover 帐户的用户将拥有相应权限,可运行所有类型的传输(某些新用户可能不允许运行部分传输)。Users creating a new Mover account using the Sign in with Microsoft account feature will have appropriate access to running all types of transfers (some transfers appeared as not allowed to some new users).

后端和前端 v1.15.0(2020 年 4 月 1 日)Backend & Frontend v1.15.0 (April 1, 2020)

  • 应用顶部导航栏中将显示新的“支持”链接。A new "Support" link will be displayed in the top navigation bar in the app. 此链接将为用户指向新的支持系统。This link will point users to the new support system. 应用中的对讲机小组件将被禁用。The intercom widget will be disabled in the application.
  • 拥有 Microsoft 帐户的全新用户和现有用户可以使用 Microsoft 帐户登录 Mover 应用。Brand new users and current users with a Microsoft account will be able to sign into the Mover app with their Microsoft account. 此功能支持工作/学校以及个人帐户。This includes work/school and personal accounts. 将继续支持使用现有 Mover 帐户登录。Existing Mover accounts will continue to be supported.

后端 v1.14.1.1(2020 年 3 月 31 日)Backend v1.14.1.1 (March 31, 2020)

  • 修复了时间久远的迁移其权限映射会阻止应用加载的问题。Fixed an issue with very old migrations with permission mappings that would prevent the app from loading. 已修复对上述旧迁移的支持。Support for these old migrations have been fixed.
  • 仅针对将 Box 笔记转换为 Word 文档的传输。For transfers that convert Box Notes to Word Documents only. 现在,Word Docx 文档不支持的 Box 笔记图像将转换为 Word Docx 可接受的格式,并且可在文档中正确显示。Box notes images that are not supported by Word Docx will now be converted to a format acceptable by Word Docx and will be displayed properly in the document.
  • Mover 应用加载后,“迁移管理器”将默认转到最新迁移而不是最旧的迁移(此问题在上一版本中回归)。When the Mover app is loaded, the Migration Manager will default to the latest Migration instead of oldest Migration (this was a regression from a previous release).
  • 这将在用户/计划聚合的所有迁移和扫描报告中添加额外一列,用于计划标记。This adds an extra column for schedule tags in all migration and scan reports that aggregate by user/schedule.

后端和前端 v1.14.0(2020 年 3 月 26 日)Backend & Frontend v1.14.0 (March 26,2020)

此版本部署结合后端和前端,修复了多处报告问题,并禁用对讲机小组件。A combined backend/frontend deploy with some fixes to reports and disabling the Intercom widget.

  • “迁移报告”中将显示准确的文件和字节统计信息(包括成功、失败、已跳过和不受支持各大类)。Accurate stats for files and bytes (success, failure, skipped, unsupported) will be displayed in the Migration Report. 报告中所显示的统计信息将和“迁移管理器” UI 中显示的信息一致。There will be no discrepancy for the stats shown in the report versus what's displayed in the Migration Manager UI.
  • 迁移中包含超大权限映射的用户不会再遇到“迁移管理器” UI 卡顿的问题。The Migration Manager UI will not be stuck for users that have migrations with very large permission mappings. 相反,应用将根据需要加载权限映射(在编辑时)。Instead, the app will load permission mappings as needed (when editing them). 如果迁移的权限映射非常大,则应用将不会显示编辑器。If a migration has an excessively large permission mapping, the app will not display the editor. 用户可以将权限映射下载为 CSV,并在编辑后重新上传 CSV。Instead, the user will be able to download the permission mapping as CSV, edit and then re-upload the CSV.
  • 应用中的对讲机小组件将被禁用。The intercom widget will be disabled in the application.

后端 v1.13.10(2020 年 3 月 24 日)Backend v1.13.10 (March 24, 2020)

此后端版本提供新的功能和潜在性能修复。A backend release with a new feature and potential performance fix.

  • 现在,Dropbox “团队文件夹”中项目的独有权限将迁移到目标。Unique permissions from items within a Dropbox Team Folder will now be moved to the destination.

后端 v1.13.9(2020 年 3 月 20 日)Backend v1.13.9 (March 20, 2020)

此后端版本旨在协助处理增长的负载。Backend release to assist with the increased loads.

  • 修复前,“取消传输”操作可能要花很长时间才能生效。There were cases in which transfer cancellations were taking a long time to take effect. 现在,通过确保缩短这一过程,已修复此问题。This fixes the issue by ensuring they happen faster.

后端 v1.13.7(2020 年 3 月 17 日)Backend v1.13.7 (March 17, 2020)

此后端版本中的更改,可帮助我们确定客户问题的根本原因。Backend release with changes to help us determine the root cause for customer issues.

  • 现在,从 Egnyte 根目录或“专用”目录迁移不会导致验证错误,并且允许用户从这些文件夹迁移文件。Transfers from the Egnyte root directory or the Private directory will not incur in a validation error and the user will be allowed to migrate out of those folders.

后端 v1.13.5(2020 年 3 月 11 日)Backend v1.13.5 (March 11, 2020)

  • 此版本发布前,当用户对计划运行扫描后,有时会延迟很久才会生成扫描报告(包含长路径、通和路径、大型文件、文件扩展名和迁移扫描摘要报告)。After a user runs a scan on a schedule, the scan reports (Long Paths, Common Paths, Large Files, Files Extension, Migration Scan Summary Report) were being generated sometimes with a pretty long delay. 现已修复此问题。This is being fixed now. 此外,“迁移管理器中”的“迁移操作”菜单将在扫描报告完成生成后实时更新,并且会正确显示“扫描报告”(zip 文件)菜单项的计数。Also, the Migration Actions menu in the Migration Manager will update in real time when the scan reports finish generating and the proper count will be shown for the Scan Reports (zip file) menu item.

后端 v1.13.4(2020 年 3 月 9 日)Backend v1.13.4 (March 9, 2020)

  • 用户可更快地在“迁移管理器”中初次加载计划表以及刷新表中的数据。User will see improved speeds both when initially loading the schedules table in the Migration Manager, and when refreshing the data in it. 现在,大型迁移(超过 10 万个计划且每个计划运行多次)的表格可在 60 秒内完成加载。The table should load in under 60 seconds now for huge migrations (100K+ schedules with multiple runs per schedule). 最重要的是,用户不会看到由于大小原因无法在 UI 中加载的表格(可能由于网络问题等其他常规问题而失败)。Most importantly, users should not see the table failing to load in the UI due to size (may fail due to other normal issues like network problems). 普通规模的迁移将会立即完成加载。Average migrations will load instantaneously. 我们的终极目标是改进用户体验,实现所有规模的迁移都能立即加载。Ultimate goal is to improve UX so that the table would load instantaneously for migrations of all sizes.