Chapter 21. Securing ConfigMgr
In a large organization, many people can use ConfigMgr at the same time for different tasks. For example, some people may be responsible for deploying applications and patches to workstations, and a different team may be performing the same tasks for servers. One team may use ConfigMgr to connect remotely to managed workstations to support users, whereas another team may be responsible for the entire ConfigMgr hierarchy.
Often each member of all of these teams has the same level of internal access to ConfigMgr: Full Administrator. Why? Because it’s considered “easier” to give people more access than they need rather than work out what access they need and provide only that much. Easier, that is, until a desktop ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access