Fiddler is a third party debugging tool which records HTTPS traffic that we sometimes require for more in depth investigation.
Multi-Server (Web UI)
If you have more than one secondary server, refer to the Multiple secondary machines section first.
- Download Fiddler Classic from telerik.com
- When it’s open, go to Tools / Fiddler Options / HTTPS and ensure that ‘Decrypt HTTPS Traffic’ is ticked,
- Accept and install the certs per the prompts,
- Go back to the main window, and in the bottom-left, you will see “All Processes”, click this and change it to “Non Browser”,
- In CloudM Migrate, as this is a multi-server migration, you will need to set Proxy Type to Explicit, and the Address should be http://127.0.0.1:8888 or http://localhost:8888. Where 8888 is the default port on which Fiddler listens.
From here, reproduce the issue with Fiddler running. When the migration is complete or has failed, go back into Fiddler and click File / Save / Save All Sessions to then provide us with the resulting .SAZ file as an attachment. We also need the corresponding debug-level migration trace file, also.
Once you have collected your Fiddler trace, reset the above in CloudM Migrate (Proxy Type: Default and remove the proxy address).
- If you're migrating to Google Workspace and you get this error:
"Failed: User does not exist and has not been created (do you need to turn on Create Users?)"
With Fiddler running, it can sometimes interfere with connection to the Google Directory API. To work around this, you can disable 'Check Users' on page (2).
- If this doesn't appear to be working, or the migration is not working as expected, or you get the following error:
" Error executing action 'User Migration Starting' System.Runtime.Remoting.ServerException
The ServicePointManager does not support proxies with the https scheme."
It's more than likely that you've entered HTTPS instead of HTTP in the proxy address field.
Migration fails and License (Validity) is empty on connection checks - Make sure that Fiddler is running and clear Fiddler's cache (Tools>Clear WinINET cache)
Multiple secondary machines
If you have multiple secondary machines and can't pinpoint the machine migration is running on:
- Open CloudM Migrate Service Manager. It can be found in the Start menu or by entering the name in the Search field next to the Start menu icon.
- Under the Service tab, ensure that Run Primary Service and Run Secondary Service are both set to True. You can find both settings under the Services section dropdown (if they are not immediately displayed).
- Open the CloudM Migrate Self Hosted web application, and select Remote Connections.
- Stop the migration services listed.
- Run Fiddler on the Primary machine / server and run the migration.