Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Missing guide: Multiple ABM and VPP for MSPs #22339

Closed
noahtalerman opened this issue Sep 24, 2024 · 5 comments
Closed

Missing guide: Multiple ABM and VPP for MSPs #22339

noahtalerman opened this issue Sep 24, 2024 · 5 comments
Assignees
Labels
bug Something isn't working as documented #g-mdm MDM product group :incoming New issue in triage process. :release Ready to write code. Scheduled in a release. See "Making changes" in handbook. ~released bug This bug was found in a stable release.
Milestone

Comments

@noahtalerman
Copy link
Member

noahtalerman commented Sep 24, 2024

💥  Actual behavior

In Fleet 4.56 we shipped the "Add multiple Apple Business Manager and Volume Purchasing Program connections" (#9956) story.

Now, Managed Service Providers (MSPs) that use Fleet and/or build on top of Fleet (ex. customer-deebradel) to manage workstations across multiple clients only need on Fleet server.

We don't have a guide that walks through the best practice setup for these customers:

  • One Fleet
  • One ABM connection per client. Each ABM connection has 3 default teams:
    • macOS: 💻 Workstations
    • iOS: 📱🏢 Company-owned iPhones
    • iPadOS:🔳🏢 Company-owned iPads
  • One VPP connection per client.

To fix

PR is here: #22458

@noahtalerman noahtalerman added bug Something isn't working as documented :release Ready to write code. Scheduled in a release. See "Making changes" in handbook. #g-mdm MDM product group :incoming New issue in triage process. labels Sep 24, 2024
@noahtalerman
Copy link
Member Author

Hey @georgekarrv I just realized we're missing a guide that walks through the core business case for multiple ABM and VPP accounts: MSPs

I filed a bug here. Leaving the story open (#9956) until we ship this guide.

cc @lukeheath

@roperzh
Copy link
Contributor

roperzh commented Sep 24, 2024

Guide was updated here #21627

This is a duplicate of #21185

Edit: the guide might need some tweaking with the wording about the best practice tho.

@noahtalerman
Copy link
Member Author

the guide might need some tweaking with the wording about the best practice tho.

Yes this!

@roperzh please let me know how I can be helpful to whoever ends up working on this. Happy to jump on a call and do it together.

@noahtalerman noahtalerman added the ~released bug This bug was found in a stable release. label Sep 26, 2024
@noahtalerman noahtalerman self-assigned this Sep 27, 2024
@noahtalerman
Copy link
Member Author

please let me know how I can be helpful to whoever ends up working on this. Happy to jump on a call and do it together.

@roperzh and @georgekarrv heads up that I took this bug.

PR to guides is up here: #22458

noahtalerman added a commit that referenced this issue Sep 27, 2024
@georgekarrv georgekarrv added this to the 4.58.0-tentative milestone Oct 2, 2024
@fleet-release
Copy link
Contributor

Fleet's guide now blooms,
ABM, VPP in rooms.
Ease for all clients looms.

@georgekarrv georgekarrv removed the :demo label Oct 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working as documented #g-mdm MDM product group :incoming New issue in triage process. :release Ready to write code. Scheduled in a release. See "Making changes" in handbook. ~released bug This bug was found in a stable release.
Development

No branches or pull requests

5 participants