Skip to the content of the web site.

Nexus: Policies, Standards and Procedures

Managing Windows PC in Nexus

Introduction

Windows PC management is complicated and managed by many IT groups on campus. What IST has been focussing on is what we believe to be the hard part, and that is to set up an infrastructure that all can leverage to do their daily work. This includes IT administrators responsible for collections of staff and lab PCs. It also means clients that manage their own PCs, and everything in between.

What we have done is built a Microsoft System Center Configuration Manager (SCCM) server, with an inventory of all PCs in Nexus that also have an IP address in DNS. That is then divided into collections, as determined by appropriate IT staff, and "management" happens as desired to those PCs.

Delegation of control is defined, like it was in Active Directory, and the people responsible for the PCs are the ones determining what happens to them. Individual clients benefit by having their administrators define what it is they should have access to, and software is advertised appropriately for either an automated install at a predetermined time, or the client installs it themselves. No administrative credentials are required by the client to perform these tasks.

SCCM can also do a LOT more. A short list is provided below:

  • Other than Software distribution, SCCM can and is being used for:
  • Patch Management
  • Hardware Inventory
  • Software Inventory
  • Operating System deployments
  • Configuration Management
  • Adaptive Application Delivery (Measure success/failure of scheduled delivery)
  • Endpoint Security Management (SCEP)
  • Client Infrastructure Monitoring
  • Remote PC Diagnosis and Repair
  • Power Management
  • It can even manage Macs, Unix boxes and Mobile Devices, if desired (but we're not)

More links will be provided in this space over time to address all of these pieces as time goes on.

Document maintained by: Manfred Grisebach                Last modified: March, 2015