Windows 10: New Windows Autopilot capabilities to deploy Windows 10

Brink · Sep 24, 2018

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

Windows Autopilot: What it is and how it works

Video: Windows Autopilot zero touch deployment and device reset

Video: Windows Autopilot walkthrough

Click to expand...

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

:)

Brink · Sep 24, 2018

What’s new and what’s next for Windows Autopilot in Windows 10

With Windows 10, we are focused on delivering a simpler, more powerful and intelligent IT experience by deepening integration across Microsoft’s products, creating a unified Microsoft 365 solution. Windows Autopilot simplifies the deployment of new Windows 10 devices in your organization by eliminating the need for IT to create, maintain and apply custom images, dramatically reducing the cost and complexity involved with custom imaging. You can now deliver new Windows 10 devices directly to your users without IT having to touch the device. With just a few simple clicks, your users can get up and running. With Windows Autopilot, the experience of deploying new Windows 10 devices is simple for end users and zero touch for IT—seamlessly integrated across Windows 10, Microsoft Intune, and Azure AD.

This post outlines the latest enhancements to Windows Autopilot in Windows 10, version 1803, specifically:

Enrollment status

OEM and hardware vendor supply chain integration

BitLocker integration

Automatic Windows Autopilot profile assignment

Device deletion with Microsoft Intune

I’m also excited to share the Public Preview of two new and exciting capabilities available to test through the Windows Insider Program and Windows Insider Program for Business:

Windows Autopilot Self-Deploying mode

Windows Autopilot Reset

Read on for details and, to see these capabilities in action, check out this new video from Microsoft Mechanics:

Don’t have time to watch this video now? .

7t7xaV8sm50

Windows Autopilot: What’s new in Windows 10, version 1803

Enrollment status

We’ve received extensive requests from customers for the ability to prevent users from accessing the desktop on a Windows 10 device until that device has been provisioned with IT-specified policies and configurations. With Windows 10, version 1803, we’ve addressed this feedback with a feature called enrollment status, which shows the status of a device’s configuration in the Windows 10 Out of Box Experience (OOBE) and gives IT the ability to hold the device in that state until all policies and configuration have been provisioned via MDM.

Figure 1. The enrollment status page.

This feature is now available as a preview with Microsoft Intune with Windows 10, version 1803. To turn on the enrollment status page, go to the Enrollment Status Page (Preview) section under Device enrollment > Windows enrollment in Microsoft Intune. Select the desired profile and click Settings to configure enrollment status page options for that profile. These options include the ability to:

Block the device in Windows 10 OOBE until all apps and profiles are installed on the device.

Choose the actions that users are allowed to perform in case of unexpected failures.

Specify how long the device should wait for enrollment status to complete before showing an error.

Specify a custom message in case of errors.

Currently, the enrollment status page can only be configured for the “All Users” group, which would apply to all devices and users in your organization. We are working on extending this capability to support additional groups in a future Microsoft Intune release.

Known issues

To take advantage of the enrollment status page, ensure that you have pre-installed Windows 10, version 1803 including the latest updates.

Certain policies (e.g. Windows Defender Application Guard) may trigger a reboot while Windows 10 is on the enrollment status page. This may cause the enrollment status to be interrupted and cause Windows Autopilot to fail. The device may prompt for built-in OOBE account (default0) credentials. This issue will be addressed in an upcoming update to Windows 10, version 1803, and we will update this blog post at that time with the details.

OEM and hardware vendor supply chain integration with Windows Autopilot

We’ve enabled OEMs and hardware vendors to integrate their supply chain and fulfillment systems with Windows Autopilot programmatically. This enables your hardware vendor to automatically register devices into Windows Autopilot as part of your Windows 10 device order fulfillment. With this automation, there is no action required from IT to register newly purchased Windows 10 devices into Windows Autopilot.

Lenovo and Surface have already automated their supply chain into Windows Autopilot, and we’re actively working with Dell, HP and other OEM partners to deliver this simplicity in coming months.

BitLocker updates for Windows Autopilot

