![]() Then in that policy, I changed the setting under User Interface > GUI from Hide to Show. To fix, I copied the Recommended Defaults policy, which I renamed as “Permissive Defaults”. From there, you can click Policies and can see what the default policy is (small white flag in the leftmost column). I finally figured out that by clicking the “Endpoint Protection Console” link on the dashboard of the new Management Console (within the Endpoint Protection summary box at top-left), it takes you to the OLD Management Console experience. It appears the new Management Console doesn’t show what the default policy is, and doesn’t present any option to change it. I ran into the same problem and it took me a while to figure out how to fix. I really need some help as we are on a deadline and have to choose between Webroot and BitDefender by Friday. These are in different locations so I know it isn’t a FW blocking a port or something to that effect. They both *seem* to install, but none of them actually check-in properly. I have tried that version on 11.6 Mac OS and 12.1 today. All of my PCs are in there without any problems. We circle back and grant the full disk access but the Mac endpoints are not showing up in my webroot console. The user doesn’t get to provide full disk access during the initial install. I have a handful of 11.6 Mac OS, some 12.1 and am using the latest version provided by Webroot ( 9.4.1.27/WSAMAC.dmg) yet they all fail at the same place. We have different versions throughout the organization and NONE of them are working properly. So we recently partnered with Atera who provides webroot 1click installs on PCs, but Webroot installs on Mac machines is VERY problematic.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |