Deployment Server LoadBalancing Address
Please provide more details.
- Are you migrating from a single deployment server implementation to a 2-DS HA implementation?
- What platforms of devices were already enrolled on your single-DS system? How many devices were enrolled? Are these devices in production state and mission critical? Or are they just test devices in very initial deployment?
- Are you 2-DS system already up and running with previously enrolled devices functioning properly and under control?
- Are you going to add new platforms of devices?
We have never worked on an HA MobiControl system with load-balancer that just handles port 5494. It's very hard to imagine what you have in mind to make the whole MDM/EMM solution works, and works cost effectively without having difficulties to accommodate new features/restrictions in emerging Android and MDM/EMM technologies.
However, from what you described, you are actually building your HA system from scratch, without the risks of screwing up loads of production devices and legacy policies already deployed. Thus you can freely explore and innovate.
We use only Port 5494 because we dont us WebEnrollment, only silent Agent Installation with the apk and the ini Files.
I can update this post later, if all works fine with my configuration.
I am still not sure if i have to configure the loadbalancer address somewhere in the console too.