With Windows 10, version 1803, we’ve made it possible for automatic BitLocker encryption to work with standard user accounts configured using Windows Autopilot. Please note, however, that automatic BitLocker encryption requires HSTI or InstantGo devices. For hardware that doesn’t support automatic BitLocker encryption, to turn on BitLocker with standard accounts using Microsoft Intune, you may find this blog post helpful.

Automatic Windows Autopilot profile assignment

Today, every time you register a new device with Windows Autopilot, you need to explicitly assign a Windows Autopilot profile to the device. Based on your feedback, we’ve integrated Azure AD groups with Windows Autopilot profile assignment through Microsoft Intune, enabling automatic assignment of a Windows Autopilot profile to Windows Autopilot registered devices. With this capability, you no longer need to manually select Windows Autopilot registered devices and assign them a profile on an ongoing basis. You can use this same Azure AD group for assignment of other Intune policies like apps and configurations, enabling complete automation for IT.

To enable the automatic assignment of the same profile to all Windows Autopilot registered devices, we tag every registered device with a tag called “ZTDID.” That means all you need to do is create an Azure AD group with a dynamic membership rule looking for the ZTDID and assign a Windows Autopilot profile to that group.

Figure 2. Creating a dynamic membership rule that looks for the ZTDID tag.

With this capability, all Windows Autopilot registered devices, regardless of when they were registered (in the past or in the future), will automatically be assigned the Windows Autopilot profile you specified. Please note: dynamic Azure AD group rules can take a few hours to process so it make take a little while for your Windows Autopilot profile assignments to show up. Alternatively, you can choose to sync on demand from the Windows Autopilot devices blade in Microsoft Intune. For more information on how to create Azure AD dynamic groups for Windows Autopilot, see Create an Autopilot device group.

In a future release, we’ll make it possible for you to specify a custom tag when you order devices from your OEM or hardware vendor to enable the creation of dynamic rules for Windows Autopilot profile assignment based on the tags you specify.

Windows Autopilot device deletion with Microsoft Intune

Based on your feedback, we’ve now made it possible to delete devices from Windows Autopilot using Microsoft Intune. If the devices are enrolled in Intune, you must first delete them from the Azure AD portal. Then, in the Windows Autopilot devices blade, simply select the devices you want to delete and choose Delete. We’re working on simplifying this experience further in a future Microsoft Intune release.

Figure 3. Deleting a device from Windows Autopilot using Microsoft Intune.

Windows Autopilot: What’s new in the Windows Insider Program

We’re taking zero touch to an entirely new level with the latest Windows Autopilot innovations:

Extending the zero-touch Windows 10 deployment experience with Self-Deploying mode.

Extending the zero-touch experience for resetting and redeploying Windows 10 devices with Windows Autopilot Reset.

These new capabilities will revolutionize how Windows 10 devices are deployed and reset—and are available to test now with Windows 10 Insider Preview Build 17672 (and later) and the Microsoft Intune preview.

Windows Autopilot Self-Deploying mode (preview)

We want the experience of deploying a new Windows 10 device to be zero touch, not only for IT, but also for the user. With a new Windows Autopilot capability called Self-Deploying mode, a new Windows 10 device can be fully business-ready by simply powering on the device. All the user needs to do is plug in the device to a network, power it on, and watch Windows Autopilot do its magic. With Self-Deploying mode, a normal off-the-shelf Windows 10 PC transforms into an intelligent device that knows how to deploy itself. Windows 10 will join your organization’s Azure AD tenant, enroll the device into Microsoft Intune (using automatic MDM enrollment), and ensure that all policies, applications, certificates, and networking profiles are provisioned on the device (using the enrollment status page).

Windows Autopilot’s Self-Deploying mode also enables you to effortlessly deploy Windows 10 as a kiosk, digital signage device, or shared productivity device. For example, if you leverage the new Kiosk Browser—an app that leverages Microsoft Edge to create a tailored and managed browsing experience—and Microsoft Intune policies to create a local automatic logon account, you can transform an off-the-shelf Windows 10 device into a browser kiosk– all that it would take is power on the device and walk away. Windows Autopilot’s Self-Deploying mode will automatically get the device joined to Azure AD, enroll into Microsoft Intune and Microsoft Intune will configure the device, deploy the app, configuration and policies, create an autologon account and transform the device into a locked down browser kiosk. No need to touch the device after power on, its as simple as that. For more information, see Simplifying kiosk management for IT with Windows 10.

