ForensiT Homepage
Forum Home Forum Home > ForensiT Support > Domain Migration
  New Posts New Posts RSS Feed - Migrate Local AD to AADJ but Machines are AADR
  FAQ FAQ  Forum Search   Events   Register Register  Login Login

Migrate Local AD to AADJ but Machines are AADR

 Post Reply Post Reply
Author
Message
sdesimone View Drop Down
Newbie
Newbie


Joined: 03 Nov 2023
Status: Offline
Points: 2
Post Options Post Options   Thanks (0) Thanks(0)   Quote sdesimone Quote  Post ReplyReply Direct Link To This Post Topic: Migrate Local AD to AADJ but Machines are AADR
    Posted: 15 Dec 2023 at 1:08am
Hi all,

Using the corporate version to create the migration package and I understand the process here. The package will disjoin the machine from local AD, permission the profile with the objectId of the AAD user, and then the Windows PPKG will join it to AAD. 

While I have hit or miss issues with the Windows PPKG (no real errors, mostly garbage that I read could be related to telemetry and what not), what I'm interested to know is if this whole process moves over the AD registration regkeys which for the AADR config with the user profile? I know that they are in the hklm:\software hive and the enrollments should technically be associated with the old SID of the user but has anyone seen if that would "break" the registration status and just leave the machine AADJ?
Back to Top
Support View Drop Down
Moderator Group
Moderator Group


Joined: 09 Nov 2006
Location: United Kingdom
Status: Offline
Points: 1840
Post Options Post Options   Thanks (0) Thanks(0)   Quote Support Quote  Post ReplyReply Direct Link To This Post Posted: 15 Dec 2023 at 5:26pm
Hi, 

The software does not move, copy or delete any data. Instead it configures the existing profile “in place” so that it can be used by the user’s new account.

Is the issue you are having with the Azure AD join using the Provisioning Package?

Do you know if the Provisioning Package is working? You can run the PPKG manually on a computer on its own as a test to prove that, and you may find additional information in the Event Viewer or logs;

You should be able to see entries in the Event Log to help identify what the problem is with the Provisioning Package under;
Applications and Services Logs > Microsoft > Windows > User Device Registration > Admin

If the Provisioning Package is actually failing to install, there is an additional log at C:\ProgramData\ForensiT\Logs\ProvisioningPackage.log.

Many thanks,

Support.
Back to Top
 Post Reply Post Reply
  Share Topic   

Forum Jump Forum Permissions View Drop Down

Forum Software by Web Wiz Forums® version 12.03
Copyright ©2001-2019 Web Wiz Ltd.

This page was generated in 0.031 seconds.