Symantec antivirus mr6

Rarely I see an advice for it or need to take a manual action, and it stills there, doing its good job. I recommend it, for sure! In our company we use it for all the employees. Our IT department has full control over adjustments of all the installations. Employees don't need to worry about scheduled scannings, updatings, fine tunning or anything else. Its pre installed on all the machines and is there to protect, not to disturb. Its awesome! What can be a pro in one hand, can also be a con in the other hand.

The way it works on client machines, by being configured by IT department and not locally may cause some troubles. You just can't set an action different than quarantine a suspect object. But we all know that sometimes it can be a bad judgment from the antivirus side, like a driver for Android that I needed to install and it was classified as unknown source and therefore didn't allowed me to proceed with installation.

At least an option to ignore the object could be better. Symantec is one of the toughest antivirus software's out there. I must say that this is by far one of the greatest enemies of Support and in case you want to be sure that something won't be changed in any possible way Firewall, incoming connections from some PC in general or files copied , make sure to get Symantec as you won't be disappointed while using it even a little bit and I can sign this as an agent who is working with it for a couple years so far.

This antivirus is so good, that it looks like an impossible obstacles sometimes on my work, as I keep encountering it daily while working on some of my Customers. It is easy to deploy, password protected if you are trying to uninstall it or stop it, you can't do it without password and provides user protection from almost anything, especially as it integrates and utilizes Windows Firewall and Virus Protection on Windows 10 for instance, to provide impenetrable wall for any attack. I can say that sometimes I don't like how tough this one is, as it is my daily job to make my software work fine with Symantec, but if Customer Administrator is not online, I am unable to do anything.

That's why I would recommend it to everyone out there, as I am battling it for a couple years so far and I know how good it is. Reasons for Switching to Symantec Endpoint Security. I used it for a couple years back and it was good, but I wanted to check some alternatives. Luca from Centro Computer SpA. Industry: Information Technology and Services. It is quite good, but the product cannot be completly compared to the competitors. RIch of a lot of funtionalities like app isolation, app control and a complete XDR console.

Use to be fantastic. But that was then. My, how things have changed. At the time, I found it to offer the best balance of effectiveness and efficiency.

Customers support was prompt and professional, and even after I fled the IT profession to preserve my sanity I kept SEP running on my own home computers. All was well until I upgraded to version 14, at which point everything pretty much went to hell. The only way for me to get through a scan was to limit the scans to known file types.

At which point they made it clear that they intended to keep me jumping through hoops indefinitely. I finally told them that their constant stream of emails demanding yet more logfiles constituted harassment, and I blocked them at my email gateway for extra protection. Great job, folks. All Posts. Search Our Blog. Get the latest about social engineering Subscribe to CyberheistNews. About Us. Free Tools. Contact Us Phone: Email: sales knowbe4.

Search Search. Using Registry Editor incorrectly can cause serious problems that require you to reinstall the operating system.

Citrix cannot guarantee that problems resulting from incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk, and always back up the Registry before you edit it. You create the exclusions in the layer, and they are processed in the image after it is published. This section explains how to layer antivirus software and configure major updates based on how you deploy the images.

This applies only to major updates. Daily updates for virus definitions are done no matter what type of image you deploy. In all cases, we recommend making a new version of the app layer when the antivirus software has a major update.

Once the layer has been updated, update all of the templates that use that antivirus app, and redeploy new images to take advantage of the changes in the antivirus software. If you are deploying images without elastic layering enabled, consider whether your images are non-persistent or persistent:.

If you are deploying images with elastic layering but no user layers, clear auto updates, since the machines are non-persistent and would be reverted on the reboot. Also, assign the antivirus layer to be deployed in the image and not loaded as an elastic layer, since the antivirus drivers must be loaded at boot time to function correctly.

When layers are assigned as elastic layers, they are only loaded once a user logs on to the machine, and therefore the drivers would not be present at boot time.

If you are deploying images with elastic layering and a full user layer or a User personalization layer , we recommend turning off auto updates. The machines are non-persistent desktops, so they revert when the user logs off.

There is also the extra consideration that if the users remain logged on to the machines for several days, the daily updates to the virus definition files may end up in user layers. For most antivirus software this is not a problem. But, if you find that the antivirus software is having some problems running, you may want to determine the directory where they store their definitions and consider adding a registry setting to force these files to reside on the non-persistent image, instead of in the user layer.