With the introduction of Self-Deploying mode, we’ve made it possible for you to specify language, region, and keyboard settings for the Windows Autopilot profile. If a device has network connectivity (via an ethernet cable) when it is powered on, Windows Autopilot will automatically configure these settings without requiring any action from the end user.

Figure 4. Configuring OOBE language and keyboard settings

You can use Self-Deploying mode with a Wi-Fi network; however, the user will need to navigate through the Windows 10 OOBE until they reach the Wi-Fi connection step, at which point Self-Deploying mode will kick in. Because Self-Deploying mode doesn’t require a user to enter their organization credentials, it is important that you physically secure possession of your devices before assigning a Windows Autopilot profile, and Self-Deploying mode, to the device.

Note: Self-Deploying mode requires a device with TPM 2.0 used to authenticate the device into your organization’s Azure AD tenant.

Windows Autopilot Self-Deploying mode is available with Windows 10 Insider Preview Build 17672 and later. When configuring an Windows Autopilot profile in Microsoft Intune, you’ll see a new drop-down menu that asks for the deployment mode. In that menu, select Self-Deploying (preview) and apply that profile to the devices you’d like to validate.

Known issues

In the current Windows 10 Insider Preview build, Self-Deploying mode requires the user to interact and click on two pages in the Windows 10 OOBE:

The user must select the “Next” button on a “Welcome” page. (This page will automatically progress in a future Windows 10 Insider Preview build.)

All Windows Autopilot scenarios (including Self-Deploying mode) require the user to interact with the Activities page in the OOBE. (This page will be skipped in all Windows Autopilot scenarios in a future Windows 10 Insider Preview build.)

Remote Windows Autopilot Reset (preview)

Resetting and repurposing Windows 10 devices is a common occurrence for many of our customers. For example, academic institutions often need to reset devices at the end of the academic year and redeploy those devices for the next group of students. With Windows Autopilot Reset, all it takes to reset and deploy a device into a fully business-ready state is click of a single button in Microsoft Intune.

You may recall that we introduced a similar capability with Windows 10, version 1709 called Windows Automatic Redeployment. Windows Automatic Redeployment required a keyboard shortcut and admin credentials to trigger a reset and redeploy a device. This scenario is still available, but with the addition of the ability to trigger the reset remotely via Microsoft Intune, we are renaming this feature Windows Autopilot Reset.

As mentioned above, Windows Autopilot Reset is available with Windows 10 Insider Preview Build 17672 and later. Windows Autopilot Reset removes personal files, apps, and settings, resetting Windows 10 while still maintaining Azure AD Join and Microsoft Intune enrollment. Enrollment status must be configured for a device to trigger Windows Autopilot Reset as this allows you to ensure that a device goes back into a fully business-ready state, updated with the latest policies, settings, and apps from Microsoft Intune.

Once either a local or remote Windows Autopilot Reset is complete, the device will automatically:

Retain the region, language, and keyboard settings as configured prior to the reset.

Connect to Wi-Fi using the network credentials provisioned to the device prior to the reset.

Apply a new provisioning package (if a provisioning package is inserted via USB when Windows Autopilot Reset is triggered), or reapply the original provisioning package cached locally on the device.

Retain Azure AD Join and Microsoft Intune enrollment.

Return to a known, good, managed and synchronized state.

Whether a device is being transferred from one user to another, or you’re trying to fix a malfunctioning device (e.g. digital signage), Windows Autopilot Reset enables you to reset and automatically redeploy Windows 10 without physically accessing a device. This makes the IT experience to reset and redeploy hundreds and thousands of devices trivially simple; it just takes the click of a button in Microsoft Intune.

To trigger a remote Windows Autopilot Reset, follow these steps:

Navigate to Devices tab in the Microsoft Intune console.

In the All devices view, select the target devices and then click More to view device actions.

Select Autopilot Reset to kick-off the reset task.

Known issue

