This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Migrating from vShield to Sophos for Virtual Environments.

Hi,

What is the best way to migrate from Sophos/vShield to Sophos for Virtual Environments with VMs being unprotected for the minimum amount of time?

Is there much impact if a VM has the SVE guest agent installed while on a VMware host with a vShield SSVM on it?

I was wondering if we could have the vShield SSVM and the SVE VM both running on each host then install the SVE agent to VMs when we get the chance to migrate them from vShield to SVE?

thanks



This thread was automatically locked due to age.
Parents
  • Hello  

    There is a section in the Startup guides, for both SEC and Central management consoles, to help migrate from SAV for vShield to SVE (look at in the contents for Migrate to Sophos for Virtual Environments)

    https://www.sophos.com/en-us/support/documentation/sophos-for-virtual-environments.aspx 

     

    You can have a host with both SAV for vShield SVM and the newer SVE SVM. You can then start to add the new thin agent to the GVMs and remove SAV for vShield. Once you are happy with the process you can deploy the thin agent via AD for instance to the rest of your GVMs. Then you can uninstall SAV for vShield SVM. 

    thanks 

    Mark 

  • Thanks,

    The documentation says to shut down the old ssvm before installing the guest agent which is why I was worried there might be issues having both active:

    To migrate:
    1. Install a Security VM.
    Note: This new Security VM can be on the same host as an existing SAV vShield Security
    VM.
    2. Go to your management console and verify that the Security VM is successfully updating.
    3. Shut down the old Security VM or uninstall your old anti-virus software.
    Caution: Your guest VMs will become unprotected so please ensure their security.
    4. Install the new lightweight Sophos Guest VM Agent.

  • Yes you will have to shut down SAV for vShield on the GVMs 1st. The new thin installer takes less than a minute to install so downtime is minimal. 

  • I didn't mean shutting down the client on the Guest VMs. My understanding of the migration guide was that the vShield Security VMs needed to be shut down before the new guest agent was installed so all of the VMs on that host would be unprotected until they had the new agent installed.

Reply
  • I didn't mean shutting down the client on the Guest VMs. My understanding of the migration guide was that the vShield Security VMs needed to be shut down before the new guest agent was installed so all of the VMs on that host would be unprotected until they had the new agent installed.

Children