AAD Join Error Code

Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic

   Hello all,
We've been trying out ForensiT for the first time to see if it is something we'd like to proceed with buying but seem to be running into a issue where the provisioning package doesn't want to apply when moving form local AD to Azure AD.  Leaving local AD works just fine but when joining to Azure AD nothing seems to happen, I attempted to copy over the ppkg and run it myself as SYSTEM to see what would happen and we do receive a error:

https://ibb.co/RThRbmh

I'm not sure entirely what might be causing it and was wondering if anyone else had encountered this?

Thanks!

Edited by atgfw - 03 Mar 2022 at 6:29pm

Author	Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic
atgfw Members Profile Send Private Message Find Members Posts Add to Buddy List Newbie Joined: 03 Mar 2022 Status: Offline Points: 2	Post Options Post Reply Quote atgfw Report Post Thanks(0) Quote Reply Topic: AAD Join Error Code Posted: 03 Mar 2022 at 6:28pm
	Hello all, We've been trying out ForensiT for the first time to see if it is something we'd like to proceed with buying but seem to be running into a issue where the provisioning package doesn't want to apply when moving form local AD to Azure AD. Leaving local AD works just fine but when joining to Azure AD nothing seems to happen, I attempted to copy over the ppkg and run it myself as SYSTEM to see what would happen and we do receive a error: https://ibb.co/RThRbmh I'm not sure entirely what might be causing it and was wondering if anyone else had encountered this? Thanks! Edited by atgfw - 03 Mar 2022 at 6:29pm

Support Members Profile Send Private Message Find Members Posts Add to Buddy List Moderator Group Joined: 09 Nov 2006 Location: United Kingdom Status: Offline Points: 1941	Post Options Post Reply Quote Support Report Post Thanks(0) Quote Reply Posted: 04 Mar 2022 at 9:49am
	Hi, To Troubleshoot the Provisioning Package you have created, my suggestion is that you run your Provisioning Package using the Install-ProvisioningPackage PowerShell Cmdlet. If you just run Install-ProvisioningPackage in PowerShell it will guide you through the process. Thanks, Support.