11/1/2023 0 Comments Airwatch uagThis way you do not need to add any other reconfiguration steps during your DSaaS migration and you can take your time preparing for the change. In order to offer the most seemless experience to your users during your SaaS migration, it is important that your API servers are accessible from Internet. This is an ideal solution if you want to control access on your API infrastructure but it can be challenging if the day comes when you have to migrate to a SaaS environment. In addition, a dedicated API server can be setup to be reachable only from your internal network. This is recommended when you are using more that 50,000 devices. In Workspace One UEM your API servers can be installed on separate servers. Unified Access Gateway with the following Workspace One UEM Edge services.Workspace One Core components (Console Serveur, Device Service Serveur).There are multiple services that use REST API in Workspace One: I would like to share my experience about this and provide an overview of the steps that you need to complete in order to achive the public API URL publication before your DSaaS migration. Using a custom URL for API gives the possibility to prepare the migration and make sure that the switch between your On Premises environnement and the SaaS environnement is done smoothly. One of the advantages of migrating to a Workspace One UEM DSaaS tenant is that you can choose the API URL that you want to use.ĭuring the migration process you will keep your Device Services URL (mandatory to keep your devices enrolled in Workspace One UEM) and you can also use a custom URL for the API services. Planning your Workspace one UEM and Workspace One Access migration from On-Premise to DSaaS can be challenging, especially if your Workspace One UEM API URL is not public and only accessible from your internal(s) server(s).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |