With the introduction of PDK.io 2.0, existing PDK.io 1.0 Cloud Nodes in Customer Accounts can be migrated to PDK.io 2.0, allowing the new features to be used with the Customer Account.
Currently, the migration process for Cloud Nodes to PDK.io 2.0 supports migrating single Cloud Nodes to a PDK.io 2.0 Customer Account.
Pre-Migration Process
Before a Cloud Node can be migrated to PDK.io 2.0, the Cloud Node must be on the most current firmware for the Cloud Node. A notification message will be displayed at the top of the Cloud Node Dashboard if a Cloud Node is not on the most current firmware.
As Cloud Nodes are updated in batches, tapping/clicking the Prioritize button ensures that the Cloud Node that needs to be migrated is prioritized for being updated.
Once a Cloud Node has been prioritized for an update, if you wish to remove the Cloud Node from the priority update queue, tapping/clicking on the 'Remove Prioritization' button on the notification message at the top of the Customer Dashboard will cancel the prioritized update, moving the update to normal priority.
Beginning the migration process
If a Cloud Node has the current firmware, the notification message at the top of the Customer Dashboard will display a message prompting you to tap/click for more information or to begin the update to PDK.io 2.0.
Tapping/clicking the 'Update' button on the notification message will begin the migration process.
If no issues that would interfere with the migration of the Cloud Node are detected, the message window will indicate this and prompt you to begin the update by tapping/clicking the Next button. If the 'Device Configuration' step fails, this is commonly due to non-Device Identity devices being present. For information regarding updating these devices, please refer to Converting Legacy Devices to Device Identity.
After tapping/clicking the 'Next' button, the Cloud Node will be ready to be staged for the migration. Tapping/clicking the 'Update System' button will 'Stage' the Customer Account, preliminarily converting the Cloud Node data to PDK.io 2.0.
After tapping/clicking the 'Update System' button, the update will begin, placing the Cloud Node into a 'Read-Only' State. This means no changes can be made by any users, despite being logged in from another computer or mobile device. The Cloud Node will function as normal during the update process.
Once the Cloud Node has been 'Staged' for migration, the Installation Partner can review the settings on the Cloud Node to confirm everything is correct before moving on to the next step.
While reviewing the Staged Cloud Node, a notification will appear at the top of the Customer Dashboard, allowing the Installation Partner to either revert the Cloud Node to a Legacy System or proceed with the migration by tapping/clicking the 'Transfer Registration' button.
After confirming the information on the Cloud Node and the Installation Partner is ready to migrate the Cloud Node to PDK.io 2.0, tap/click the 'Transfer Registration' button a final prompt regarding the migration will be displayed. Tap/click the 'Transfer Registration' button to synchronize the Staged data and complete the migration of the Cloud Node to PDK.io 2.0. Once completed, the Cloud Node will no longer be in the Customer Account where the Cloud Node was before the migration. Instead, it will be registered and synced in a new Customer Account with the old Cloud Node name.
Once completed, the Customer Account can be accessed in the same manner as a newly created PDK.io 2.0 Customer Account.
Comments
0 comments
Please sign in to leave a comment.