Make sure that these settings are done in a different layer than the antivirus app, because you would not want those settings to interfere with updates to the antivirus layer. On newly deployed desktops, enable the Caching option again, which can happen automatically through integration with AVG Remote Administrator.

This section explains how to deploy Kaspersky in a layer. See the Kaspersky documentation for more instructions about installing the software in a VDI environment.

The following versions of Kaspersky antivirus software have been tested by Citrix and are verified to work with App Layering:. Encryption with Kaspersky Kaspersky Before you deploy Kaspersky If you use the Kaspersky Administration Server to manage the desktop, install Kaspersky antivirus for Workstations and NetAgent on the Packaging Machine or a gold image.

If you do not plan to use the Kaspersky Administration Server, install Kaspersky antivirus for Workstations only on the Packaging Machine or the gold image. When you install the Kaspersky NetAgent, clear the selection for the start application during install option.

When you install the Kaspersky antivirus for Workstations in a stand-alone configuration, do not enable password protection for any of the administrative options. The password you type on the Packaging Machine or gold image does not work on the desktop after you deploy the software.

After you install the Kaspersky software on a PackagingMachine for App Layers or layer revisions , a system restart and desktop image rebuild is required. Add a value to the Unifltr service in the registry before you add Kaspersky Attempts to finalize Kaspersky for Virtualization Light Agent 3.

The failure occurs when layer integrity attempts to restart. Install the Kaspersky software on the Packaging Machine. When you mark the image, the Kaspersky Administration Server considers the clones of this image dynamic. When a clone is disabled, its information is automatically deleted from the database. For details, see the section of this article on Dynamic VDI support. Restart the Packaging Machine.

The Packaging Machine restarts normally. No intervention is necessary. When you deploy this layer, the desktops restart normally and the STOP message does not appear.

The Kaspersky NetAgent might not start when users log on to the desktop for the first time. This issue occurs when you assign the App Layer with the Kaspersky software to a desktop. Restart the desktop to start the NetAgent software. The following interoperability issues can occur on App Layering desktops that have Kaspersky antivirus software installed. The Windows Event Viewer can show the following error:. Then the NetAgent software starts correctly.

To fix this issue, restart the Kaspersky software. The Network Attack Blocker continues to run. The following versions of McAfee software have been tested by Citrix and are verified to work with App Layering:. If you use the ePolicy Orchestrator 5. Installation requirements to install McAfee antivirus on a gold image or App Layer are the same. You can also find the requirements for including the agent on an image in the McAfee ePO product guide.

This allows for the agent to deregister from ePO on shutdown, which in turn prevents duplicate host names from populating in the ePO console. For more about this requirement, see the McAfee KB See the McAfee documentation for the version of the software you are using for more information. Allow the McAfee Agent Updater to complete the update.

This step can take several minutes to complete. Use this procedure if you plan to use a layer to deploy the McAfee antivirus software on App Layering desktops. After completing the installation, the Packaging Machine is visible in the ePolicy Orchestrator System Tree systems list.

Otherwise, allow the McAfee Agent Updater to complete an update. Open the registry editor, go to the following key, and change the Start value from 0 to a 1 :. The following interoperability issues can occur on App Layering desktops with McAfee antivirus software installed.

If you configure the McAfee antivirus software to scan script files, there can be long delays when you open video files in Internet Explorer. When you try to open these files, the McAfee software and App Layering try to perform operations on these files at the same time.

This conflict causes a delay in running the video file. All other windows and applications continue to function normally. If you encounter this type of delay, wait for the video file to run. Eventually, the McAfee operation times out and the App Layering operation completes. This issue has no effect on the ability of the antivirus software to check the video files for viruses.

The Create Layer Wizard opens. View the current tasks in the App Layering management console. App Layering supports the following versions of Microsoft Security Essentials antivirus software:. Enable the Windows Update service, but do not use the Windows updates. The updates must remain disabled. The Update service startup type changes from Disabled to Manual.

Windows Updates are not enabled, which is an App Layering requirement. During installation, check services. If the Microsoft Security Essentials update fails on a desktop because Windows updates are disabled, try the following.

Before you start, create and activate your Sophos Cloud account, as described in the Sophos documentation. When the task status changes to Action Required, prepare your packaging machine according to the General Guidelines for deploying antivirus software. You can find this information at the beginning of this article.

The Sophos installer creates Groups and puts users into them.