Create a Post
cancel
Showing results for 
Search instead for 
Did you mean: 
Marcus_Halmsjo
Contributor

SandBlast Agent Management migration

Jump to solution

Hi,

We are moving from on-prem endpoint management server to cloud, both setups are active.

From what i understand we need to re-install the agent with the cloud managed one and tried a few things to minimize the work this entails.

So my question is if there are some tricks to make the re-installation less reboot more just works.

 

I downloaded the installation package i made from cloud management and tried installing it to see if it can upgrade.
It worked only thing i had to enter was the uninstall password and then the setup uninstalled old agent and installed the new without any reboot needed. Now to the problem it seems to not clear the management server adress so the new installation still connects to the local management address, is there some way to change this?

I'd hate to haft to uninstall, reboot, install, reboot 400 computers hands on.

0 Kudos
1 Solution

Accepted Solutions
Marcus_Halmsjo
Contributor

Thanks for the pointer, i found sk163372 that describe consolidating two management servers and running reconnect tool using config.dat from the new server after installation package is created. Seems logical this would be possible going to cloud if there is some way to get the config.dat.

 

Edit: Found the config.dat in the msi file for the new agent, created a reconnect tool using this will try and see if it works.

Update: it works, pushed new agent with the argument UNINST_PASSWORD and it upgraded then pushed the reconnect.exe created with the config.dat from the new agent msi, zero reboots and client shows up in cloud management.

View solution in original post

(1)
2 Replies
MikeB
Advisor

Hello @Marcus_Halmsjo ,

I know that there is a ReconnectUtility tool that runs on endpoints when the Endpoint Management IP is changed. It would be good if someone from Check Point could confirm if it is possible to use this tool also for your scenario (migrate on-prem to EMaaS). I can't find any SK with this information.

 

(1)
Marcus_Halmsjo
Contributor

Thanks for the pointer, i found sk163372 that describe consolidating two management servers and running reconnect tool using config.dat from the new server after installation package is created. Seems logical this would be possible going to cloud if there is some way to get the config.dat.

 

Edit: Found the config.dat in the msi file for the new agent, created a reconnect tool using this will try and see if it works.

Update: it works, pushed new agent with the argument UNINST_PASSWORD and it upgraded then pushed the reconnect.exe created with the config.dat from the new agent msi, zero reboots and client shows up in cloud management.

(1)