Skip to main content

We are just rolling out new computers to our staff, the currently have MBPs with local accounts, on the new computers, we are adding them to the AD domain to ease with logins and password across our district.



If we let them use Migration Assistant, they will create new users on the computer with their settings and files and not use the new account that we are trying to get them to use.



We will assist them in moving their files, bookmarks,images and music over, but don't want them to use Migration Assistant.



I have tried to rename / remove the app, I tried to restrict the app, nothing works.



Any ideas?

Use NoMAD login and NoMAD to continue to allow local accounts. As it is a far better experience than trying to use AD mobile accounts.



If not you could just disable "Transfer Information." in your pre-stage profile if you're using DEP deployment.



or Possibly try restricted software


Hi @jcalvert



See attached screenshot, via Restricted Software we have restricted the Migration Assistent.




@txhaflaire Our setup is like this:



Yours is most likely not working because you have "Restrict exact process name" checked, the process is named "Migration Assistant.app".
If you add the .app, or remove the checkbox it will most likely work!


@remyb We have no issues with our Restriction 🙂 all is working fine, just posted it for @jcalvert


Arrgh, I need more coffee, sorry 🙂


@remyb Haha no worries, thanks for helping out in this discussion!


Thank you everybody for your responses, very much appreciated.


I have disabled "Transfer Information" AND restricted Migration Assistant

BUT it is still showing up as an option and allowing end users to do this.

????


Reply