AADC - Swing Migration - Ver 1.6.4 Endpoint 2 not enabled by default after import of json

%3CLINGO-SUB%20id%3D%22lingo-sub-2534464%22%20slang%3D%22en-US%22%3EAADC%20-%20Swing%20Migration%20-%20Ver%201.6.4%20Endpoint%202%20not%20enabled%20by%20default%20after%20import%20of%20json%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2534464%22%20slang%3D%22en-US%22%3EFolks%20bit%20of%20a%20strange%20one%20and%20maybe%20someone%20might%20be%20able%20to%20shed%20some%20light%20on%20this%20behaviour...%3CBR%20%2F%3E%26amp%3Bnbsp%3B%3CBR%20%2F%3EHave%20recently%20completed%20an%20AADC%20Swing%20Migration%20as%20original%20version%20was%20a%20quite%20an%20old%20version.%3CBR%20%2F%3EOriginal%20version%20AADC%201.1.882.0%20-(No%20export%20%2F%20import%20config%20option)%3CBR%20%2F%3E-%20Steps%20were%20%3A%3CBR%20%2F%3E%3CBR%20%2F%3E1%20-%20Start%20Install%20new%20version%20of%20AADC%201.6.4.0%20on%20new%20Win2019%3CBR%20%2F%3E%3CBR%20%2F%3E2%20-%20Copy%20migratesetting.ps1%20from%20New%20to%20%22old%20Server%22%3CBR%20%2F%3E%3CBR%20%2F%3E3%20-%20Run%20migratesettings.ps1%20script%20on%20old%20server%20and%20then%20import%20exported%20config%20into%20New%20AADC%3CBR%20%2F%3E%3CBR%20%2F%3E4%20-After%20checking%20which%20endpoint%20was%20in%20use%20on%20New%20AADC%20noticed%20it%20was%20set%20at%20Endpoint%20V1%20%2Chad%20to%20manually%20set%20it%20to%20V%202***%3CBR%20%2F%3E%3CBR%20%2F%3E5.Then%20exported%20the%20new%20config%20to%20Staging%20server%20and%20again%20AADC%20was%20set%20to%20V1%20after%20import%20of%20config%3CBR%20%2F%3E%26amp%3Bnbsp%3B%3CBR%20%2F%3EJust%20wondering%20if%20this%20is%20by%20design%20%3F%3CBR%20%2F%3E%26amp%3Bnbsp%3B%3CBR%20%2F%3ETks%20a%20mill%3CBR%20%2F%3E%26amp%3Bnbsp%3B%20%26amp%3Bnbsp%3B%26amp%3Bnbsp%3B%3CBR%20%2F%3E%26amp%3Bnbsp%3B%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-2534464%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAzure%20AD%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EIdentity%20Management%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Senior Member
Folks bit of a strange one and maybe someone might be able to shed some light on this behaviour...
 
Have recently completed an AADC Swing Migration as original version was a quite an old version.
Original version AADC 1.1.882.0 -(No export / import config option)
- Steps were :

1 - Start Install new version of AADC 1.6.4.0 on new Win2019

2 - Copy migratesetting.ps1 from New to "old Server"

3 - Run migratesettings.ps1 script on old server and then import exported config into New AADC

4 -After checking which endpoint was in use on New AADC noticed it was set at Endpoint V1 ,had to manually set it to V 2***

5.Then exported the new config to Staging server and again AADC was set to V1 after import of config
 
Just wondering if this is by design ?
 
Tks a mill
    
 
0 Replies