Re-building deployment server
How many devices are currently being managed?
Are they mission critical that you cannot afford even a handful of device recalls and re-enrollments?
Are you prepared to recall and re-enroll ALL existing devices in the worst case?
Hi, thanks for the reply.
Yes, in the worst case.
Is there a way to preserve existing enrollment by simply exporting and importing at the destination server? I want to avoid the complicated database migration procedure.
Thank you again.
How many devices are to be managed for each of Android, Windows and iOS platforms?
Why do you choose to target to MobiControl v14.0.0 rather than the latest v14.2.2?
Are your iOS devices going to be DEP supervised devices? Are they running iOS12+?
Are your devices restricted to a closed corporate network or have access to the internet?
There are total around 200 devices, among them 40% Android and rest are Windows. There is no currently iOS devices. we might use it in near future.
I dont mind to go to latest version. I just mentioned the major release.
Yes, we access them both environment, intranet and internet as well.
Though the number of devices are not that many, you have so many device platforms to consider, and your current and target configurations are a bit tricky and some just don't make sense. A seamless migration may be possible if you give up some requirements, which you should not if you want to prepare the server to be able to support latest Android/iOS/Win10 devices and features in the coming few years. I think you need someone experienced in migration/upgrade to plan, implement and support the whole process for your company.
Frankly, you likely cannot reveal enough details of your implementation in an open forum due to security reasons, and those who are competent to do it will not or are not allowed to reveal every details of the required implementation in an open forum due to business reasons. The best is for you to get in touch with Soti support/professional service teams to discuss the details.
Hi Raymond, Thank you for the direction and I totally understand your concern.
As i know it is a SOTI business user forum, not a PUBLIC trial user forum. Supposed to be able to discuss various implementation scenarios.
I am not from Soti, nor am I stopping you from discussing anything you like.
You can virtually post any questions for discussion. It's just that your problem is quite complex, and your implementation details can become too sensitive to be revealed in an open forum if more questions are asked. My company and I got paid for doing upgrade/migration in Hong Kong, and I'm not allowed to reveal too much information due to business reasons. Besides, if what we do screw things up in our customer's system, we have obligation to fix it to the end. Here, if I or somebody else say something wrong and you follow it or miss some crucial steps, you might regret why you don't officially outsource the task and have to spend very very long time struggling by yourself.
If you are lucky, maybe someone from Soti can give you all the information you need for free.
BTW, you likely need to use paid SSL certificate from selected CA vendors and also official FQDN (rather than host name or IP address) if you need to manage iOS12 devices. Many features for Windows 10 and Android Enterprise platforms also need them.
I partially disagree your points. Everybody knows the limitations and risk of the expert advise or opinions of a FORUM. Nobody going to put critical information on forums. It is totally at the risk of who initiate the question. I don't put it for an argument. Rather, respect your business and i hope someone else be here to give advise beyond the business perspective and enabling the users to experience the best of SOTI features!
Have an awesome day, Raymond.
Thank you for requesting a response from SOTI Support Staff.
The processes of retiring an old server can be simplified by using the same FQDN, IP address's and performing your upgrade prior to moving to the new server or afterwards (not during) as it requires an upgrade path to be followed.
This way you can backup and restore the Db and away you go. You will need assistance from the SOTI Support Dept to release you installation ID so that it can used on the new server but this can be done same day by creating a case and speaking with a SOTI Support Technician.
Is it a business requirement to change the hostname and use this is the configuration instead of the FQDN? Also, I do not see any mention of the SQL in the new configuration...
We also want to remind you that what may work for one environment may not work entirely for another installation. ie... you need to consider that your environment needs a SHA-1 certificate for your CE devices and MC V14 "fresh installs" utilize SHA 2 certificates as the default encryption level.
Lastly Raymond's suggestion to get a hold of SOTI Support at email@example.com by creating a case is consistent with what we would recommend as most situations have unique scenarios and security considerations that we can only address privately. If you would like, VIA a SOTI Technician, a Professional Services call can be scheduled as a PAID service where we can provide any scrip assistance if new server information needs to be updated onto devices as "migrations" can render devices unable to communicate to the server and therefore unable to be managed, if done incorrectly.
Hopefully this has provided you some more information but please keep in mind it is meant only as a discussion and not as a guide to "Rebuilding your Server"
Technical Support | SOTI Inc. |1.905.624.9828 | firstname.lastname@example.org | www.soti.net |