Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Teams Rooms on Windows devices support Intune Autopilot, which enables a zero-touch deployment, to learn more about the overall process see: Windows Autopilot and Autologin for Teams Rooms on Windows.
One of the key portions of Autopilot is adding the hardware identity information from the Teams Rooms compute to the customers Intune environment. Registration can be completed in three ways:
This document provides step by step instructions for a Teams Rooms partner (that is a Cloud Solution Provider) how to add the Teams Rooms Autopilot hardware identity into a customer’s environment.
Important
If you're a CSP but aren’t deploying Teams Rooms devices, reference the Intune documentation. If you're a Teams Rooms partner who isn't a Cloud Solution Provider: use the OEM automatic registration method or gather the hardware identities for your customer to load directly.
Step 1: Establish a CSP relationship with the customer environment
A CSP relationship with a customer is essential to add devices into their environment. Follow these instructions to: request a CSP relationship with your customer
Note
Typically, CSP relationships are for requesting administrative access to a customer environment, Granular Delegated Administrative Permissions (GDAP) isn't required for registering Autopilot hardware identities. You can request GDAP to assist your customer with other administrative activities, but it isn't required for this process.
Step 2: Gather hardware identities
Adding hardware identities to a customer’s environment through Partner Center can be accomplished using one of three combinations of values. Different devices can be registered with different methods, but you must have one of the three sets of information per device as it allows the Intune Autopilot service to identify the device.
Serial Number + Manufacturer Name + Model Number
- This information is typically included in the packing invoice when hardware is ordered/delivered from a distributor or OEM
Windows PKID (Product Key ID)
- This information is frequently found on the label on the box for a Teams Room or on a sticker on the Teams Room itself. Some OEMs also make this information available on their website by providing proof of device purchase.
Device Hardware Hash
- This information is most frequently collected manually by running a script on the device itself however occasionally it's also available by contacting the Teams Rooms OEM.
Since the best practice for gathering this information can vary by Teams Rooms OEM, the learn to deploy Teams Rooms on Windows in minutes blog has information authored by each OEM on what is recommended for their products.
Step 3: Retrieve the CSV template for uploading Autopilot hardware identities
Open Partner Center
Select Customers
Select your desired customer from the customer list
Select Devices from the left navigation rail
Select Devices in the tabs at the top
Select Add group
Select Download next to You can see a sample CSV here
Step 4: Add the device identity information to the CSV
Open the CSV template, delete all of the sample information and add in the relevant information for the customers Teams Rooms devices.
Step 5: Upload the CSV into Partner Center for the customer
Open Partner Center
Select Customers
Select your desired customer from the customer list
Select Devices from the left navigation rail
Select Devices in the tabs at the top
Select Add group
Enter a group name for this upload. Ensure the group name starts with “MTR-“ so devices are automatically populated into the Pro Management Portal
Select Upload File and attach the file created in step 4
Step 6: Continue the Teams Rooms Autopilot setup steps
The Autopilot hardware identity registration is now complete. Continue with the Intune and Pro Management Portal configuration guidance outlined in the deployment documentation: Windows Autopilot and Autologin for Teams Rooms on Windows.
Note
The remaining Teams Rooms Autopilot + Autologin steps are completed by the customer administrator or using GDAP.