Chapter 6. Configuring ConfigMgr clients
The Configuration Manager client—the software package you deployed in chapter 4—is a powerful piece of kit, ready to help you in your daily administrative efforts. Once installed, it will regularly talk back to its assigned ConfigMgr management point, which is a site server role that acts as the main communication point between the ConfigMgr client and the ConfigMgr site server, checking whether there’s anything new it needs to be aware of. Welcome to the world of client policy.
Imagine that you want to enable your first-level help-desk operatives to remotely connect to a user’s machine in order to assist them with a support call; that’s something that you would use a client policy for. Now let’s say that a subset of your user base (such as senior managers) doesn’t want help-desk operators to be able to remotely connect to their machines. In this scenario, you’d use granular client policies, making sure that only the right policies are applied to the right users and devices, reflecting the needs of your organization.
As shown in figure 6.1, in this chapter you’ll look at the default policy options that every ConfigMgr client receives when it’s first installed, how that policy is received and updated, how to modify the default policy, and how to create and deploy custom client policies.
Figure 6.1. This chapter is all about making your deployed ConfigMgr clients do exactly what you want them to.
