Skip to main content

Like most JAMF environments, we don't let users be admins on their own box, so when a user gets a new computer that means that they cannot use Apple's Migration Assistant either, so I had to come up with a "homegrown" solution for users to migrate their data instead of having the IT do the transfer for them.  This a constant work in progress, and in no way as comprehensive as Apple's utility, but it works to get the job done.  Feel free to use in your own environment and let me know of any feedback / usability enhancements, etc...  Again...this is not perfect in any way, and always a WIP, so if you use this test, test, test!  Enjoy...


 


Source Code: https://github.com/ScottEKendall/JAMF-Pro-Scripts/tree/main/MigrationWizard





Do you have some undocumented steps for the Outlook signature? Simply copying the signature files to the GroupContainer path doesn’t load them into Outlook’s database..


Great job, Scott. I like it a lot and will make sure to test it thoroughly :-)


Do you have some undocumented steps for the Outlook signature? Simply copying the signature files to the GroupContainer path doesn’t load them into Outlook’s database..

It appears to get the signatures data loaded you have to delete the sqlite database. Here’s a snippet of from my modified version to catch this…

outlook_profile_path="${user_dir}/Library/Group Containers/UBF8T346G9.Office/Outlook/Outlook 15 Profiles/Main Profile/Data"
if -d "$outlook_profile_path" ]]; then
sqlite_files_found=$(/usr/bin/find "$outlook_profile_path" -type f -name "*.sqlite" 2>/dev/null)
if -n "$sqlite_files_found" ]]; then
sqlite_count=$(echo "$sqlite_files_found" | /usr/bin/wc -l | /usr/bin/xargs)
/usr/bin/find "$outlook_profile_path" -type f -name "*.sqlite" -exec /bin/rm -f {} \; 2>/dev/null
echo "Deleted $sqlite_count .sqlite database files" >> "${user_log_file}"
fi

Delete that after restoring the signatures and the user is prompted for a rebuild on restart of Outlook.


Reply