06-26-2019 09:32 PM
Hi
So I am thinking of doing the traps on premise to in cloud move and at the same time upgrading versions.
So is it doable ?
Whats the main gotchas to look out for
07-04-2019 07:29 PM
The configuration doesn't match, so you'll need to re-create your policy in TMS and can only utilize the EMS configuration as a baseline to what you need to make for TMS. Youll then want to ensure that your agents have been upgraded to the latest release to ensure that the migration goes smoothly.
When you generate the package on TMS you'll actually deploy that package through EMS, just be sure you've disabled service protection for the agents you're upgrading.
You can find the guide within the TMS admin guide as far as how you would perform the upgrade step by step.
06-27-2019 08:30 PM
You sure can, and without any issues. When you have your TMS instance setup you'll actually be able to generate an agent installation specifically for upgrading from an existing EMS managed agent. There really aren't any gotchas with it as long as you verify that any agent that was on EMS is actually shwoing up in your TMS instance and is showing as active.
07-02-2019 09:25 PM
Hi
Thanks, so I have create TMS and set it up, I believe - I can log into it.
So i think the next steps is to migrate any polices or stuff from my on premise traps install - seems like I can export and import stuff.
Then you are suggesting I can download something from my TMS to install on my machines that will automatically repoint them to the new location
Cool.
I used to send my logs to my panorama box is there any way to do that from TMS back into my panorama on premise
07-03-2019 07:48 PM - edited 07-03-2019 09:24 PM
@BPry Do you know of any document that outlines the best practise setup for TMS. I am having issues exporting the current config from my EMS, so I am thinking I might redo the polices - wouldn't mind basing it upon what PA consider best practise
Go an upgrade package - how can I install the uninstall password so that the upgrade can happen without user intervention
07-04-2019 07:29 PM
The configuration doesn't match, so you'll need to re-create your policy in TMS and can only utilize the EMS configuration as a baseline to what you need to make for TMS. Youll then want to ensure that your agents have been upgraded to the latest release to ensure that the migration goes smoothly.
When you generate the package on TMS you'll actually deploy that package through EMS, just be sure you've disabled service protection for the agents you're upgrading.
You can find the guide within the TMS admin guide as far as how you would perform the upgrade step by step.
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!