- Products
- Learn
- Local User Groups
- Partners
- More
Welcome to Maestro Masters!
Talk to Masters, Engage with Masters, Be a Maestro Master!
Join our TechTalk: Malware 2021 to Present Day
Building a Preventative Cyber Program
Be a CloudMate!
Check out our cloud security exclusive space!
Check Point's Cyber Park is Now Open
Let the Games Begin!
As YOU DESERVE THE BEST SECURITY
Upgrade to our latest GA Jumbo
CheckFlix!
All Videos In One Space
Hello,
I've got a problem with the migration of the SMS server. Right now I have a production SMS ( with EPM endpoint management) and the new one where I want to set migration. Both of them are using two separate interfaces one for mgmt second for emp.
Both servers are with the same software version and JHF.
After ./migrate import, I can see all the same configurations as in the production environment.
Unfortunately, the connections with end-points are down. After that, I try to use this procedure (reconnect tool) for every hosts in my company.
I. Create Reconnect utility Reconnect clients:
1. Connect to the new server using the Endpoint Management console and export any profile.
2. Get the "config.dat" file from the server path
cd /$FWDIR/conf/SMC_Files/uepm/DA/config.datc.
3. Run cmd.exe from the machine where the SmartConsole is installed.
4. cd C:\Program Files (x86)\CheckPoint\SmartConsole\E80.30\PROGRAM\util\RepWorkFolder\INVOKE
5. Run the command: maketool.bat <path to config.dat created in step #1> <"client uninstall password">
6. Reconnect.exe will be created in the current directory.
II. Reconnect Clients:
1. Run Reconnect.exe on the client computer, it will register to the new server.
But in a situation where I have around 500 hosts and more people are working remotely, it is very problematic.
Do you have any idea how can I do it more automatically?
I will be very grateful for help or any suggestions.
All the best,
Is the same IP used pre and post migration?
If so...I wonder why you're needing to run the reconnect utility at all.
Yes both interfaces (MGMT and EPM) have the same IP addresses as current production SMS.Of course, Before this new one is turning on I switch off the production.
I recommend getting the TAC involved then.
Sounds like something else may be at play here.
Actually, I get this instruction from TAC support.
But I wonder if someone had the same problem with migration EPM and after those connections between SMS and endpoint clients
Hello,
Copying a file named: "server-list.xml" from production SMS solved the issue. 🙂
All the Best,
About CheckMates
Learn Check Point
Advanced Learning
YOU DESERVE THE BEST SECURITY