Migration on prem AD to Azure AD (Corporate)

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

   We have the corporate version - I set up the Provisioning package and userlist.csv file and am using the deployment kit.
Everything seemed to run without errors (log file below) but when the machine I'm running it on reboots it has a nonexistent user login, no option for 'other user' and the domain just shows workgroup and is not connected to Azure.

I used the instructions to use simple setup on the provisioning kit, then switch to advanced at the end to keep the machine name the same - could that be the problem?

When I looked in Entra ID I see the machine listed there - possibly from Azure connect on the on premises domain controller?

Thanks,
Dean

-----------------------  migration log ----------------------
ForensiT User Profile Wizard 24.6
Licensed to Tech One Computer Solutions, LLC (1 Seats) License No. FFF2437
Copyright (c) 2002-2024 ForensiT Software Ltd
www.ForensiT.com

Target device: UW-VOLNTR01-WXL
OS build 10.0.19044.3086. Version 21H2.
Domain: UWFCPA
Migrating user account "uwadminvol01"
Processing UWP Apps... Done.
Setting Registry ACLs... Done.
Set Registry ACLs in 0.510 seconds.
Closing Apps... Done.
Setting Profile ACL... Done.
Set Profile ACL in 0.942 seconds.
Creating Profile registry keys... Done.
Adding new account to local groups... Done.
Setting uwadminvol01 as default logon... Done.
Calling Provisioning Package... Done.
Migration Complete!

Author	Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic
dlmartin Members Profile Send Private Message Find Members Posts Add to Buddy List Newbie Joined: 24 Jan 2024 Location: Chambersburg, P Status: Offline Points: 2	Post Options Post Reply Quote dlmartin Report Post Thanks(0) Quote Reply Topic: Migration on prem AD to Azure AD (Corporate) Posted: 24 Jan 2024 at 1:52pm
	We have the corporate version - I set up the Provisioning package and userlist.csv file and am using the deployment kit. Everything seemed to run without errors (log file below) but when the machine I'm running it on reboots it has a nonexistent user login, no option for 'other user' and the domain just shows workgroup and is not connected to Azure. I used the instructions to use simple setup on the provisioning kit, then switch to advanced at the end to keep the machine name the same - could that be the problem? When I looked in Entra ID I see the machine listed there - possibly from Azure connect on the on premises domain controller? Thanks, Dean ----------------------- migration log ---------------------- ForensiT User Profile Wizard 24.6 Licensed to Tech One Computer Solutions, LLC (1 Seats) License No. FFF2437 Copyright (c) 2002-2024 ForensiT Software Ltd www.ForensiT.com Target device: UW-VOLNTR01-WXL OS build 10.0.19044.3086. Version 21H2. Domain: UWFCPA Migrating user account "uwadminvol01" Processing UWP Apps... Done. Setting Registry ACLs... Done. Set Registry ACLs in 0.510 seconds. Closing Apps... Done. Setting Profile ACL... Done. Set Profile ACL in 0.942 seconds. Creating Profile registry keys... Done. Adding new account to local groups... Done. Setting uwadminvol01 as default logon... Done. Calling Provisioning Package... Done. Migration Complete!

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: 08 Feb 2024 at 5:34pm
	Hi Dean, According to the log file, you are using the Professional Edition. User Profile Wizard doesn't join the computer to Azure itself, your Provisioning Package does that. User Profile Wizard installs it using the PowerShell cmdlet install-provisioningpackage packagename.ppkg -forceinstall when you see 'Calling Provisioning Package... Done' in the migration log. When the computer boots, if you do not have the 'Other User' option, it could just be that the computer hasn't yet joined Azure. When the Provisioning Package is 'installed' at the end of the migration process, Windows actually joins the computer to Azure when the computer next boots, that's why you don't see the Other User option immediately on boot. In our testing, we see that does appear after a while, or you can just reboot the computer again (just give it a couple of minutes to join Azure first). Do you know if the Provisioning Package is working? You can run the Provisioning Package 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. You do not need to use a Provisioning Package to join the computer to Azure, as you are using the Professional Edition, you are manually migrating each computer using the GUI, you could also join the computer to Azure in Windows Settings if you are having a problem with the Provisioning Package, or until you resolve the issue with the Provisioning Package. Many thanks, Support.