VirusScan 8.8 and ENS can co-exist with each other. The ENS Migration Assistant helps you to position your VSE policies into an ENS environment. You have two scenarios for the migration assistant, automatic or manual. If you choose automatic your VSE policies will automatically be converted and assigned to the same locations your VSE policies are assigned to. The choice for a manual migration means you will hand hold the procedure for the policy process. The official position is that a few hundred machines is what they want you to target for an automatic decision. The policies will either convert or not due to complexities. Complexities would mean syntax, duplicate entries etc.
I have migrated node counts in your range without issue. If the automatic runs successfully your in pretty good shape. If it fails you will have to clean up your policies anyways.
first sentence is most important for me :-)
Do you agree that I can run the Migration assistant, and afterwords
-> manage one single machine with ENS installed +
-> manage all other machines with VSE installed
... with the same ePO 5.3.2 Server?
Do you agree that my existing VSE policies will not be removed when creating the new ENS policies with the Migration assistant?
sorry for rephrasing the same question again, but there is no public info on this Scenario - wherever Migration to ENS is discussed or explained, one cannot determine if the old VSE policies are still valid and in use.
2 of 2 people found this helpful
i have currently 4200 VSE / HIPS / SAE computers man,aged by my main ePO and also 4800 ENS computer Inside it.
Really not a problem. You just need to find the best way to manage your environment. In my case, a single tag when assigned on a computer launch the ENS migration
Thank you very much!
what about in the case of ENS and HIPS in ePO 5.3 ?