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...

    Windows 7 Offline files will not go Online when connected to network

    Issue Several laptop users move between networks, domain, home, etc and when they attempt to access DFS shares explorer status is working offline.  The issue only resolves it self after a reboot. Connecting directly to the share works and i am able to ping network resources.  This behavior occurs for VPN users as well. Possible Causes "slow-link mode". In win7 (with default settings) a client will enter slow-link mode if the latency to the server is above 80ms. In slow-link mode all writes are made to the local cache and a background sync only happens every 6 hours.  Depending on your connection the default slow link detection speed is 64,000 bps On client computers running Windows 7 or Windows Server 2008 R2, a shared folder automatically transitions to the slow-link mode if the round-trip latency of the network is greater than 80 milliseconds, or as configured by the "Configure slow-link mode" policy. After transitioning a folder to the slow-link mode, Offline Fil...

    SCCM Software Update - Job error 0x80004005 Failed to Add Update Source for WUAgent

    SCCM Software Updates - Failed to Add Update Source for WUAgent  Today I have been looking at a range of servers (Server 2008 /R2 2012 /R2) that were failing to communicate with the Software Update Point (SUP) in SCCM and retrieve deployment policy. The UpdateDeployment.log was reporting the Job error 0x80004005 Job error (0x80004005) received for assignment ({af7a48e6-d550-4070-dd9b-ecc234567584}) action UpdatesDeploymentAgent 12/6/2017 10:32:27 AM 2096 (0x0830) The WUAHandler.log  was reporting "Unable to read existing WUA Group Policy object" and "Failed to Add Update Source for WUAgent " Unable to read existing WUA Group Policy object. Error = 0x80004005. WUAHandler 12/6/2017 3:41:00 AM 2828 (0x0B0C) Failed to Add Update Source for WUAgent of type (2) and id ({3AAB6A76-CE2D-4E8A-9F11-123AE69612A1}). Error = 0x80004005. WUAHandler 12/6/2017 11:03:31 AM 2276 (0x08E4) Until the agent can report back to the SUP, SCCM will not be able to summarize Software Update sta...