In the current Windows 10 Insider Preview build, if you set up a kiosk device with an auto-logon local account and issue a Windows Autopilot Reset to that device, after finishing Windows Autopilot Reset, Windows 10 will prompt you to enter the password for the local auto-logon account. You can leave the password blank and select enter to logon manually. This issue will be addressed in a future Windows 10 Insider Preview build so that it will not prompt for logon if an auto-logon local account is configured.

Summary

We hope you are as excited about these new capabilities as we are. Windows Autopilot is an absolute game changer, and we will continue to make investments to simplify Windows 10 deployment and management–powered by Microsoft 365.

Please try out these new capabilities and provide feedback and suggestions via the Feedback Hub. We look forward to hearing your thoughts on new capabilities and features.
Click to expand...

Source: Windows Autopilot: What's new and what's next

See also: Simplifying IT with the latest updates from Windows Autopilot - Microsoft 365 Blog

Ahhzz · Sep 24, 2018

Windows 10 Tweaks

Pressing “Windows+Pause Break” (it’s up there next to scroll lock) opens the “System” Window.

Windows 10: In the new version of Windows, Explorer has a section called Quick Access. This includes your frequent folders and recent files. Explorer defaults to opening this page when you open a new window. If you’d rather open the usual This PC, with links to your drives and library folders, follow these steps:

Open a new Explorer window.

Click View in the ribbon.

Click Options.

Under General, next to “Open File Explorer to:” choose “This PC.”

Click OK

credit to Lifehacker.

Brink · Sep 24, 2018

Modernizing Windows deployment with Windows AutoPilot

Windows AutoPilot is a suite of capabilities designed to simplify and modernize the deployment and management of new Windows 10 PCs. As Rob Lefferts announced this morning, the Windows AutoPilot Deployment service marks the start of these capabilities. With Windows AutoPilot, IT professionals can customize the Out of Box Experience (OOBE) for Windows 10 PCs and enable end users to take a brand-new Windows 10 device and—with just a few clicks—have a fully-configured device ready for business use. There are no images to deploy, no drivers to inject, and no infrastructure to manage. Most importantly, users can go through the process independently, without making any decisions and without needing to involve IT.

I’m Sidd Mantri, Principal PM Manager for Windows AutoPilot and I’ll now explain Windows AutoPilot in a little more detail.

How does Windows AutoPilot Deployment work?

With Windows 10, version 1703 (also referred to as the Creators Update), you can register your organization’s devices with the Windows AutoPilot Deployment service to your Azure Active Directory (Azure AD) tenant and customize the OOBE for your end users using a cloud configuration. This enables users to walk through the self-service deployment of their new Windows 10 devices without needing IT assistance.

Here’s how it works:

Hand out a brand new Windows 10 PC to the user.

The user unboxes and powers on the new Windows 10 device. With a few clicks (select language, choose keyboard layout, connect to a network), the device is recognized as your organization’s device and delivers the customized OOBE you configured. (Additional steps in the standard Windows 10 OOBE such as choosing between a personal device or a work device, selecting privacy settings, OEM registration, Cortana setup, and OneDrive setup can be skipped using Windows AutoPilot Deployment.)*

Once connected to the network, Windows prompts the user to sign with their Azure AD e-mail address and password. (The sign-in experience is branded with your organization’s name and logo before your employee enters their Azure AD sign-in information.)

Upon successful authentication, the device joins Azure AD and is automatically enrolled in Microsoft Intune or other mobile device management (MDM) solution.**

Of course, there is no better way to understand this process than to see it in action. Watch this short Microsoft Mechanics video for an overview:

4K4hC5NchbE

Don’t have time to watch this video now? Bookmark it for easy viewing later.

Some of the benefits of Windows AutoPilot are:

Intune can push policies, settings, and configuration to the device, and install Office 365 and other apps without IT ever having to touch the device or apply a custom image to the device.

Intune can configure Windows Update for Business to apply the latest updates.

The device can automatically upgrade from Windows 10 Pro to Windows 10 Enterprise seamlessly using AAD–no product keys to manage, no reboots, no prompts for the user.***

