Sure, no problem at all with that task.

Make a backup and restore it in another SQL server.

Then in Mobicontrol Admin Utility change the database settings accordingly.

Hi Edgar,

thanks for your fast answer.

Unfortunately I made a mistake: I want make a copy instead of moving.

I've done an export of the source- database and I can't find any server addresses.It looks like the server addresses are only stored in the ".exe.config" files and they have to be configured as you wrote through the admin utility.

Of cource I will make a backup of my destination database before importing any data ;)

Copying database is basically not recommended officially, and  is much more complicated than migrating database between servers.      Based on my previous hands-on experience , there are some preparation work needed in the source server before the copy operation, and some clean-up to be done in the target server after the copy operation.  If done improperly,  some policies of both servers will be problematic.

Hi Chan,

thanks for your reply.

Can you tell me the preperation and clean-up procedure, please?

I think preparation should be look like:

- you need same Version of MobiControl

- Licencekey for destination server

- backup database of source and destination

- stop all services on destination

- Import database into destination

Clean up on destination:

- (stop all services on destination)

- start Admin-Utility and check/ change all Server- addresses  (Database, Deployment server name, Agent address addresss, Management Service Address, Deployment Server FQN/IP)

- start services on destination

- Login into Webconsole

- remove all devices

- If you use certificates that use the source server, exchange all certificates with the correct certificate

- delete all "Add device rules" and create new ones

The preparation and clean-up I was talking about were nothing like what you said, but were related to modifying/removing some entries in tens of tables in the SQL database depending on what devices, groups, policies, certificates,  ..., etc. had been included in the original database.

In the past, I played with different options on evaluation servers only.   There are just so many different combinations to try, and the results on whether some entries should stay or go were not conclusive even for some simple options.  Moreover, the schema/tables varies between different MobiControl versions.    Hence, I have never performed the process on any production servers for my customers even when they are willing to pay for such service.    The risks are just so high, and we will be on our own without any official support from Soti if we do that for our customers.   Thus, I think there is nothing on this worth sharing in this forum.

If you think you know enough about Soti & MDM, have the time to make sufficient tests and  are so bold to do it on your company server,  you can go ahead,  as long as you remember that you won't get any official support from Soti if some hidden problems eventually surface.

If any of my friends ask me the same question face-to-face,  my only answer to them would be : "Don't even think about it!"  (unless Soti documents the procedure or provide tool(s) to support such process in the future)