Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 6 Next »

Windows Platform-as-a-Service (PaaS) provides the following technical capabilities.

Operating System Deployment (OSD)

Operating system deployment is supported using System Center Configuration Manager (SCCM). The SCCM infrastructure provides the ability install Windows 10 and configured applications via and OSD task sequence (TS) to devices connected to on-campus wired Ethernet networks. Specific combinations of applications can be configured for installation during OSD by creating and saving a build in the Config-O-Matic application. Saved builds may be assigned to specific computers in Config-O-Matic.

Application Deployment

Available Applications

All systems built with using Windows PaaS OSD come with a standard set of software pre-installed. This set of applications is know as MiWorkspace Core software. A list of the MiWorkspace Core Software is available here - Windows Standard Software.

In addition to the MiWorkspace Core software, there are other categories of applications that may be deployed Windows PaaS systems. The available software catalogs are described in the table below:

Catalog NameCatalog Description
MiWorkspace CoreApplications installed on all MiWorkspace and Windows PaaS computers.
MiWorkspace CatalogApplications that can be installed on any MiWorkspace or PaaS computer.
BYOL CatalogBYOL stands for Bring Your Own License. After installing a BYOL title, a customer must enter their own license or account information. BYOL titles may be installed on any MiWorkspace or PaaS computer.
ITAM CatalogApplications that can be installed on MiWorkspace or PaaS computers that are in a unit that participates in the UmichITAM program.
Unit CatalogSoftware that can be installed on any computer in the unit with unit approval.


Additional applications may also be deployed to Windows PaaS systems using SCCM. 

There are two types of deployments - required deployments and self-service.

Required Deployments

Required deployments will run automatically on targeted client systems when the client system meets all installation requirements. Status of deployments may be viewed by users in the Software Center application on the client system. Applications that have been installed by SCCM are listed in the installation status area of the Software Center application.

Self-Service Deployments

Self-service deployments will can be initiated by the user of a client system when the user and the client system meet all installation requirements. Available deployments are managed in the Software Center application on the client system. Applications that have been installed by SCCM are listed in the installation status area of the Software Center application.

Update Deployment

Updates for the Windows operating system and for Microsoft applications such as Microsoft Office and Skype are installed on client systems using required deployments. Deployed updates will install automatically when the deployment deadline is reached. Pending update installations may be viewed in the Software Center application. Installed updates are not displayed in Software Center, but they may be viewed in the Programs and Features control panel. To read about the release schedule of updates, view the Windows Change Schedule topic.

Anti-Virus

Windows Defender antivirus is deployed to all Windows PaaS client systems. Antivirus definitions are updated automatically multiple times per day. Configuration policies for Windows Defender are deployed centrally using SCCM. Customized configuration policies may be deployed on a per-unit basis. To read detailed information about the Windows Defender configuration, view the Windows Defender Configuration topic.

Security Configurations

Windows PaaS systems share many of the same security settings that are implemented on MiWorkspace Windows systems. The baseline security configuration for Windows PaaS systems is designed to enable users to securely access institutional and personal data while still preserving an easy to use computing experience. The settings were developed in consultation with the University of Michigan Information Assurance (IA) team. The specific settings that comprise the baseline security configuration have been tested by the MiWorkspace Quality Assurance (QA) Team to ensure compatibility with major university systems and applications.

The baseline security settings are implemented by Active Directory Group Policies. Settings are implemented in the following Group Policy Objects (GPO):


Virtual Private Network (VPN)

The Windows PaaS product provides provides secure network capabilities via two different VPN technologies, Microsoft DirectAccess and Cisco AnyConnect VPN.

Microsoft DirectAccess is an always-on VPN that provides connectivity to organization network resources without the need for traditional Virtual Private Network (VPN) connections. More information about the DirectAccess implementation in Windows PaaS is available in the MiWorkspace DirectAccess Overview document.

The Cisco AnyConnect VPN Client is availble for deployment to Windows PaaS computers. The client provides connection to the ITS Cisco VPN Service. More information about the Cisco AnyConnect VPN Client implememation in Windows PaaS is available in the MiWorkspace Cisco AnyConnect Overview document.

BitLocker Drive Encryption

The hard drives of all laptop computers using the Windows PaaS solution are automatically encrypted using BitLocker. Hard drives on desktop computers may be opted-in to BitLocker drive encryption. Bitlocker drive encryption is deployed and managed using the Microsoft BitLocker Administration and Monitoring (MBAM) product. The MBAM product provides automated deployment of encryption policies and provides simplified management of recovery keys. More information about the BitLocker implementation is Windows PaaS is available in the MiWorkspace BitLocker Overview document.



  • No labels