For Windows AutoPilot Deployment to work, you must register your organization-owned Windows 10 devices to your organization’s Azure AD tenant. This is possible for new Windows 10 PCs acquired from OEMs, distributors, and resellers participating in the Windows AutoPilot Deployment Program. It will soon be possible for OEMs and resellers to take care of this registration automatically on your behalf when fulfilling device orders in the future. Contact your device reseller or OEM partner for their plans to support the Windows AutoPilot Deployment Program.

The Surface team is working with customers and partners to roll out the Windows AutoPilot Deployment program and expects to make it broadly available to customers later this year. Contact your Microsoft Sales team representative for details.

Alternatively, for existing Windows 10 PCs running version 1703 (or higher), you can query the DeviceIDs programmatically and build the deviceID file to register applicable devices into the Windows AutoPilot Deployment service.

When can I start using Windows AutoPilot?

These capabilities are available today for Windows 10, version 1703. To try them out, check out the Windows AutoPilot documentation, which will walk you through the process. The Microsoft Store for Business and Cloud Solution Provider program will provide organizations and partners with the ability to register devices and configure Windows AutoPilot Deployment in the near future. We’re also working with MDM partners to integrate the AutoPilot Deployment configuration experience.

For scenarios where IT will be configuring the device with traditional on-premises or cloud-based modern IT scenarios, Windows Configuration Designer can be used to help automate the process. For simpler school scenarios, the Set Up School PCs app (announced last year) can be used as well. For a comparison of these scenarios, see the Windows AutoPilot overview.

As we move down the path towards modern IT, we will continue to add additional capabilities to Windows AutoPilot to ensure that the process is as simple as possible for both IT and the end user. At the same time, we will strive to provide additional “stepping stone” capabilities for organizations who feel they need to move in more measured increments toward this modern IT future.

New capabilities to Windows AutoPilot that will be added in the Windows 10 Fall Creators Update release later this year include:

Self-service deployment for Active Directory domain-joined devices – Windows AutoPilot Deployment will enable self-service deployment capabilities to get new Windows 10 devices into an Active Directory domain-joined state along with Microsoft Intune enrollment.

Enhanced personalization for self-service deployment – Windows AutoPilot will offer the ability to pre-assign a new Windows 10 device to a specific user in your organization and deliver a highly-personalized OOBE.

Windows AutoPilot Reset – A new reset capability In Windows AutoPilot will enable organizations to easily reset their configured devices while still maintaining MDM enrollment and the Azure AD join state, and automatically get the device back into a business-ready state.

* Starting with Windows 10, version 1703, captive portals are supported in the Windows 10 OOBE, so users can still leverage self-service deployment with Windows AutoPilot when using a Wi-Fi hotspot.
** Automatic enrollment requires an Azure AD Premium subscription.
*** Requires a Windows 10 Enterprise E3 subscription.

How can I learn more about Windows AutoPilot?

For tips on how to best take advantage of Windows AutoPilot in your organization, and a walkthrough of common usage scenarios, stay tuned to this blog and follow us on Twitter @MSWindowsITPro for an announcement about a special Windows AutoPilot webcast in late July.

We’ll also be hosting a one-hour “Ask Microsoft Anything” about Windows 10 management event at 9:00 a.m. Pacific Time on July 25th. Members of the Windows engineering and product teams will be standing by to answer your questions.

Click to expand...

Source: Modernizing Windows deployment with Windows AutoPilot Windows for IT Pros

Windows 10: New Windows Autopilot capabilities to deploy Windows 10

New Windows Autopilot capabilities to deploy Windows 10

New Windows Autopilot capabilities to deploy Windows 10

New Windows Autopilot capabilities to deploy Windows 10

New Windows Autopilot capabilities to deploy Windows 10 - Similar Threads - Autopilot capabilities deploy

Deployment windows 10

Deploy Windows OS automatically via Autopilot upon SSD change

Deploy Windows OS automatically via Autopilot upon SSD change

Deploy Windows OS automatically via Autopilot upon SSD change

AutoPilot Deploying Application Error 0x800b0100

What’s new and what’s next for Windows Autopilot in Windows 10

Windows 10 Deployment

Windows 10 Deployment

Modernizing Windows deployment with Windows AutoPilot

Users found this page by searching for:

does autopilot deploy images

lenovo autopilot

dell autopilot enrollment