Reworking the SEP documentation
Created: 13 Aug 2013 • Updated: 02 Jun 2014 | 14 comments
We are just about to start a project internally to look at how the SEP documentation is delivered. One thought that we had was to focus it on "jobs" that our customers are trying to achieve, an example of this might be "How do I give different access levels to different administrators in my organization, and in my customers' organizations" which would result in a walkthrough of conifguring administrators, domains, domain admins, limited admins, etc.
What are your thoughts to this? Can you think of any questions or queries like this that you have had in your time working with SEP that might help others if we were to build documentation around them?
Some more examples:
How do I keep my employees safe and secure at remote offices:
• Over high bandwidth network
• Over low bandwidth network
How do I keep my offices safe, and comply with European Union privacy regulations
How can I use a single SEP server to manage multiple groups of users, or multiple customers, while keeping their data segmented and allowing group or customer administrators to see and manage their own machines.
Discussion Filed Under:
Security, Endpoint Protection (AntiVirus), Agents, Backing Up, Basics, Best Practice, Beta, Case Study, Certification, Cloud Computing, Compatibility, Configuring, Documentation, Downloads, Error messages, Evaluating, Features, Installing, Integration, Layer Definition File, Licensing, Managing Backup Devices, Monitoring, News, Patch, Performance, Recovering, Reporting, Restore, Roadmap, Rules, Tip/How to, Training, Troubleshooting, Uninstall, Upgrade, Virtualization, Not Applicable