Logging in before the migration completes

Users should definitely NEVER log in before the migration has completed.  Usually there will be two reboots before they should log on to their device.  If the user logs in BEFORE the migration completes, they are almost certainly going to break the migration process - specifically around re-permissioning their Windows User Profile.  This is because as soon as they log in, they will lock their registry as it will be in use, and the Migration Agent will not be able to run through and re-permission the relevant keys by updating the ACLs.

Project Communication

Your project should include clear and obvious instruction advising users not to attempt to log in during the migration event, however we all know that with all the will in the world, and the repeated comms that are sent out, not all users will read and follow the instructions.

Discourage Logging In

Migration in Progress image

On the Startup tab of your Runbooks you are able to configure a Migration in Progress image.  Whilst this is optional, we strongly urge customer to use this option.  

You can choose your own custom image to match your corporate branding, or we have one available that you can utilise.

Migration in progress.  Please wait…

Right Click on the image below and save to your PSP Server.

Migration in Progress - LockScreen image

This is what a user will see during the migration event:

Legal Notice Caption & Legal Notice Text

Need more? Not convinced that users still won't attempt to log in?  Over and above the LockScreen Image, as an additional  “belt & braces" option, we would also recommend an extra gate for users to pass through so that they do not attempt to log in during the migration event.

This is configured via a simple pair of registry keys:

Configure Legal Notice Caption

You can achieve this with a Startup migration Command Package to Run.

Step 1

Create a file called cmdline.cmd and add the following code (or edit/choose your own to suit your needs)

reg add "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System" /v legalnoticecaption /t REG_SZ /d "PowerSyncPro - MIGRATION IN PROGRESS" /f /reg:64
reg add "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System" /v legalnoticetext /t REG_SZ /d "Your migration has not completed yet.  Are you sure you still wish to sign in?  Continuing beyond this point could cause your migration to fatally fail" /f /reg:64

Step 2

Add this single file to a compress/zip file like Add_Legal_Notice.zip

Step 3

Add this file to your migration Runbook on the Startup tab.

Step 4

Remove Legal Notice

Create another file called cmdline.cmd and add the following lines:

reg add "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System" /v legalnoticecaption /t REG_SZ /d "" /f /reg:64
reg add "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System" /v legalnoticetext /t REG_SZ /d "" /f /reg:64

Step 5

Add this single file to a compress/zip file like Remove_Legal_Notice.zip

Step 6

Add this file to your migration Runbook on the Completion tab.

Block Local Log In

In future releases of PowerSyncPro Migration Agent we will be adding capability to fully block scoped users from being able to log in locally until the migration completes (but still allow local Administrators to log in to troubleshoot).