<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Autopilot on Ru Campbell MVP</title>
    <link>https://campbell.scot/categories/autopilot/</link>
    <description>Recent content in Autopilot on Ru Campbell MVP</description>
    <generator>Hugo</generator>
    <language>en-gb</language>
    <lastBuildDate>Tue, 15 Jun 2021 15:26:14 +0000</lastBuildDate>
    <atom:link href="https://campbell.scot/categories/autopilot/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Deploying Office 365 with Intune as a Win32 App (and Why You&#39;d Want To)</title>
      <link>https://campbell.scot/deploying-office-365-with-intune-as-a-win32-app/</link>
      <pubDate>Tue, 15 Jun 2021 15:26:14 +0000</pubDate>
      <guid>https://campbell.scot/deploying-office-365-with-intune-as-a-win32-app/</guid>
      <description>&lt;p&gt;Office 365, or Microsoft 365 Apps for Enterprise, or whatever it&amp;rsquo;s called this month, can be deployed by Intune to Windows 10 devices using a built-in wizard.  The advantage of this is you don&amp;rsquo;t need to package anything: you fill out some nice drop-downs and options in a GUI, assign it like any other app, and Microsoft takes care of the rest.&lt;/p&gt;
&lt;p&gt;&lt;img loading=&#34;lazy&#34; src=&#34;https://campbell.scot/wp-content/uploads/2021/06/Office-365-Intune-Deployment-Wizard.png&#34;&gt;&lt;/p&gt;
&lt;p&gt;In the background, this is using the Office CSP to deploy the client, which makes it quite unique compared to the deployment of other apps, which are best done with Win32 packaging.  I wrote a general guide about that for &lt;a href=&#34;https://petri.com/how-to-package-and-deploy-windows-applications-with-intune&#34;&gt;Petri.com, available here&lt;/a&gt;.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Turn Existing Azure AD Devices into Windows Autopilot Devices</title>
      <link>https://campbell.scot/turn-existing-azure-ad-devices-into-autopilot-devices/</link>
      <pubDate>Sat, 06 Feb 2021 09:19:13 +0000</pubDate>
      <guid>https://campbell.scot/turn-existing-azure-ad-devices-into-autopilot-devices/</guid>
      <description>&lt;p&gt;To provision Windows 10 PCs using Autopilot and Intune, they must first be registered as &lt;strong&gt;Windows Autopilot devices&lt;/strong&gt; in the &lt;strong&gt;Device Directory Service&lt;/strong&gt;, which is really the cloud Autopilot service.  When a device is registered to the Autopilot service, its &lt;strong&gt;hardware hash&lt;/strong&gt; is used to generate a &lt;strong&gt;Zero Touch Device ID&lt;/strong&gt;(ZTDID) - a globally unique identifier for that device based on hardware information such as (but not only) MAC address, disk serial number, and system serial number.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
