Separating Endpoint Management from SMS

[Kryten]

Hello!

I am currently trying to find out the neccessary steps for separating an EPM from a SMS. 

At the moment the SMS is doing the Endpoint Management, but our customer plans to separate that into two servers for better redundancy and to get rid of that limitation with DB revisions (Not possible to use revisions when SMS is also doing the EPM). 

Apart from an old Post (2017) that ended with "PS needs to be involved", I did not find anything...So I came here to see if anyone has done this before and could give some useful hints.

I guess at first I should be installing a second management server, importing the DB and then activating the EPM blade. But what then? I guess I cannot just disable that blade on the first server and everything will work, that sounds too easy. 🙂

Somehow the Clients will need to know that they have to connect to a different server now and that will probably bring other issues like changed fingerprint and/or certificates...and probably more stuff that I do not think of yet. 

So...is there a Guide or SK that I missed? Or someone who did this already? 

Best Regards,

Alex

[Don_Paterson]

Can you do it the other way?

The existing server stays there for EPM (and remove firewalls and policy) and the new one is installed (import) for the gateway management.

I guess EPMaaS  is not an option to move the EPM to the Infinity Portal?

You have to plan around licenses too.

Another option is to leave the current server as EPM (as above) and build a new SG management server (SMS) and then build that up from scratch.

You would need to do a SIC reset on the SGs and can use API to make policy 'migration' more efficient.

Just initial thoughts. Hopefully someone who has done it picks this up too.

Regards,

Don