![]() There’s a lot more work that needs to be done to make it useful, but to be totally frank, admin privileges are complex due to the variety of needs and the destructive ability if every abused, misused or through ignorance, so it’s not super easy on purpose. Admin privileges has grown over the years to what we have today. THEN, that per-mutates down to sites with a hole other set of permissions as we support site only admins for when/if you have a user that JUST needs to manage/see just one site.Īs an aside, the entire console is being redesigned to offer streamlined UI for these kinds of settings & needs. Super vs Limited show/allow high level sections and if not visible, then that user/tech can’t modify things, like policy and/or overrides at a global level. There are many customers that have different admins for different needs, like helpdesk, NOC techs, administrators, site only admins, specific customer admins, so the UI and settings are for a variety of needs. ![]() Then, the site admin view/admin per user, per site is for the same. The different settings, Admin type (Super vs Limited) are for specific use cases. offered good suggestions for using Unmanaged policy over turning on “Shutdown protection”, beyond the ability to modify/admin policies, sites, settings. I’ve been heads down all day on another project and didn’t get a chance to jump in earlier. If you guys need a full walk through of best practices and help with managing your console, you can private message me here or email me at I’ll have someone on my team reach out to get that - looks like you figured it out. Once you have admin privileges to make these changes, you can make as many custom policies as you’d like for specific use or to assign to various endpoints. If not, the administrator can reset them and/or setup your permissions site by site. I noticed at one point you’d mentioned this was a multi-site console, so if you’re log in is established as a GMS admin, check there to see if you have rights at the global level. If you could modify policies at the site level, you’d see the extra column to the right where you could make the respective change.Ĭheck with the main console administrator to change your permissions. See Create/Delte/Rename etc… these are admin options. If you had admin privileges, you’d see the following buttons along the top. However, these screen shots indicate you do not have admin privileges to make a policy or modify a policy at the site level. A reply from Support should take from 24 to 48 hours but could take a little longer because of COVID 19 and the Webroot Employees are busy working from It does look like that redacted site policy may be a custom policy assigned to all of the endpoints, which you should be able to duplicate and modify for single use or what you’re trying to accomplish. Putting in another Support Ticket on this problem before Support responses will put your first Support Ticket at the end of the queue. Note: When submitting a Support Ticket, Please wait for a response from Support. You can also Submit a Support Ticket and the Support Team will assist you free of charge: For 64bit Operating Systems: "C:\Program Files (x86)\Webroot\WRSA.exe" –pollįor more information on editing policies, please see the user guide.For 32bit Operating Systems: "C:\Program Files\Webroot\WRSA.exe" -poll.Forcing the endpoint to poll by locally or remotely executing a wrsa –poll command:.Right clicking the system tray icon and selecting ‘Refresh Configuration’. ![]() You can force the endpoints to check in by: **NOTE: Policy changes will be applied during the polling interval set for the policy.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |