Coming up.
We take a look at Windows AutoPilot deployment.
A new cloud service from Microsoft
that provides you a zero touch experience for deploying new Windows 10 devices.
We take look at how you can work with your hardware vendor to use Windows AutoPilot deployment.
And I'll show you the set of experience on a new Windows 10 device
guided by Windows AutoPilot deployment
that gets your users up and running with everything they need
in just a few simple clicks.
Today, if you need to deploy new devices in your organization,
typically you end up creating your own custom Windows image.
You need to get the right drivers, apps, policies and settings
to prepare this image.
And then you need to maintain it for every device type you support.
For every new PC you deploy,
you wipe the Windows that came pre installed
and replace it with your custom image.
Or, you set up a device manually.
As the idea owner,
you may do this yourself or have your hardware vendor do it for you.
Either way, this costs you time as well as money.
And it adds significant complexity and effort
for the process of deploying new devices.
With Windows AutoPilot deployment,
there is no need to re-image or manually setup new devices
before handing them out to your users.
Devices can be shipped from you hardware vendor directly to your employees.
IT no longer needs to intercept and touch these devices.
There is no need to re-image
or manually prep the device
before you hand it out to your user.
Here's how it works.
There are three entities involved with Windows AutoPilot deployment.
Each play a role.
The Hardware Vendor, the IT Admin and finally the User.
There are three easy steps to get it all working.
Step 1 is device registration.
When you require new devices for your organization,
Your hardware vendor sends a file containing device IDs to you.
All you need to do is upload this device ID file
into Windows AutoPilot deployment service
using your admin AD account
and claim ownership of these devices for your organization.
In the future,
Your hardware vendor can automatically perform this step on your behalf.
Step 2.
Create your deployment profile and assign it to your devices.
With Windows AutoPilot deployment,
You can customize the users set up experience and configuration
by creating a deployment profile.
To create this profile,
select the steps you wish to skip.
In the Windows 10 out-of-box setup experience
and choose whether the user must be restricted to a standard account
or allowed an admin account on the device.
Once you create a profile,
you can assign it to your organizations devices.
You can also mark a profile as default
so all devices automatically get this profile assigned.
Step 3 is shipment.
You can now ship your new Windows 10 devices from your hardware vendor
directly to your employee.
All that your user needs to do
is unbox the device,
power it on and go on line.
As soon as the device is online,
even before the user enters their organization email address
the Windows AutoPilot deployment service
recognizes that the device belongs to your organization,
and delivers a customized setup experience
based on the profile assigned to the device.
Once the user signs in,
The device enrolls in MDM
that will start pushing policies, settings and apps to the device automatically.
The user is up and running with all the apps and settings they need
without having to physically touch the device
in just a few clicks.
Let me know show you windows AutoPilot in action.
After I power on the device,
I just need to select a few things like language and keyboard settings
and then connect to a network.
This can be any network.
You can be at home, at work or even a public wifi hotspot.
With the Creators update release of Windows 10,
The out-of-box setup supports Captive portals.
In my case, I'm connecting to my home network.
As soon as a device connects to a network,
The windows AutoPilot deployment will immediately recognize
that the device belongs to my organization
and customize my setup experience.
I'm directly taken to my organization's sign in page.
Note that this page is personalized
with my organizations name and logo.
So the device knows that it belongs to my organization
just by virtue of connecting to my network.
All powered by Windows AutoPilot.
If you setup Windows 10 before,
you'll recognize that several steps in the setup experience
that require the user to make decisions
do not show up.
Decisions such as,
choosing between a personal device and a work device.
Setting up Cortana,
selecting privacy settings,
registration with the OEM and so on.
Windows AutoPilot deployment took care of those decisions for the user on behalf of IT.
So I'm just going to type in my organization email address
and enter my password and that's all.
My device will now join Azure Active Directory,
automatically enroll into Intune,
or another MDM,
and I'll get to my desktop.
At this point,
Intune can automatically push the apps the I need.
Including line of business apps,
Office apps,
and other Win 32 apps.
The next thing I want to show you is the fact that the user has a standard account
just like the ID had been configured in the deployment profile.
Usually any user
who set's up Windows using the out of box setup experience,
always get's an admin account.
Because that's the first user on the device.
Windows AutoPilot deployment is the only way to restrict the user
stepping through the out-of-box experience on Windows
to a standard account.
If this account was an admin,
it would say administrator, here.
Anna has a standard account on this device.
The next thing I want to show you
is the fact that the device is in fact Azure Active Directory join.
And enrolled into Intune for management.
Finally,
I started with an off the shelf shrink wrapped
Windows 10 Pro edition device.
My device can automatically upgrade from Windows 10 Pro,
to Windows 10 Enterprise.
As long as the IT Admin assigned a Windows enterprise license
to my Azure AD user identity.
Similar to how you would assign the license for Office 365.
There are no product keys, no reboots,
and it doesn't even need an enterprise activation server.
So that was a quick tour of Windows AutoPilot deployment.
You can try it out today with the Creators Update release of Windows10.
To learn more, check out the link below.
We'll be adding some exciting new capabilities
to Windows AutoPilot with the next Windows 10 feature update.
later this year.
Stayed tuned and thanks for watching.
Microsoft Mechanics
www.microsoft.com/mechanics
Không có nhận xét nào:
Đăng nhận xét