Domain > AzureAD via GPO Issue

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

   Getting "Azure Object ID file path not found" in the logs when attempting to migrate local domain users to AzureAD.

Here are the files we have in the Startup folder for the GPO:

Users.csv
Provisioning Package (to join to AzureAD)
ForensiTAzureID (for the Object ID lookup)
PowerShell script (generated via the wizard)
Config file
Profwiz Application

Using the wizard, we point those dependency/lookup files towards the default C:\ProgramData\ForensiT\User Profile Wizard Corporate\Deployment Files location.  According to the documentation, if we check the box "Deploy using a Desktop management tool..." that should collect all the files we need and associate them accordingly.  Though it doesn't seem to collect the AzureID or Provisioning Package files, we've tried both including them and removing them from the Startup folder for the GPO.  Seems like it can't find the AzureID lookup file, and probably wouldn't find the Provisioning Package if it got that far.  What are we missing?

Author	Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic
Kgrizzell Members Profile Send Private Message Find Members Posts Add to Buddy List Newbie Joined: 16 Nov 2023 Status: Offline Points: 3	Post Options Post Reply Quote Kgrizzell Report Post Thanks(0) Quote Reply Topic: Domain > AzureAD via GPO Issue Posted: 16 Nov 2023 at 10:24pm
	Getting "Azure Object ID file path not found" in the logs when attempting to migrate local domain users to AzureAD. Here are the files we have in the Startup folder for the GPO: Users.csv Provisioning Package (to join to AzureAD) ForensiTAzureID (for the Object ID lookup) PowerShell script (generated via the wizard) Config file Profwiz Application Using the wizard, we point those dependency/lookup files towards the default C:\ProgramData\ForensiT\User Profile Wizard Corporate\Deployment Files location. According to the documentation, if we check the box "Deploy using a Desktop management tool..." that should collect all the files we need and associate them accordingly. Though it doesn't seem to collect the AzureID or Provisioning Package files, we've tried both including them and removing them from the Startup folder for the GPO. Seems like it can't find the AzureID lookup file, and probably wouldn't find the Provisioning Package if it got that far. What are we missing?

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: 1809	Post Options Post Reply Quote Support Report Post Thanks(0) Quote Reply Posted: 18 Nov 2023 at 7:52am
	Hi, "Azure Object ID file path not found" the path to the file is incorrect in the config file. You can remove the path and only specify the filename, profwiz will look in the same directory as itself if no path is specified. Many thanks, Support.

Kgrizzell Members Profile Send Private Message Find Members Posts Add to Buddy List Newbie Joined: 16 Nov 2023 Status: Offline Points: 3	Post Options Post Reply Quote Kgrizzell Report Post Thanks(0) Quote Reply Posted: 20 Nov 2023 at 3:31pm
	Many thanks, that worked. I suppose we should have looked at where it was referencing the Users.csv file as a clue for the other reference files. So does the Wizard not remove the file path during the setup process? Just wondering why we would have to manually modify the Config file, and why it wasn't necessary for the Users.csv file.

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: 1809	Post Options Post Reply Quote Support Report Post Thanks(0) Quote Reply Posted: 21 Nov 2023 at 10:15am
	Hi, It will if you are creating a Single Deployment File, because all required files are included within the exe for ease of distribution. It will not edit the paths that you specify in the config file, you could be referencing the files from a UNC share for example. Many thanks, Support.