Windows 10: Windows Autopilot for existing devices supports Hybrid Azure AD Join

Brink · Jul 2, 2019

First, a quick refresher on Windows Autopilot for existing devices: For customers looking for a path to migrate from Windows 7 (or 8.1) to Windows 10 using Windows Autopilot, the challenge was always that you had to register the existing machines with Windows Autopilot in advance, but doing so was impossible because you couldn't grab the hardware hash from a device running Windows 7.

So, we added the ability in Windows 10, version 1809 to use a JSON file containing the equivalent of the Windows Autopilot profile so that you didn't have to register the device in advance; you could then tell Microsoft Intune to harvest the hash from the device later and register the device after the fact.

This solution worked great and has been leveraged by a number of organizations to move from Windows 7 and Active Directory to Windows 10 and Azure Active Directory, using Microsoft Intune (often with Configuration Manager for co-management) to deploy and manage the device.

But some organizations weren't yet ready for Azure AD Join (even with the Administrative Templates support in Microsoft Intune, and full support for Kerberos authentication from an Azure AD-joined device to Active Directory-secured resources) and asked us to support this same process, but with Hybrid Azure AD Join.

With this month's Microsoft Intune updates, we can now support this. And no client changes are needed: this works with Windows 10, version 1809 and above. All you need to do is specify a JSON file that specifies to join Active Directory (via Hybrid Azure AD Join) instead of Azure Active Directory - the rest of the process (e.g. the Configuration Manager task sequence that deploys Windows 10 to the device) is unchanged.

Note that you will need to target a Domain Join profile (and any other device-targeted policies) to "All devices" since the device won't be known to Microsoft Intune in advance. (Don't worry, this Domain Join profile has no impact on already-deployed devices, as it's only used by Microsoft Intune to determine what domain and OU should be used when joining a device to Active Directory.) See the updated documentation for more details.
Click to expand...

Source: https://techcommunity.microsoft.com/...re/ba-p/730408

Tweet

— Twitter API (@User) View on Twiiter

:)

JohneSanchez4994 · Jul 2, 2019

Autopilot Profiles: Azure /Intune.

In the Microsoft Partner Center Dashboard I am able to both create and configure Autopilot profiles and (once it’s working) register devices to apply those Autopilot profiles to.

In the Azure Intune Dashboard I am able to do the exact same functions as mentioned above in the Microsoft Partner Center by navigating:

Open Azure

Open InTune

Click Device Enrollment

Click Windows Enrollment

In this GUI there are options for Windows Autopilot

The odd thing is that for the same customer I can configure Autopilot in two different places. Additionally, if I create a profile in one location, it does not propagate to the other. I can have two completely different profiles in each place.

How is it determined which is the profile that will be used for Autopilot if I have one in each place? Is one being phased out? Thanks for any information that you can provide.

Also, what would happen if we had a device from a completely different source than Ingram? Like we inherited a client that already had PC’s, and we wanted to onboard them with the Azure/InTune stack? Would we not be able to register
those devices? I don’t think Ingram would interested in taking requests for devices that they didn’t even sell.

Thank you.

Brink · Jul 2, 2019

New Windows Autopilot capabilities to deploy Windows 10

Windows Autopilot simplifies the deployment of new Windows 10 devices by eliminating the cost and complexity associated with creating, maintaining, and loading custom images. Windows Autopilot lets you deliver new off-the-shelf Windows 10 devices directly to users. With a few simple clicks, the device launches in a fully business-ready state, dramatically reducing the time it takes for your users to get up and running with new devices.Not only does Windows Autopilot significantly reduce the cost of deploying Windows 10 devices, it also delivers a great experience for users that’s zero-touch for IT.

This week at Microsoft Ignite, we are excited to announce two new Windows Autopilot capabilities:

Windows Autopilot Hybrid Azure AD join support for user-driven deployments. You can now choose to join devices to either Azure Active Directory (available since Windows 10, version 1703) or Active Directory (new in Windows 10, version 1809).

Windows Autopilot for existing devices. Use System Center Configuration Manager to take your existing devices from Windows 7 to Windows 10, configuring them so that they go through the normal Windows Autopilot user-driven deployment process once booted into Windows 10.

These new features build upon the Windows Autopilot capabilities we announced earlier this year and will be available in Windows 10, version 1809 (also referred to as the Windows 10 October 2018 Update.

Windows Autopilot self-deploying mode, which completely automates device provisioning (plug it in, turn it on, let it set up itself).

Windows Autopilot reset, which enables you to reset and redeploy a Microsoft Intune-managed Windows 10 device remotely to prepare it for a new user or use case.

Partner support for Windows Autopilot

We are also excited to share that Dell, HP, Lenovo, and Toshiba are participating device manufacturers for Windows Autopilot along with Microsoft Surface. Panasonic and Acer are coming soon.

In addition, beginning November 30, 2018, Dell is enhancing the Windows Autopilot services it first launched in April. Dell will offer Windows Autopilot registration globally at no additional cost when ordered with Dell commercial PCs. Coupled with Windows 10, Windows Autopilot enables the pre-configuration of devices for unified endpoint management. Dell will continue to offer additional services for a fee, such as generic image and asset tagging, to help customers provision systems faster and easier.

Learn more

To learn more about Windows Autopilot, please see the following resources:

Overview of Windows Autopilot

Click to expand...

Source: https://techcommunity.microsoft.com/...rt/ba-p/260430

Mr Davo · Jul 2, 2019

Image W10 workstations for Azure AD join?

Hi All,

I want to image Windows 10; but more importantly I need to join Azure AD 'Out of the Box'!

I don't have a 'master' Azure AD account. I am not even sure that such a thing exits, e.g.: the Administrator account on a standard Active Directory Domain.

Where should I be looking for configuration, where it comes to Azure AD automatic joining?

My thoughts are PowerShell DST! But that is just a rumour.

Any suggestions would be amazing.

Regards,

Davo

Windows 10: Windows Autopilot for existing devices supports Hybrid Azure AD Join

Windows Autopilot for existing devices supports Hybrid Azure AD Join

Windows Autopilot for existing devices supports Hybrid Azure AD Join

Windows Autopilot for existing devices supports Hybrid Azure AD Join

Windows Autopilot for existing devices supports Hybrid Azure AD Join - Similar Threads - Autopilot existing devices

Hybrid Azure AD Join device didn't show managed by "Org name" and unable to enable co-manage

Hybrid Azure AD Join device didn't show managed by "Org name" and unable to enable co-manage

Hybrid Azure AD Join device didn't show managed by "Org name" and unable to enable co-manage

Azure AD Hybrid environment with on prem

Azure AD Hybrid environment with on prem

update on Azure AD support for FIDO2 security keys in hybrid environments

WIndows 10 Activation Issue / Azure AD joined device

RDP to Azure AD joined computer

Dis-Join Azure AD