Migration App UI v1.22.0 / Agent v3.22.0 Release Date: 4/27/2023
We will initially be enabling this feature by request to email@example.com. This feature allows you to schedule your migration job to run one time in the future.
From the Migration Job Details page, go to Advanced Options in the left column. Click on that to reveal the options. Click on Scheduler to access the configuration dialog.
Clicking On to Enable Scheduler reveals a calendar picker to select a date and time. Date and time selected must be in the future. Time slots are at :15 intervals, are presented in military time and reflect the clock on the host where the agent is installed. If no time is selected, time will default to 00:00.
In the Other Details (right column on the details page), Scheduler will display simply Disabled or Enabled.
When Scheduler has been enabled for a job, on the Migration Dashboard a clock icon will appear next to the status of the job. Hovering over the clock icon will display when the job is scheduled to run.
- Once a job has been scheduled, you may change the date and time to another point in the future.
- If both Scheduling and Unattended Mode are enabled, Unattended Mode will take precedence and the Scheduled job will not run.
- In the next iteration of this feature, Scheduling will allow for recurring job executions, which will replace Unattended Mode.
Folder Picker for the Source when Creating a New Migration Job
Initially, this feature will be enabled by request to firstname.lastname@example.org.
When creating a new migration job, users previously were required to manually enter both the source and destination paths in the dialog. Recently we implemented an improvement to this experience by offering a Folder Picker for the destination. With this release, we are now implementing the Folder Picker for the source.
In order for Migration App to have intelligence about the folder structure on the source, an initial high-level scan is required from the Agent. This can be done from the Migration Dashboard or from the Create New Migration dialog.
To initiate a scan of a connected Agent from the Migration Dashboard, under the context menu (3 dots), select Scan Source.
Next, you’ll be offered a dialog box displaying all the mapped drives connected to the host where the agent is installed. Select one or more and click Scan.
While the scan is in progress, it displays the status on the Agent details as Running.
Once the scan has finished, the completion time is displayed on the Agent details.
On the Create New Migration Job dialog, you can hover over the information icon and see when the source was last scanned.
Clicking Scan Source brings up details about all disks on the source, and allows you to rescan if desired, or initiate a scan if none had previously been run on any of the available disks.
Once a scan has been completed, on the main dialog you may click Select in the Source Folder Path field, which brings up a list of folders.
Next you can navigate down as many levels as desired through the folder structure.
After making a selection and clicking Select, you’ll be returned to the main dialog with the Source Folder Path prepopulated.
The maximum number of folders the Source Scan can accommodate is 500K. If the source contains more than 500K folders, the Source Scan will fail and you will be presented with an error message. In these cases, you must manually enter the Source Folder Path.
Domain Storage Limit Not Accurately Registered, Failing Migration Jobs
When a domain recently upgraded from a trial domain to a production domain, the scan was failing during the pre-check and would not allow the user to proceed with the migration. This has been resolved with this release.
Hard Disk Space Limiting Migration
Even after adding hard disk space of as much as 500GB, the Migration App was still getting degraded. The cloud dashboard showed as connected but the agent on the device was showing as not connected. Users would try to stop the service but were being presented with an error.
This has now been resolved.
Customers with Custom Domains Now to Access Migration App
Customers with custom (vanity) domains were previously directed to access Migration from their standard domains, which would then upload content that could be viewed in the custom domain. However, when we recently implemented a new SSO feature, it introduced an authentication conflict for Migration App. Customers with SSO enabled and custom domains would try to access Migration App from their standard domain, but were automatically redirected to the custom domain (where Migration App wasn’t accessible.)
Now users can access Migration App from either the standard or custom domain, however it is recommended that they always use the standard domain to run Migration App. From the custom domain, the user cannot register a new migration Agent.