Skip to main content

Corporate iPad management

This blog will cover how to manage corporate iPad; iPads owned by the company/school.

Once all prerequisites have been setup, enrolment is very quick as easy as turning the device ON.

Device Enrolment steps
  1.  Unbox and turn on
  2. Select language
  3. Select Region
  4. Connect to the Internet
    1. At this stage the onboard MDM agent will check in with Apple servers to see if the device is part of the Apple Device Enrolment program.
    2. NOTE: Devices not added to this DEP program must be enrolled manually: see below
  5. Open Safari and navigate to the URL https://account.manage.microsoft.com
  6. Enroll corporate-owned devices with the Device Enrollment Manager (Microsoft Intune account specifically created and can enrol 2000 devices) 
  7. The Company portal page will ask you to Enrol the device and install the APN certificate.  Run through this process until finished.

Processes 


How to reset the PIN?

If the user forgets their PIN; Administrator can reset by logging into https://manage.microsoft.com
Select Groups> all Corporate-Owned Devices> identify iPad via mobile number
Select Groups> All Mobile Device> Right click iPad and Reset PIN

 

References


Apple Deployment Programmes Volume Purchase Programme for Business Guide 



Microsoft Intune Account portal
https://account.manage.microsoft.com

Microsoft Intune Manage portal
https://manage.microsoft.com

Apple Volume Purchase Program portal
https://vpp.itunes.apple.com

Mobile Application Management with Intune (Dated 2014 Video)
https://channel9.msdn.com/Events/TechEd/Europe/2014/EM-B312

Apple DEP portal
deploy.apple.com

Apple ID management
https://appleid.apple.com/

    Apple DEP
    Apple Customer ID
    Apple Configuration
    MDM solutions
    Microsoft Intune
    Silent device enrolment (Device Enrolment Program)
    Policy management
    Locking down devices.

    Comments

    Popular posts from this blog

    SCCM Unknown computer not able to see Task Sequences after installing Current Branch 1702

    Soon after installing SCCM CB 1702 we were unable to see Task Sequences deployed to the unknown collection. This issue was identified as a random system taking the GUID of the 'x64 Unknown Computer (x64 Unknown Computer)' record. As a result it was now a known GUID; as we were only deploying Task Sequences to the Unknown collection none were made available. 'x64 Unknown Computer (x64 Unknown Computer)' record 'x86 Unknown Computer (x86 Unknown Computer)' record To get the GUID of your unknown systems open SQL management studio and run the following command: --Sql Command to list the name and GUID for UnknownSystems record data select ItemKey, Name0,SMS_Unique_Identifier0 from UnknownSystem_DISC Using the returned GUID (SMS_Unique_Identifier0) we can find the hostname that has been assigned the 'x64 Unknown Computer (x64 Unknown Computer)' GUID by running the query below. --x64 Unknown Computers select Name0,SMS_Unique_Identifier0,Decommissioned0 from Sys...

    KB5025885: How to manage the Windows Boot Manager revocations for Secure Boot changes associated with CVE-2023-24932

    This article outlines the protection against the publicly disclosed Secure Boot security feature bypass involving the BlackLotus UEFI bootkit (CVE-2023-24932). It includes steps to enable the necessary mitigations and provides guidance on creating bootable media. I will provide: - An overview of the CVE issue. - Pre-requisite actions within ADK. - Detection and remediation scripts for CVE-2023-24932. - Instructions for creating a WinPE Boot.wim file to support systems that have undergone remediation. - A breakdown of the files changed and how to boot WinPE to support systems before remediation. 1. Secure Boot Security Feature Bypass Vulnerability CVE-2023-24932 see MSRC CVE-2023-24932 is a security vulnerability involving the BlackLotus UEFI bootkit, which allows attackers to bypass Secure Boot protections. This vulnerability enables the execution of malicious code at the UEFI level, potentially leading to persistent and evasive threats. Mitigations for this issue include updates to th...

    Java 7 update 21 (1.7.0_21) Enterprise Repackaged Security Medium Deployment with SCCM

    ------------------------------------------------------------------------------------------------- Java 7 update 45 Enterprise deployment complete walk through http://www.syswow64.co.uk/2013/10/java-7-update-45-enterprise-deployment.html -------------------------------------------------------------------------------------------------- The issue on many blogs and articles is around creating the 'deployment.config' and 'deployment.properties' files for an enterprise deployment.  In my case i wanted to set the security level to 'Medium', but everytime I open the Java control panel it was set to the default HIGH setting. Solution 1 Create the following directory path 'C:\Windows\sun\java\deployment' 2 Create a file called 'deployment.config' in this directory and open with Notepad. Copy the two line below #################### deployment.system.config = file\:\\C\:\\WINDOWS\\Sun\\Java\\Deployment\\deployment.properties deployment.system...