Webroot® Business Mobile Protection
- 35 Topics
- 101 Replies
I see that I have the same problem as everyone else who has the Samsung S22 Ultra cell. I can not load Webroot on my cell as there is a bug. The program works fine on my husband’s S19 and it worked fine on my S18. These are the 2 screens I get. Is there a resolution for this? It doesn’t do me much good to have antivirus protection on my tablet and laptop but not on my cell. HELP PLEASE! I tried to get this resolved with GeekSquad and they couldn’t resolve it either. This isn’t good that the latest, greatest cell update can’t get Webroot protection. PLEASE HELP!Here is the screen I get. When I click on GO, this is what I get.When I click on Learn More, I get an AW SNAP! screen. Then when I click on Reload I get the following message:“Something went wrong with Webroot. Webroot closed because this app has a bug. Try updating this app after its developer provides a fix for this error”. So DO WE HAVE A RESOLUTION YET?
This post is to remind customers that Webroot will end of life Webroot Business Mobile Protection on April 15, 2020. This change will not impact any consumer products, endpoint protection, or the BrightCloud® Mobile Security SDK used by Webroot technology partners. Only business mobile protection products will be affected. How will this impact you? The end of life notice for Webroot Business Mobile Protection has the following implications: Notification: As a follow up to the End of Life notification sent April 15, 2019, this email communication serves as a final notification of the end of life for the Webroot Business Mobile Protection product. End of Life: On April 15, 2020, the Webroot Business Mobile Protection product will be discontinued, and no further support will be provided. Additional Details: As a reminder, you are not able to renew your contract at this time and should take measures to deploy an alternative mobile protection product or service. You w
[h3][b]Important Webroot Product Announcement[/b][/h3] Webroot is announcing the end of sale and end of life for Webroot Business Mobile Protection, and due to the mobile protection end of life, we will no longer offer Webroot Business User Protection, with the mobile service closedown planned for [b]April 15, 2020[/b] (the “[b]end of life date[/b]”). [b]This change will not impact any consumer products or the BrightCloud® Mobile Security SDK used by Webroot technology partners.[/b] [b]How will this impact you?[/b] The end of sale and end of life notice for Business Mobile Protection will have the following implications: [b]Announcement:[/b] [list] [*]This announcement serves as a 30-day notification of the end of sale and end of life for the Business Mobile Protection product. [/list] [b]End of Sale:[/b] [list] [*]As of [b]May 15, 2019,[/b] no further sales or renewals will be accepted for Business Mobile Protection. [/list] [b]End of Life:[/b] [list] [*]As of [b]
Hi, I installed Webroot SecurAnyhere (WSA, 5 units) on another mobile phone. The new device appeared in my WSA web console after some minutes, but with the wrong phone number +491 (760) 000-0000 (just the country code +49 is ok, as I am located in Germany). Moreover, this wrong number was set in the mobile phone as primary number! So I tried to correct the number with "edit" in the web console, but even trying many formats, on saving I always end with the error message "No valid country code / No valid phone number". I tried formats using - , paranthesis, spaces, entering the country code in the first field etc etc.... nothing worked. Astonishingly the number for another phone, defined earlier, works (e.g. I can remote lock the phone), but when I try to edit (formally) and save the same number by new, I get the same error message. --> Can anybody help me how to enter /correct phone numbers in the WSA console? (there are two entry fields: when do I have to use the first filed?
[b]Mobile Protection Updates[/b] On March 15, Google will release version 66 of the Chrome browser to beta testers. They expect a public release date of April 17. We are working toward full compatibility. However, the Webroot mobile device management console is not yet supported for Chrome v.66. In the interim, we recommend you use a different browser to manage mobile devices.
Hi, It's time to decide whether or not to renew my WebRoot mobile licenses, and I am undecided on whether or not to find an alternative. Unlike the desktop app, the mobile app has been less reliable in my one year experience with a handful of devices. What is the current state of the Apple app? Last I checked it constantly shutdown, or was shutdown by iOS to save battery power, and required a reboot of the phone to restart. Is that still the case? For anyone else on the community using WebRoot Mobile protection, what has your experience been like? Thanks, Bill
I am running Webroot SecureAnywhere Mobile Business Security version 220.127.116.1136 on my Droid Turbo android version 6.0.1. Yesterday I noticed a message stating "Secure Web Browing disabled." I have tried several times to enable Secure Web Browsing, even turning my phone off and on several times; but cannot enable Secure Web Browsing. Please help!
I have a handful of users on Mobile Protection, only two of whom have an iOS device. In the portal, the iOS devices go amber and report "WebRoot iOS agent is not running". The app on the phone, however, reports the phone is protected and all is okay. According to WebRoot support, after a period of time, iOS will stop the app from communicating, presumably for performance or battery life considerations. Even then, the app appears to be running normally on the phone. Also according to WebRoot support, when the agent is not reporting into the portal, the Scream and Location features are not available, though the other features are (Lock, Wipe, Password). The suggested remedy is to have users open the app daily, or restart the phone daily, to keep the app communicating. I view this solution as lacking, and wonder about the opinion of other WebRoot Business users on the iOS Mobile Protection agent. My clients are business owners with a lot on their plate. I
My organization uses Airwatch MDM. We are looking at deploying Webroot for desktop and mobile devices. I don't believe you can have 2 different MDMs on one IOS device. Is there a way to use Webroot IOS app with Airwatch MDM? Thank you.
Guys! I dont know why is this important point missing from your application regarding security of Mobile Android devices. I have signed up for Trial version from your website and tried testing it on our devices to see if security policy is really in favour of my company. Issue Details: Android version 5 and above. Android -> Settings -> Users -> Add User Or Profile. Once we change the user account from Owner to a guest account / or simply add another user, then, your application stops controling the device. Anybody who knows how to change this setting can deactivate your application easliy in few seconds. Do you have any alternative settings to do here which i might have missed?!?!?!
Your sales team set me up with Mobile protection console yesterday & I created a bed of testers so we can start looking out its useful ness. At this time only users with Androids (myself included) can get the app installed. There is no option for the Microsoft phones & Apple users are recieving this error: " The portal server is not correctly configured with a valid certificate needed to manage iOS devices. Please contact your administrator to resolve this issue. " I have emailed sales & opened up a ticket - neither have added any comments. - now I'm reading in the community board that apple won't allow it to install, puzzling me - why would sales be pushing this product if it won't install? Thanks for any assistance on this
Mobile protection doesn't read correct telephone number: it read SIM phone number, but real number is another: in Italy we have possibilities to do number portability from an operator to another. So it simply doesn't work. Only virus protection works fine, all others functions are not usable.
All, Why are iOS users wiht iPad's able to disable MDM? I am testing the applicatio non Android phones, iPhones, and iPads. It does not make sense that the app can be disabled. I do not see a way to block this by policy. Please advise. Thanks, Stefan Jones
i've been seeing issues where users will update to Lollipop and then the mobile protection will saturate 50% or more of battery time. The solution ended up being to uninstall the version of mobile client and update to the newer 3.6 and battery usage returns to normal. My question is: why isnt the client updating? or at least a warning that the client needs updating before installing Lollipop.