Right-click the computer(s) that you want to upgrade, and select Actions > Upgrade Agent Software.In Deep Security Manager, go to Computers, and then:.Upgrade the agent from the Computers page For details, see Configure agent version control. What is considered 'out-of-date' is determined by version control rules you've set up. Click Upgrade Agent / Appliance Software to upgrade all out-of-date computers.The check is only performed against software that has been imported into Deep Security, not against software available from the Download Center. In the main pane, look under the Computers section to see whether any computers or virtual appliances are running agents for which upgrades are available.In Deep Security Manager, go to Administration > Updates > Software.Continue with Upgrade the agent from the Computers page or Upgrade the agent manually.In the alert, click Show Details and then click View all out-of-date computers.Ĭomputers appears, displaying all computers where Software Update Status is Out-of-Date.When a new agent software version is available, a message appears on Alerts. You are now ready to upgrade your agent using any of the methods described in this topic. There are no upgrade notes for AIX at this time. Next, review the platform-specific notes below and complete any advised tasks. For more information, see Agent package integrity check. When you upgrade the Deep Security Agent, Deep Security verifies your signature on Deep Security Agent to ensure that the software files have not changed since the time of signing. You must upgrade all relays before you begin upgrading agents, otherwise, upgrades may fail. Import the new agent package into the manager.Make a system restore point or VM snapshot of each agent. Back up the agent computers that you plan to upgrade.Deep Security 12 LTS (GA version or LTS updates).Deep Security 11 LTS (GA version or LTS updates).You can upgrade to Deep Security 20 from: Check that you're upgrading from a supported version.Upgrade the agent embedded on the virtual appliance automatically.Upgrade the agent from a scheduled task.Upgrade the agent from the Computers page.Upgrade the agent starting from an alert.Once you are happy to deploy to all clients you just need to un-tick this option and apply the changes.Software upgrades can be initiated through Deep Security Manager or a third-party deployment system. Those clients you do wish to run the latest version can be manually upgraded. This of course will depend on your setup – in my case I allowed a week. Now all we need to do is allow time for the policy change to progagate throughout the network to all OfficeScan agents. Select the tick box next to this option and then click to ‘Apply to All Agents’. ‘ OfficeScan agents can update components but not upgrade the agent program or deploy hot fixes‘ Click the ‘Other Settings’ tab, the option we need to configure is highlighted. Click the ‘Settings’ option and then select ‘Privileges and Other Settings’.Ī new browser window should open allowing us access to these configuration options. Now that we have the root object selected we can start configuring our policy options. Next we need to highlight the root OfficeScan object in the agent tree to ensure all clients receive the policy. As I can’t know what your policy layout is you may actually need to carry out this step differetly but I am going to assume a setup where the policy is being applied at the root level and inherited by all sub-clients. To do this select the ‘Agents’ menu and then chooose ‘Agent Management. If you try and rush ahead with the server side upgrade you may have agents which are running an old policy allowing them to upgrade.įirstly we need to logon to the OfficeScan web management console and modify our agent policy. I strongly recommend you make these changes and then allow a sensible amount of time for all agents to detect the change. In this post I will quickly cover how to disable the OfficeScan management server pushing automatic agent upgrades.įirstly we must consider the following BEFORE upgrading the server side – changes made on the server side will take time to propagate throughout the network. When it comes to a major upgrade I prefer to deploy to a small subset of clients for testing and gradually roll out to more departments over a period of time. Sometimes you want this, for example you might just be applying a minor hotfix or update which you want all clients to receive ASAP. Typically once the server side software has been upgraded it automatically begins to push out the new program version to all OfficeScan agents. I recently upgraded one of our Trend Micro OfficeScan management servers to the latest ‘XG’ (v12) version.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |