Transferring Devices to new environment

Transferring Devices to new environment

Morning,

 

Has anyone attempted to transfer devices from one SOTI environment to another without user interaction? If so how did it go for you. Looking thru my scripts it seems I should be able to just send this:

Writeprivateprofstring Connection DeploySvr1 (FQDN of new server)
Writeprivateprofstring Connection DeploySvr2 (ip of new server)
restartagent
sleepex 350
connect -f

7 Answers

Order By:   Standard | Newest | Votes
Edgar Gomez | posted this 02 November 2018

Hello,

You need to create an add device rule and get the Add Devices Rule Tag.

Also you need the Mobicontrol SiteName (in Global Settings)

Then send the following script to devices:

 

writeprivateprofstring Comm TLS 0
writeprivateprofstring Info SiteName <MobiControl>
writeprivateprofstring Device DeviceClass <DEVRULETAG>
writeprivateprofstring Connection DeploySvr1 <IP/DNS>
disconnect
sleep 5
connect

 

Hope this helps

  • 0
  • 0
Anil | posted this 04 November 2018

Dear team,

i have also two environment . AND my devices are communication to the server on the two different port. and there is netting on firewall to redirect traffic to both environment depend on the ports .

 

FQDN:5494   for environment 1 

FQDN:5499   for environment 2

 

so i can use this script also ??

can we send port number also like below  for moving device from environment 1 to environment 2  

writeprivateprofstring Comm TLS 0
writeprivateprofstring Info SiteName MobiControl
writeprivateprofstring Device DeviceClass <DEVRULETAG>
writeprivateprofstring Connection DeploySvr1 FQDN1:5499
writeprivateprofstring Connection DeploySvr2 FQDN2:5499
disconnect
sleep 5
connect

 

 

  • 0
  • 0
Raymond, Chan | posted this 05 November 2018

I personally doubt the two scripts suggested can cleanly achieve the required task.  Even if they could do so, I suspect that they might partially work only for some Android+ devices.   Thorough tests have to be carefully done on test platform before deciding on whether to use them on production server/devices.  

 

If the original server is managing Android Enterprise,  iOS DEP or Windows 10 devices, there will likely be many problems.  After many security enhancements recently introduced by Google, Apple and Microsoft,  seamlessly (i.e. no device recall/re-enrollment and no device end-user interaction required) migrating an EMM implementation to a different FQDN is getting more difficult, if not impossible.  

 

Even if a "seamless" migration (to different FQDN) solution does exist, the procedures required vary widely with the servers and devices present in each case.  If it is very costly to do device recall/re-enrollments in a production environment,  it is best to consult and get Soti Professional Service team to plan and carry out the migration tasks.

 

  • 1
  • 0
Edgar Gomez | posted this 06 November 2018

Well, we have migrated more tha 1.000 devices from cloud to on-premises with that script. It was very clean process. Of course, we need to have profiles and rules setup in the new server so when devices connect they have the same configurations applied.

  • 1
  • 0
Raymond, Chan | posted this 08 November 2018

Hi Edgar,

Were all your 1000 migrated devices using Android+ agents ? Or do some of them belong to Android Enterprise and other device platform(s)?

 

If you have to set up profiles and rules from scratch in the new server, then what you did was not seamless migration because there was risk that your newly set up profiles and rules were not exactly the same as the original sets in the old server.  If there were data/content and/or apps previously pushed on the devices from the old server,  I doubt if you could have all of them untouched and remained functional with your new server.   BTW, did Soti recommended you to migrate from cloud server to on-premises server using this approach? 

 

In the general cases with tens or hundreds of device groups and profiles/rules already deployed and hundreds of devices of multiple device platforms, using this script approach to migrate does not sound practical.   

 

  • 0
  • 0
Jason Klotz | posted this 5 days ago

Were you moving devices agents with ELM?

  • 0
  • 0
ASMOD@Soti.net | posted this 5 days ago

Hi Jason,

Please be cautious using the script since the migration/transferring of devices to a new environment are customized according to each user's unique environment. There is a risk of losing connectivity to the devices if not performed accurately. I recommend you get in contact with our Professional Services department for expert advice regarding the migration process.  

Regards,

Technical Support | SOTI Inc. |1.905.624.9828 | support@soti.net | www.soti.net |

  • 0
  • 0
Give us your feedback
Give us your feedback
Feedback