Skip to content

Draft: Add Okta errors to Jamf enrollment handbook; add tips for data migration (Gdrive, Chrome bookmarks)

Michael Friedrich requested to merge handbook-endpoint-management-jamf-okta-errors-tips-data-migration into master

Why is this change being made?

During my Macbook refresh, I needed to enroll Jamf which was not installed. After setting up Okta Device Trust and 1Password, I was able to log into Okta which then showed a permission error for Jamf. https://gitlab.com/gitlab-com/it/end-user-services/issues/laptop-issue-tracker/-/issues/2621#note_1418786627

After asking in the #it_help Slack channel, I could configure Jamf with assistance and temporary permissions.

This MR updates the endpoint management handbook with adding the 1Password/Okta Device Trust instructions as requirement for Jamf enrollment. Team members can follow the handbook links, when they come from the laptop refresh issue template to complete the process. If Okta already works, this requirement is fulfilled.

The FAQ at the bottom adds a new error section, guiding team members to the Slack channel for human assistance.

Additionally, this MR also adds a section for data migration. I like the Google drive suggestion, but accidentally did not read it in the second sentence. I've also added a hint for syncing browser settings and bookmarks which is very handy and efficient with Google Chrome.

Author Checklist

  • Provided a concise title for this Merge Request (MR)
  • Added a description to this MR explaining the reasons for the proposed change, per say why, not just what
    • Copy/paste the Slack conversation to document it for later, or upload screenshots. Verify that no confidential data is added, and the content is SAFE
  • Assign reviewers for this MR to the correct Directly Responsible Individual/s (DRI)
    • If the DRI for the page/s being updated isn’t immediately clear, then assign it to one of the people listed in the Maintained by section on the page being edited
    • If your manager does not have merge rights, please ask someone to merge it AFTER it has been approved by your manager in #mr-buddies
    • The when to get approval handbook section explains the workflow in more detail
  • If the changes affect team members, or warrant an announcement in another way, please consider posting an update in #whats-happening-at-gitlab linking to this MR
    • If this is a change that directly impacts the majority of global team members, it should be a candidate for #company-fyi. Please work with internal communications and check the handbook for examples.

Merge request reports