Intune & Autopilot: Setting up a Shared Use Device running Microsoft Windows
This article’s intended audience is University IT technicians who have been provisioned access to UConn’s Microsoft Intune Admin Center.
Shared Use Device Definition: A Windows desktop or laptop that is not assigned to a specific individual and is being used by multiple faculty, staff and/or students.
Step 1 - Identify the computer to be setup as a shared device
Identify the serial number of the computer that will be setup as a shared use workstation.
Step 2 - Confirm the computer is registered in Autopilot, has a group tag and has the “Shared Device Autopilot“ profile assigned
A. Sign into the Microsoft Intune Admin Center with your netidadmin@ad.uconn.edu account
B. Click “Devices“ in the navigation column, then under “Device Onboarding”, click “Enrollment“
C. Under “Windows Autopilot“ click “Devices“
D. Type the serial number from Step 1 in the “Search” box.
If the computer appears in Autopilot proceed to Step 2E, if not follow the steps in Intune & Autopilot: Enrolling devices into Intune then proceed to Step 2E.
E. With the computer in Autopilot, ensure it has the proper group tag assigned. You can review the list of group tags in the table below.
F. If it is a shared device within a distributed functional area, then the computer will need to be run (or re-run) thru enrollment after being placed in the Assigned Azure Shared Device Group for the Functional Area in which it belongs.
Notes
If the device is a classroom, lab or conference room to be configured the same as those devices managed by ITS then no further action is needed beyond applying the appropriate group tag in Autopilot and running the device thru enrollment.
Adding a device to an Assigned Azure Shared Device Group will:
Give the device the “Shared Device Autopilot” profile
Add the device to the top level policy group “Policy - MW Shared Machine Config“ for shared devices, which will ensure “Windows Hello for Business” is disabled and “Microsoft Office LTSC” is installed instead of “Microsoft 365 Apps for Enterprise”.
Once the device is configured you will need to confirm there is no Primary User and the Management Name is adjusted to reference who is responsible for the device.
Article: kb.uconn.edu/space/IKB/26471759873
Autopilot/Intune Group Tag | Functional Area / Purpose | Assigned Azure Shared Device Group | Member of Policy Group |
|---|---|---|---|
mwAveryPoint | Avery Point Campus | mwAveryPoint - Shared Computer Policy | Policy - MW Shared Machine Config |
mwBUSN | School of Business | mwBUSN - Shared Computer Policy | Policy - MW Shared Machine Config |
mwCLAS | College of Liberal Arts and Sciences | mwCLAS - Shared Computer Policy | Policy - MW Shared Machine Config |
mwENGR | School of Engineering | mwENGR - Shared Computer Policy | Policy - MW Shared Machine Config |
MWClassrooms | ITS Hi-Tech Classrooms | Not Applicable | Not Applicable |
MWConference | ITS Managed Conference Rooms | Not Applicable | Not Applicable |
MWLabs | ITS Managed Computer Labs | Not Applicable | Not Applicable |
mwOVPR | Office of Vice Provost & Research | mwOVPR - Shared Computer Policy | Policy - MW Shared Machine Config |
mwSA | Student Affairs | mwSA - Shared Computer Policy | Policy - MW Shared Machine Config |
mwEDU | School of Education | mwEDU - Shared Computer Policy | Policy - MW Shared Machine Config |
mwLibrary | University Libraries | mwLibrary - Shared Computer Policy | Policy - MW Shared Machine Config |
MWManagedWorkstation | Information Technology Services | mwManagedWorkstation - Shared Computer Policy | Policy - MW Shared Machine Config |
mwStamford | Stamford Campus | mwStamford - Shared Computer Policy | Policy - MW Shared Machine Config |
mwInCHIP | Institute for Collaboration on Health, Intervention, and Policy | mwInCHIP - Shared Computer Policy | Policy - MW Shared Machine Config |