SCCM to AirWatch Auto Registration

This script connects to SCCM via WMI, gathers the devices in a collection, checks to see if they are registered in Airwatch, and if they are not it registers the device in Airwatch to the primary user of the device. 

This Sample has been Productized as VMware Workspace ONE AirLift

VMWare recommends customers implement Workspace ONE AirLift to achieve the functionality in this sample

The main purpose and goal of VMware {code} is to share code samples and collaborate with our development community. We actively watch and listen to customer feedback and sometimes take some of the open-source projects and convert them into fully supported versions. We have recently released Workspace ONE AirLift, a server-side connector that simplifies and speeds the customers journey to modern management. Workspace ONE AirLift bridges administrative frameworks between Microsoft System Center Configuration Manager (SCCM) and Workspace ONE UEM.

SCCM to Airwatch Device Registration

Overview

  • Author: Chris Halstead
  • Email: chalstead@vmware.com
  • Date Created: 2/20/2018
  • Updated: 9/13/2018
  • Tested on: SCCM 2012 R2 & SCCM 1806 and AirWatch 9.3-9.7
  • Version: 2.1

SYNOPSIS

In order to silently onboard Windows 10 devices into AirWatch and have them automatically assigned to the primary user, you will have to first preregister devices via a batch import. You can use the attached script to perform a batch import of these device records into AirWatch.
This script connects to SCCM via WMI, gathers the devices in a collection, checks to see if they are registered in Airwatch, and if they are not it registers the device in Airwatch to the primary user of the device.

Parameters

SCCMServer

Name of the SCCM Server you want to connect to

SCCMCollectionName

Name of a Collection in the SCCM site which you want to query devices from

AirwatchServer

Server URL for the AirWatch API Server

AirwatchAdmin

An AirWatch admin account in the tenant that is being queried. This admin must have the API role at a minimum.

AirwatchPW

The password that is used by the admin specified in the username parameter

AirwatchAPIKey

This is the REST API key that is generated in the AirWatch Console. You locate this key at All Settings -> Advanced -> API -> REST, and you will find the key in the API Key field. If it is not there you may need override the settings and Enable API Access

OrganizationGroupName

The name of the Organization Group where the devices will be registered. The API key and admin credentials need to be authenticated at this Organization Group.

Prerequisites

SCCM 2012 R2 or later and Airwatch 9.x

Must be run with an account that has access to SCCM WMI Provider

Airwatch admin account with at least API privileges needed

##Change Log

  • 2/20/2018 Published
  • 5/1/2018 Version 2.0 Changed script so it will connect via remote WMI to the SCCM Server. It no longer needs to be run locally on the SCCM Server
  • 9/13/2018 Added AirLift reference in README
  • 9/13/2018 - Version 2.1 Changed script's AirWatchUser reference to AirWatchAdmin.

Sign in to be able to add comments.

Comments 2


saadukhan 1 year ago
Please change the "AirwatchUser" parameter to "AirwatchAdmin". It took me forever to realize that the script was looking for an admin account, instead of the user account. Even the parameter description states: "This user must have...".

This has caused much confusion for the SCCM admins who are using AW/WS1 for the first time. They don't have the experience to know that this script actually means an admin account, not user account.
JosueNegron 11 months ago
Thanks @saadukhan for reporting this enhancement, we have applied the changes and updated the description for AirWatchAdmin to be more clear. Please be sure to also check out Workspace ONE AirLift which will automate this entire process for you.
;