I'm working with a customer and they want to use Jamf Login/Connect. I got this all deployed and setup. The issue I see is since this creates a new user account on their Mac what can we do with the old account data. They want all the data that was on the old local account. Is there a script that would be good to run so they can migrate data over? This is a deployment with out MDM yet.
Question
Jamf Connect/Login user migration
+17
+9You should be able to use the migrate flag:
defaults write /Library/Preferences/com.jamf.connect.login.plist Migrate -bool TRUE
defaults write /Library/Preferences/com.jamf.connect.login.plist MigrateUsersHide -array "localadmin" "managementaccount"When set, the user should be able to log in, and then get presented with a list of accounts that are already on the system.
Here's a link to the documentation for these preferences.
+17This is only for Okta.
Migrate
Allow local accounts to be migrated to Okta-based accounts.
<key>Migrate</key>
<false/>
+17Just tested and works with Azure thanks.
+4Does anyone know how to format this in the plist that is delivered by the configuration profile? I can't find this mentioned in the documentation. Where did you find this?
+4Has anyone else been able to get this to work with Azure. Jamf support tells me it's not supposed to work but as we can see above it is working for some.
+9I haven't been able to get this to work under version 1.1.2.
+1I've used the Migrate flag with Azure and it works ok.
The problem I'm having is if you log out/restart afterwards and try and log in with the azure window the next time it loops back. Logging in with local auth is fine but kind of defeats the point of migrating.
I've since removed the Migrate flag for a test and it looks like it doesn't do it any more. Is this a known bug or is there a good way to avoid it?
+1As you can see below I have used "Migrate" key in the payload and still after successful AzureAD sign-in its not presenting a window with list of existing local users for me choose and map.
please assist
+1As you can see below I have used "Migrate" key in the payload and still after successful AzureAD sign-in its not presenting a window with list of existing local users for me choose and map.
please assist
According to logs from this location /private/tmp/jamf_login.log it seems like JC is throwing error as shown below and I suspect migrate key isn't working as expected. please assist if you are aware of this issue.
+1According to logs from this location /private/tmp/jamf_login.log it seems like JC is throwing error as shown below and I suspect migrate key isn't working as expected. please assist if you are aware of this issue.
We are on the same phase, getting the same error, did you got any solution for this?
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.