Primary Goals
- Standardization of hardware, services, etc. to provide a high level of baseline IT support to all our campus clients.
- Increase overall efficiency through process automation and enterprise management of multi-user computers.
- Increase the University’s information security posture through centralized management of multi-user computers.
- Fully standardize virtual deployment of software as the primary method on campus, recognizing that physical deployments will be marginalized as an exception.
Based on the findings of this working group, we have combined several categories and narrowed potential variances in the hopes of streamlining and standardizing approaches. The resulting three categories are Computer and Teaching Labs, Classrooms (GP and Non-GP), and Research Labs.
Computer & Teaching Lab Recommendations
We used the following definitions for categorizing rooms as computer and teaching labs.
Computer Lab — A generalized lab within a unit that is always available to students. The software used in this category is generalized to a unit and will include a significant number of applications.
Teaching Lab — A specialized computer lab used for teaching. These rooms may be open outside of class time and have a specific subset of applications based on the classes taught in that room. These computers may have specialized equipment attached as well.
Windows
Recommended Platform: Physical Thin Client with Virtual Machine
VMware Horizon can manage the entire support cycle of computer and teaching labs from image creation and deployment to patch management and updates. The ease of deployment and scaling makes this platform ideal for the potentially fluid landscape of computer and teaching labs. The centralized management also reduces the workload necessary for IT professionals.
Thin client terminals used to connect to remote virtual machines are typically a cost-effective solution, with a low entry price and significantly longer lifespan than a standard PC.
Mac
Recommended Platform: Physical Desktop
Macs cannot be virtualized on campus, thus the only option is a physical machine. Physical Mac labs are recommended in cases where desired software is only available for macOS, or when student education can be enhanced using a Mac computer lab. Macs have become the standard in many industries so providing them to students is important to their professional development.
Classroom (GP & Non-GP) Recommendations
We used the following definitions for categorizing rooms as General Purpose (GP) and Non-GP classrooms.
GP Classroom — General Purpose classrooms are managed/scheduled by the Registrar’s office. Classroom Technology Services and Client Services have historically provided support for these rooms.
Non-GP Classroom — Non-GP classrooms are managed/scheduled by individual departments or units in which the classroom resides. Departmental personnel have historically provided support for these rooms.
Recommended Platform: Physical Desktop
Due to the number of peripherals and the current lack of testing, physical machines should be used over VDI machines. With the proper testing and vetting of Thin Clients in classrooms, it is possible that they could move over to remote virtual machines. This testing will require significant collaboration with the Center for Teaching & Learning and faculty.
Research Lab Recommendations
Research labs include any lab dedicated to research only and do not include labs used for classroom instruction.
Windows
Recommended Platform: Physical Desktop
Mac
Recommended Platform: Physical Desktop
Linux
Recommended Platform: Physical Desktop
Research labs often have unique configurations and may have equipment that either requires a proprietary add-on card or requires that the computer not be connected to the network. These limiting factors make physical desktops the only solution currently available. Additionally, Mac and Linux desktops/workstations cannot be virtualized on campus.
Recommended Tools
Windows
Virtual Machine: VMware Horizon, Group Policy
Computers in the Virtual Machine category can be completely managed by VMware Horizon. These computers are all based on template machines allowing for a single point of management per pool. Due to the temporary nature of VDI Instant Clones, patch management and updates are handled once per month or as needed for critical updates on the template machine. Applications also only need to be installed on the one template machine which makes all parts of the deployment process easier.
Group Policy can be used in a VDI environment to control pool-specific policies such as printer deployment, script management, and other restrictions or configurations.
Physical Desktop: LiteTouch, SCCM, Group Policy
Physical computers with Windows 11 Operating System (OS) are imaged using LiteTouch/MDT. They receive the base OS with the most current Windows 11 version, as well as some standard applications. These computers are joined to the CAMPUS domain, after which time they are managed by SCCM which is the university’s Systems Management tool. Computers receive monthly security updates, computer policies, third-party application patches or upgrades, as well as Windows 11 Feature Updates. Group Policies are also applied to manage configurations including security baselines, protocols, and standards.
Mac
Physical Desktop: Apple Recovery Environment, Jamf Pro, Munki
Labs running macOS on Apple hardware must be purchased through the UVM Techstore to be enrolled in UVM’s Mobile Device Management system (MDM), Jamf Pro, which will configure the machines to suit a lab environment, while Munki will install and maintain software.
Mac lab management is a constantly evolving task for two reasons: Apple releases a new version of macOS every year, often with significant changes that can present new challenges for lab managers; Apple’s new hardware releases can only run the latest version of macOS available at the time of release. As a result, the lab management process must be continually evaluated and tested with new tools and processes.
Linux
Physical Desktop: No tools have been identified for the management of Linux workstations.
Conclusion
Some of these recommendations will need to be tested and vetted with other campus constituents before becoming a UVM standard. We also understand that processes for these recommendations need to be thoroughly documented and enforced if standardization is to occur. While this working group focused on three categories of interest, it is worth pointing out that there still exist several edge-case categories that may need further exploration after the initial standardization is complete. The categories not mentioned in this document include tablets, conference rooms, kiosks, and equipment control computers. The recommendations laid out in this document allow us to follow what we believe to be best practices and will allow for consolidation of the tools used for management.