- Flexera Community
- :
- App Broker
- :
- App Broker Forum
- :
- Two App Broker Environments Using Single SCCM
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
A customer is looking to implement both a dev and prod App Broker instance and currently only has one SCCM environment to point them both to. I'm sure that if they were to go this route there should be some best practices to take into consideration to help easily identify what is dev and what is prod in SCCM, but for now I'm just wondering if this is technically possible? I don't see anything about the web service that's installed on the SCCM server that would limit it to a single App Broker instance, but am I wrong about that or is there another limitation that would prevent one SCCM instance from connecting with two App Broker instances?
- Mark as New
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
This is not a best practice (i.e. it's better to stand up a simple second SCCM instance even if it doesn't mimic production SCCM), but it can be done. You will need to make sure the catalog titles are unique in each App Broker instance to avoid potential collection and deployment naming conflicts. We generally recommend pre-fixing the catalog titles in your DEV environment with "DEV-" (e.g. DEV-Adobe Acrobat DC). Then in production you would not use a prefix (e.g. Adobe Acrobat DC).
This thread has been automatically locked due to inactivity.
To continue the discussion, please start a new thread.
- Mark as New
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
This is not a best practice (i.e. it's better to stand up a simple second SCCM instance even if it doesn't mimic production SCCM), but it can be done. You will need to make sure the catalog titles are unique in each App Broker instance to avoid potential collection and deployment naming conflicts. We generally recommend pre-fixing the catalog titles in your DEV environment with "DEV-" (e.g. DEV-Adobe Acrobat DC). Then in production you would not use a prefix (e.g. Adobe Acrobat DC).
