2020. 1. 31. 20:52ㆍ카테고리 없음
Hi, I just finished up getting this to run well on my Windows 8 machine, now on my Macbook with Lion 10.7.5, The initial scan says it's scanning, but the Files scanned: Threats: Processes all stay at 0 and the Time elapsed just continues to climb. Also in my dashboard it says 3 PC's protected but the Macbook does not show up there.
In the My Account section, under status it says Waiting for license even though I have input the license key successfully. The only way to exit the program is to kill it out of activity monitor. Clicking on the icon in the system try to kill it does not work.
Solved: Hope I am on the correct location for this post. With MacOS Sierra coming out soon, is there a centrify directcontrol agent coming out soon. Nov 4, 2016 - Solution: There are agents for multiple OS due soon, but soon does not have an ETA, you should be able to scan macs without though.
There is no context menu choice to scan items either. So it sounded like a broken install at that point, so removed it and tried to reinstall. That failed with the same behavior. Then I REINSTALLED LION and updated it to 10.7.5 and it still happens. @DavidP wrote: Hello Shady! The WSA product for MAC is a bit different than the one for Windows.
Ths is due to the fact that Apple refuses to admit MAC's can be vulnerable to malware and so they refuse to allow AV 'scanning software'. WSA for MAC does have a few features to keep your MAC safe, but it does not have a scan function as a result. That might help a little bit. So, wait a minute. I got this as a complete security package but it doesn't even have on demand scanning for Mac OSX? I kind of don't believe it because either A) Why are you selling the product? Regardless of Apple's take on AV's if your service doesn't work properly then thats on Webroot B) The FIRST THING it wants to do is run a system scan that never finishes.
If it doesn't work, then why is it even in there? I read the article you posted, but this program is behaving like a bad install (cant shut it down, cant uninstall it correctly). So are you guys saying that it isn't compatible with Macs? Wrote: @DavidP wrote: Hello Shady! The WSA product for MAC is a bit different than the one for Windows.
Ths is due to the fact that Apple refuses to admit MAC's can be vulnerable to malware and so they refuse to allow AV 'scanning software'. WSA for MAC does have a few features to keep your MAC safe, but it does not have a scan function as a result. That might help a little bit.
So, wait a minute. I got this as a complete security package but it doesn't even have on demand scanning for Mac OSX? I kind of don't believe it because either A) Why are you selling the product? Regardless of Apple's take on AV's if your service doesn't work properly then thats on Webroot B) The FIRST THING it wants to do is run a system scan that never finishes. If it doesn't work, then why is it even in there? I read the article you posted, but this program is behaving like a bad install (cant shut it down, cant uninstall it correctly). So are you guys saying that it isn't compatible with Macs?
Not owning a MAC, I am not as familiar with the installer. The MAC product does give protection, but not an actual on demand scanner that you think of in a PC antimalware software suite. I am guessing that the initial scan that it is trying to run is detecting settings and autoconfiguring for you MAC. If this is not completing correctly, it might be a problem that uninstalling and re-installing might help. If this does not work, consider filing a. @DavidP wrote: wrote: @DavidP wrote: Hello Shady! The WSA product for MAC is a bit different than the one for Windows.
Ths is due to the fact that Apple refuses to admit MAC's can be vulnerable to malware and so they refuse to allow AV 'scanning software'. WSA for MAC does have a few features to keep your MAC safe, but it does not have a scan function as a result.
That might help a little bit. So, wait a minute. I got this as a complete security package but it doesn't even have on demand scanning for Mac OSX? I kind of don't believe it because either A) Why are you selling the product?
Regardless of Apple's take on AV's if your service doesn't work properly then thats on Webroot B) The FIRST THING it wants to do is run a system scan that never finishes. If it doesn't work, then why is it even in there?
I read the article you posted, but this program is behaving like a bad install (cant shut it down, cant uninstall it correctly). So are you guys saying that it isn't compatible with Macs? Not owning a MAC, I am not as familiar with the installer. The MAC product does give protection, but not an actual on demand scanner that you think of in a PC antimalware software suite. I am guessing that the initial scan that it is trying to run is detecting settings and autoconfiguring for you MAC. If this is not completing correctly, it might be a problem that uninstalling and re-installing might help. If this does not work, consider filing a And since the initial scan never starts/finishes, the MAC does not show up on the secure anywhere dashboard.
I'm going to have to file a ticket I guess. Wrote: @DavidP wrote: wrote: @DavidP wrote: Hello Shady! The WSA product for MAC is a bit different than the one for Windows. Ths is due to the fact that Apple refuses to admit MAC's can be vulnerable to malware and so they refuse to allow AV 'scanning software'. WSA for MAC does have a few features to keep your MAC safe, but it does not have a scan function as a result. That might help a little bit.
So, wait a minute. I got this as a complete security package but it doesn't even have on demand scanning for Mac OSX? I kind of don't believe it because either A) Why are you selling the product? Regardless of Apple's take on AV's if your service doesn't work properly then thats on Webroot B) The FIRST THING it wants to do is run a system scan that never finishes.
If it doesn't work, then why is it even in there? I read the article you posted, but this program is behaving like a bad install (cant shut it down, cant uninstall it correctly).
So are you guys saying that it isn't compatible with Macs? Not owning a MAC, I am not as familiar with the installer. The MAC product does give protection, but not an actual on demand scanner that you think of in a PC antimalware software suite. I am guessing that the initial scan that it is trying to run is detecting settings and autoconfiguring for you MAC. If this is not completing correctly, it might be a problem that uninstalling and re-installing might help. If this does not work, consider filing a And since the initial scan never starts/finishes, the MAC does not show up on the secure anywhere dashboard.
I'm going to have to file a ticket I guess. MAC devices are not supposed to show up on the Console.
I was not happy with my own response, do I PM'd one of the MODS here on the Community. Here is his reply, including where I was incorrect 'Sorry for getting back to you a bit late on this. What you're saying is partly true, but not exactly. Here is the post that I think needs a bit of adjusting. 'The WSA product for MAC is a bit different than the one for Windows. This is due to the fact that Apple refuses to admit MAC's can be vulnerable to malware and so they refuse to allow AV 'scanning software'.
WSA for MAC does have a few features to keep your MAC safe, but it does not have a scan function as a result. That might help a little bit.' I think this post would be a great way to phrase the Android vs. IOS protection, but it's not exactly the same for OSX. While WSA for Mac will not currently show up in the My Webroot Account, the program itself does indeed scan the Mac computer it is installed on.
I have WSA installed on my Mac and I use it on a regular basis. That said, the Mac product is not nearly as feature rich or customizable as the Windows product, but this is mainly because there a just not nearly as many threats for Mac. That said, we are currently working on adding new features and improving the Mac client. Going back to Shady's issue, however, something is definitely not working properly as it sounds like the scan is initiating, but not actually scanning any files.
A support ticket would definitely be best in this case, but I think you should rephrase that post to acknowledge that the Mac won't currently show up in the console and that it indeed sounds like a scan issue that needs further analysis.' No worries, DavidP! Thanks for jumping in on the thread and providing some great input. I'm just here to clear up a couple of things about the Mac product. Shady-David is absolutely right that the Mac product is a bit different. As of right now, your Mac will not show up in the 'PC Security' portion of your My Webroot account alongside your PC's. This is a feature we're currently working on inplementing.
That aside, SecureAnywhere for Mac is indeed an antivirus program that scans and protects your Mac from threats. While it doesn't scan automatically like the Windows program, it will work much the same way in letting you know if you're clicking on a malicious website and will notifty you if it detects a threat. Likewise, you can always open SecureAnywhere on your Mac and run a manual scan. On that note, our developers are constantly working to add features and make improvements to the Mac client just as they're doing for the Windows product.
Based on your description, it's clear that there is indeed an issue at hand-it sounds like the scans are initiating, but not progressing to scan your computer. DavidP is correct that best way to go about the issue is to submit a support ticket (which it sounds like you have done). Please update the thread and let us know if you have any questions and/or if a support agent has helped you get this issue resolved!
Recent updates to this article Date Update September 6, 2018 Removed link to article KB83696 (ePO 5.1.x end of life). August 21, 2018 Added reference 1225305. June 18, 2018 Added details for reference 1128232 and 1159984.
Grouped solutions and expected behavior together. March 7, 2018 Updated to add expand/collapse titles. September 27, 2017 Added information about a known issue with reference number 1211288.
MA Version Release Date Release Notes MA 5.0.6 July 11, 2017 MA 5.0.5 March 28, 2017 MA 5.0.4 August 11, 2016 MA 5.0.3 May 9, 2016 MA 5.0.2 August 31, 2015 MA 5.0.1 June 16, 2015 MA 5.0.0 October 21, 2014 NOTE: Any future product functionality or releases mentioned in the Knowledge Base are intended to outline our general product direction and should not be relied on, either as a commitment, or when making a purchasing decision. IMPORTANT:McAfee Agent 5.5.x supersedes McAfee Agent 5.0.x. To view the MA 5.5.x Known Issues, see. Contents Click to expand the section you want to view. Critical known issues Reference Number Related Article Found In Fixed In Issue Description 1225305 5.0.0 5.5.1 Issue: The McAfee Agent service masvc stops working (system crash) intermittently.
The issue is seen on systems where tasks are scheduled at a system restart. 1201012 - 5.0.5 5.0.6 Issue: If a group policy for system shutdown is enabled on Windows operating systems, MA fails to exit McTray.exe and prompts the UI to shut down the service manually. 1211288 - 5.0.x 5.0.6 Hotfix 1211288 Issue: McAfee Agent 5.0.x services fail to start on Mac OS X 'High Sierra' (10.13).
1153407 5.0.4 Host IPS 8.0 update 8 Hotfix 11153407 Or Host IPS 8.0 update 8 Issue: When you install any McAfee product that includes SysCore 15.5, such as McAfee Agent 5.0.4, it breaks the trust in Host Intrusion Prevention (Host IPS) 8.0 updates 5–7. Workaround: To avoid the issue, upgrade to Host IPS 8.0 update 8 before installing McAfee Agent 5.0.4 or later. See the related article for details. 1151125 5.0.3 5.0.5 Issue: McAfee Agent communication with the McAfee ePO server fails intermittently with a curl error or curl error, and the client connections are in a FINWAIT2 state on the McAfee ePO server. Workaround: Change the KeepAlive setting to Off in the httpd.conf file on McAfee ePO server and Remote Agent Handlers. 1099913 5.0.2 5.0.3 Issue: Bug check failures occur on startup for systems with non-uniform memory access (NUMA) processors.
Workaround: Revert to a previous version of the agent. 1085179 5.0.0 5.0.3 Issue: McAfee Agent 5.0.x operations fail when OS X is upgraded from Yosemite/Mavericks/Mountain Lion to El Capitan. Workaround: Upgrade to McAfee Agent 5.0.2 Hotfix 1085179 before upgrading the operating system to El Capitan. 1104711 5.0.0 5.0.3 Issue: When McAfee Active Response (MAR) is installed on a system where Ad-Aware Web Companion is also installed, the MAR service (MARService.exe) fails to start. Workaround: Uninstall Ad-Aware Web Companion.
5.0.0 5.0.1 Issue: Agent-server communication over a non-secure (SSL) agent-server port is not supported with McAfee Agent 5.0.0. 5.0.0 5.0.1. Issue: Upgrading to McAfee Agent 5.0.0 is not supported on Linux operating systems with McAfee Application Control installed. 978603 5.0.0 5.0.0.481 Issue: You observe high CPU utilization for the McAfee Agent (CMA) process on non-Windows clients after upgrading to ePO 5.1.1 when 'All packages' is used in a McAfee Agent update task.
988214 5.0.0 Host IPS 8.0 P5 Issue: Host Intrusion Prevention 8.0 update 4 or earlier and McAfee Agent 5.0.x have client compatibility issues on Windows and Linux systems. 1031482 - 5.0.1 n/a Issue: Update fails on a Windows XP Embedded operating system. Resolution: If the Null Device Driver component is missing, the McScript start from the McAfee Agent service might fail.
Ensure that the Null Device Driver is installed before agent installation. 989030 5.0.0 n/a Issue: A blue screen error occurs during McAfee Agent 5.x installation on Kaspersky Endpoint Security 10 for Windows clients. Resolution: Remove Kaspersky Endpoint Security 10 for Windows before installing McAfee Agent 5.x.
See the related article for details. Non-critical known issues Reference Number Related Article Found In Fixed In Issue Description 1174812 - 5.0.4 5.0.4 Hotfix 1179191 Issue: The AutoUpdate Repository List in the VirusScan Enterprise console shows a multi-byte repository name with garbled characters. 1161103 5.0.4 ENS 10.5.0 Issue: System restore fails with an 'access denied' message if Endpoint Security, McAfee Agent, or VirusScan Enterprise is installed. 1153218 5.0.2 SysCore 15.4 and later ENS 10.2.1 ENS 10.2.0 Hotfix 1164434 Host IPS 8.0 P9 VSE 8.8.0 P9 Issue: Installing or upgrading to McAfee Agent 5.0.2 and later results in intermediate certificates being installed in the wrong certificate store, potentially causing problems on some IIS servers.
IIS servers reject non-self-signed certificates in the Trusted Root Certification Authorities. Workaround: See the related article for more details.
1031221 - 5.0.1 5.0.5 Issue: McAfee Agent sets an incorrect runtime for a task set with a missed policy if you change the system time to a later date. 991229 5.0.0 5.0.5. Failed to load props.xml file Modify agent props failed! Workaround: See the related article.
1123973 5.0.0 5.0.4 Issue: On Windows operating systems, if the Power Service is disabled, a McAfee Agent installation will time out and McAfee Agent will not operate correctly after installation in the following two scenarios:. Scenario 1: Upgrade to McAfee Agent 5.0.x.
Scenario 2: Uninstall of McAfee Agent 5.0.x already in a bad state and attempt to upgrade to McAfee Agent 5.0.x Workaround: Uninstall the existing McAfee Agent 5.0.x and install McAfee Agent 5.0.4. See the related article for details. NOTE: This issue does not occur on systems with the Power Service disabled before a fresh installation of McAfee Agent 5.0.4.
1080143 5.0.1 5.0.3 Issue: McAfee Agent 5.0.1 performs agent-server communications every few seconds when some third-party security products are installed.5.0.1 5.0.3 Issue: The McAfee Agent 5.0.1 Product Guide mentions the use of command-line parameters maconfig -stop and maconfig -start on page 44. These command-line options are not supported in McAfee Agent 5.0.1 and later.
Resolution: This issue is corrected in the McAfee Agent 5.0.3 Product Guide. 10711 5.0.0 5.0.2 Hotfix 1110392 Issue: Upgrading McAfee Agent from version 4.x/5.0.x to version 5.0.x fails in the presence of VSE 8.8.0 Hotfix 1087536 and VSE 8.8 update 7 and later. 1112739 - 5.0.2 Hotfix 1110392 5.0.3 and later Host IPS 8.0 P8 Issue: After installing McAfee Agent, the following error displays in the Host Intrusion Prevention notification area user interface. Workaround: Manually restart the McAfee Host Intrusion Prevention service or reboot the system after the McAfee Agent installation.
1108214 - 5.0.2 5.0.2 Hotfix 1110392 Issue: An agent wake-up call fails after upgrading to McAfee Agent 5.0.2 if Host Intrusion Prevention 8.0 update 7 is installed. 970854 - 5.0.1 VSE 8.8.0 P4 JTI Hotfix and VSE 8.8.0 P5 Issue: VSE 8.8.0 update 4 and earlier does not whitelist McAfee Agent executables.
Access Protection hits are generated for McAfee Agent executables such as masvc.exe, macompatsvc.exe, macmnsvc.exe, and maconfig.exe if VSE 8.8.0 update 4 and earlier versions are installed. 1065602 - 5.0.1 5.0.2 Issue: Automatic Update is triggered even though the deployment task has not deployed the product. 10626 5.0.0 5.0.2 Hotfix 1110392 Issue: Event generation fails with some McAfee Products when McAfee Agent 5.0.x and VSE 8.8 update 7 and later or Hotfix 1087536 are installed. Some affected products are. Issue: Deployment tasks configured to deploy a specific version of McAfee Agent install a different, later version of McAfee Agent when you overwrite the agent package. 967081 5.0.0 5.0.1 Issue: Documentation errors in the McAfee Agent 5.0.0 Product Guide.
1016628 - 5.0.0 ePO 5.1.2 Issue: Policies are not enforced for any managed products after upgrading the client to McAfee Agent 5.0. 1108985 5.0.0 ePO 5.3.2 and ePO 5.1.4 Issue: McAfee Agent deployment fails to non-Windows systems running recent versions of SSH-server. Workaround: Manually replace the PSCP executable that ePO uses to initiate the file transfer.
See the related article for details. 988097 5.0.0 DLPe 9.3 Update 3 Hotfix 12 Issue: McAfee DLP Endpoint does not display in McAfee Agent 5.0 Managed Features. 5.0.0 n/a Issue: McAfee Agent or ePO installation fails with the following error when KB3072630 is installed. Resolution: Verify that Microsoft Windows updates KB3072630 and KB3139923 are both present and installed on the impacted system. See the related article for details. 1181853 - 5.0.4 n/a Issue: The macOS computer hangs and McAfee Agent does not respond for about five minutes when the following conditions occur in the listed order:. You enable Endpoint Security for Mac (ENSM) Threat Prevention On-Access Scan (OAS).
You upgrade to macOS to version 10.12.3. You upgrade McAfee Agent. Resolution: The McAfee Agent process, Macompatsvc, takes time to start if ENSM Threat Prevention OAS is enabled. Wait for the McAfee Agent process to start after the operating system upgrade completes before you upgrade McAfee Agent. 5.0.2 Hotfix 1110392 5.0.3 and later n/a Issue: After performing the following installation sequence, the system will be vulnerable to the trusted access bypass vulnerability described in after upgrading McAfee Agent:. Install McAfee Agent 4.8.x and Host Intrusion Prevention 8.x or Data Loss Prevention Endpoint 9.x (or both) on the client.
Upgrade McAfee Agent to 5.0.2 Hotfix 1110392 or 5.0.3 (and later). Workaround: Restart the system after upgrading McAfee Agent to completely mitigate the trusted access bypass vulnerability in this scenario. See the related article for details. 1131469 - 5.0.3 n/a Issue: If you change the system time multiple times, the next agent-server communication interval (ASCI) time value is printed incorrectly in the McAfee Agent Status Monitor. The ASCI is unaffected.
Workaround: On the next scheduled ASCI, the time value is corrected automatically. 1109811 - 5.0.2 Hotfix 1110392 5.0.3 and later n/a Issue: McAfee Agent 5.0.2 Hotfix 1110392 and later, which uses SysCore 15.4.0.773 and later, fails to install on Windows 7 operating systems.
Workaround: Install the Microsoft fix documented in before the McAfee Agent installation.5.0.0 n/a Issue: The following status displays in agent monitor. Agent service is now stopped Cause: The McAfee Agent Backwards Compatibility Service state is getting changed from manual to automatic after a reboot by a group policy applied on clients that had McAfee Agent 4.x.x. NOTE: This issue also occurs fresh installations of McAfee Agent 5.x when a Group Policy is set to enable McAfee services, or any other third-party application doing the same action.
Workaround: Disable the group-level policy on systems running McAfee Agent 5.0.0 and later because these McAfee Agent versions have an automatic recovery mechanism when stopped unexpectedly. 5.0.0 n/a Issue: A compatibility issue exists with third-party 'hooking' applications when SysCore 15.3 is installed. Resolution: See the related article for details.
1014169 - 5.0.0 n/a Issue: A client task that is scheduled to Run Now runs indefinitely on upgrade of McAfee Agent from 4.8.0 update 1/Patch 2/Patch 3 to McAfee Agent 5.0.x even though the upgrade is successful. Resolution: McAfee Agent 5.0.0 and later handle the Run Now task by design. This issue does not occur in upgrades from McAfee Agent 5.0.0 to McAfee Agent 5.x.x.
972679 5.0.0 n/a. Resolution: These options were intentionally removed. See the related article for details. Under Investigation 11232 5.0.0 - Issue: On non-Windows systems, McAfee Agent 5.x is unable to listen for wake-up calls on ports lower than 1024. Workaround: See the related article for details. 1155972 - 5.0.5 - Issue: When the McAfee Agent mode is changed from managed to self-managed on Windows operating systems, EpoServerLastUsed and LastASCTime registry keys still contain managed information.
Solved: Agent For Mac Download
1175956 5.0.5 - Issue: VirusScan Enterprise 8.8.0 update 4 and earlier do not whitelist McAfee Agent executables. Access Protection hits are generated for masvc.exe if VSE 8.8.0 update 4 and earlier versions are installed. Resolution: See article for more details. 1174728 - 5.0.4 - Issue: Tasks are scheduled beyond the 'until' time if:. The task is set to 'repeat until' a specific date and time.
The clock shifts one hour ahead of the actual time because of Daylight Saving Time (DST) shifts the clock one hour ahead of the actual time. 1172436 5.0.4 - Issue: The IP address shown for some systems in ePO is all zeros (0:0:0:0:0:0:0:0). Workaround: If possible, limit the number of IP addresses being used by the affected systems to nine or fewer IP addresses. 1168133 - 5.0.2 - Issue: If system time is changed while a task is in progress, the task is immediately freed up. 1077826 5.0.2 - Issue: Upgrade of McAfee Agent to version 5.0.x fails if the Prevent Programs Registering as a Service rule is blocked in the Access protection policy of VirusScan Enterprise. Workaround: Disable the Prevent Programs Registering as a Service rule in the Access Protection policy for VirusScan Enterprise, then retry the upgrade. See the related article for details.
1029656 - 5.0.1 - Issue: A missed task does not execute if the task is scheduled to run repeatedly. 1024771 - 5.0.1 - Issue: Messages in Agent Monitor are not logged sequentially. 982072 - 5.0.1 - Issue: Customized policies are not enforced on clients while McAfee Agent is switched between modes.
1135834 - 5.0.1 - Issue: Policy changes are not applied as designed until the user logs on again or reboots the system for the Security Innovation Alliance partner product Avecto DefendPoint. Microsoft Active Directory domain user accounts are affected, but Windows local user accounts are not, as policy updates still occur live. 1070435 5.0.1. Resolution: Run the Microsoft MSIZAP (msizap.exe) tool to remove the remnants of McAfee Agent 4.x.x. See the related article for details.
1067653 - 5.0.1 - Issue: A duplicate node entry is created for a Linux system if you upgrade from McAfee Agent 5.x.x to McAfee Agent 5.x.x using McAfee Smart Installer. Workaround: If you notice duplicate entries, schedule a server task to identify duplicate entries and delete the inactive node. See the ePolicy Orchestrator Product Guide for instructions to schedule a server task. 1060850 - 5.0.1 - Issue: McAfee Agent fails to schedule the on-demand scan task post upgrade when VirusScan Enterprise is present. Workaround: After restarting the system, McAfee Agent schedules the task successfully. 1044276 5.0.1 - Issue: The McAfee Agent Backwards Compatibility Service is not be protected by VirusScan Enterprise if the agent's self-protection policy is disabled.
Resolution: To protect McAfee Agent Backwards Compatibility Service, always enable the self-protection policy for McAfee Agent. 1040305 - 5.0.1 - Issue: Agent deployment tasks download the FrameworkConfig.zip and FrameworkInstall.zip files even though they are not used by agent deployment tasks. 1035603 - 5.0.1 - Issue: Intermittently, McAfee Agent on Mac OS X fails to collect and send properties to the McAfee ePO server. Resolution: On the next agent wake-up call, McAfee Agent will collect and send the latest properties to the McAfee ePO server.
1031325 - 5.0.1 - Issue: The next runtime of a task is not recalculated despite changing the randomization interval value for a local task. 953245 5.0.0 - Issue: A Program Compatibility Assistant pop-up window displays when closing SmartInstaller.exe installation windows for McAfee Agent 5.x on Windows 7. Issue: Incorrect system properties operating system Build Number, Total disk space, Used disk space, and Free System Drive Space are displayed in ePO for non-Windows systems. See the related article for details. 934776 - 5.0.0 - Issue: When you compare client tasks in ePO, the output displays string IDs instead of the actual strings.
818917 - 5.0.0 - Issue: McAfee Agent upgrade from 4.6.x is unsuccessful on some Windows XP SP3 32-bit systems when Avecto Privilege Guard is installed and a reboot has not occurred since the Privilege Guard installation. Workaround: Avecto Privilege Guard recommends a restart of the system after installation. Restarting Avecto Privilege Guard allows a successful McAfee Agent upgrade. N/a - not applicable. Resolution did not require an MA-specific solution.