Azure AD Conect - custom install problem - Specified cast is not valid

Question

Hi,

I'm faced with migfration of Azure AD Connect from one server to another.
I have exported settings on one server, copied to another and during custom install I recieve an error like below:

Invalid Cast Exception
Specified cast is not valid

AAD Connect version - 1.6.13 - from this version od AD connect settings we're exported and to this version I try to import.

Log entries:
[11:59:14.875] [ 12] [INFO ] SyncEngineSetupViewModel: Validating sync engine settings.
[11:59:14.875] [ 13] [ERROR] A terminating unhandled exception occurred.
[11:59:14.875] [ 12] [INFO ] MigrateSynchronizationPolicy: Loading persisted settings (0).
Exception Data (Raw): System.AggregateException: One or more errors occurred. ---> System.InvalidCastException: Specified cast is not valid.
at Microsoft.Online.Deployment.OneADWizard.UI.Controls.SyncEngine.SyncEngineSetupViewModel.ValidateSettings(Boolean verifyDataDiskSpace)
at Microsoft.Online.Deployment.OneADWizard.UI.WizardPages.InstallSyncEnginePageViewModel.StartNewInstallation(Boolean skipSyncEngineInstall)
at System.Threading.Tasks.Task.Execute()
--- End of inner exception stack trace ---
---> (Inner Exception #0) System.InvalidCastException: Specified cast is not valid.
at Microsoft.Online.Deployment.OneADWizard.UI.Controls.SyncEngine.SyncEngineSetupViewModel.ValidateSettings(Boolean verifyDataDiskSpace)
at Microsoft.Online.Deployment.OneADWizard.UI.WizardPages.InstallSyncEnginePageViewModel.StartNewInstallation(Boolean skipSyncEngineInstall)
at System.Threading.Tasks.Task.Execute()<---

Answer 1

Hi Adam,

How are you migrating the AD connect form one server to another. the recommended practice is to put the new server in staging mode and switch over. Its pretty straight forward.

Please refer this article for step-by-step. https://practical365.com/migrating-azure-ad-connect-new-server/

Answer 2

HI Adam, what is the version of your new AD connect. is it 2.0.8.0. - looks this installer have some issues with config import .

The same issue was solved in version 2.0.10.0 . Please give a try.

Regards,
Dev