No Matches Found!
Try with a different search term
I have a 13.3 setup on a physical server, and I have recently setup a 14.1 on a VM that will be our new production server. I'm trying to figure out the best way to start to migrate these windows (all win ce) devices to the new SOTI server.
Any one have any ideas or experience doing this? I've been searching around for some info but I actually do not see much online.
I've run into this in the past and have yet to get a really straightforward answer on the recommended "best practice" approach for migrating devices across instances.
That was also before Raymond Chan hit the scene so I'm sure we'll get a more thorough answer now!
Can you provide more information, e.g.
- How many devices are currently managed by your v13.3 server?
- How critical are the devices to your business operations? (I mean how serious/costly will it be if some/all of your device(s) get out of control after the migration? Can you afford massive device recalls/re-enrollments ?)
- How many different types (brand/model, firmware version, etc) of devices are there?
- Does your v13.3 implementation use AD/LDAP, SSL certificates closed internal/public network?
How many devices are currently managed by your v13.3 server?
Currently about 7000 devices.
How critical are the devices to your business operations? (I mean how serious/costly will it be if some/all of your device(s) get out of control after the migration? Can you afford massive device recalls/re-enrollments ?)
No, ideally mass device recalls are a no go. Re-enrollments isn't a horrible option, but not the best solution.
How many different types (brand/model, firmware version, etc) of devices are there?
Single device model/version of windows/all same firmware.
Do you v13.3 implementation use AD/LDAP, SSL certificates closed internal/public network?
We do use LDAP/AD but no public network, everything internal with the certs.
This is neither a small nor a straightforward project! It's likely to be at least 2-3 weeks' work (including planning, pilot-run on test server, actual upgrade, device migration, ..., etc.) if my company is working on something similar. We'll need answers to many tens of questions before we can estimate the effort, feasibility and costs.
As there are so many devices and you can't afford many device recall/re-enrollment, I recommend you to contact Soti professional service team in your region to do it. Trust me. You would likely regret if you try to do it yourself.
Finally, I personally won't recommend my customers having that many devices in production to migrate to v14.1 so soon.
Are there any glaring issues with 14.1 still? What is your current "stable" build, 13.3 or 13.4?
The UI of v14 is still being migrated to the new design step-by-step, and there are just so many new features introduced in the recent v14.x releases.
At the moment, it should be comparatively much safer to stick with the latest patch for v13.4 (currently 13.4.0.4744) for "mission critical" and/or "large" implementations. Although we always test all major features in a new version on our own test server(s) before recommending it to our customers, we still remind each customer to test features critical to his/her operations before upgrading.