Windows 10: Intune device configuration Windows 10 + after restriction deployment status is "Not...

Nathan Li Nathan.Li · Feb 4, 2021

Hi:

I created a Intune device configuration profile, it is a Device restrictions Windows 10 and later profile, it has "Removable storage" set as "Block". it use to block usb storage device from my testing computer. I deployed it to a group which have my co-managed windows 10 2004 pro laptop. shortly I saw the deployment status showing "Not applicable".

Please advice how to deployment this police successfully to our windows 10 deivces.

Thanks

:)

Cluster Head · Feb 4, 2021

What's new in Microsoft Intune

What's new in Microsoft Intune

May 2016

With the exception of TeamViewer integration, all of these features are also supported for hybrid deployments (Configuration Manager with Intune). For more information about new hybrid features, check out the Hybrid What’s New page.

Documentation

Welcome to the preview version of docs.microsoft.com! This is a completely new, modern content platform designed to make it easier for you, our customers to understand and use Intune. To read about all of the new features, see Introducing docs.microsoft.com

Intune service health

Service health information for Intune has been moved to a central location with other Microsoft services. You'll now find this information in the Office 365 management portal under Service Health. For more information, see this blog post.

App management

•MAM SDK: Support PIN length configuration. You will be able to specify the length of the PIN for MAM apps similar to a device PIN. This will require end users to comply with the new restrictions you set. They will see a slightly modified PIN screen to account for the longer input. For details, see MAM policy settings for Android, and MAM policy settings for iOS.

•Skype for Business for iOS and Android. You can now target Skype for business with MAM without enrollment policies. Once users log in, the MAM policies will be applied.

•New apps available for management with MAM policies. The Microsoft Word, Excel, and PowerPoint apps for Android can now be associated with MAM policies on devices that are not enrolled with Intune. For a full list of supported apps, go the Microsoft Intune mobile application gallery on the Microsoft Intune application partners page.

Device management
•Remote assistance sessions for Windows PCs. TeamViewer integration for Windows PCs managed by the Intune client software will let you establish remote assistance sessions with Windows PCs to support your help desk department. Supported PCs include Windows 7, 8, 8.1 and Windows 10. For details, see Common Windows PC management tasks with the Microsoft Intune computer client

Company portal updates

Android Company portal app

•End user toast notifications: End users will now see toast notifications from the Android Company Portal app when they are enrolling their devices or removing their devices from the Company Portal.

•Changes to Device Enrollment Managers accounts in the Android Company Portal app. To improve performance and scale, Intune is no longer showing all Device Enrollment Managers (DEM) devices in the My Devices pane of the Android Company Portal app. Only the local device running the app is displayed, and only if it is enrolled via the Company Portal app. The DEM user may perform actions on the local device, but remote management of other enrolled devices can only be performed from the Intune admin console. -

Company Portal website

Company Portal website: Device identification banner will provide more information to end users. End users can now more easily identify the device they’ve selected when they are using the Company Portal website. If the wrong device is selected, they will be able to select the correct device by tapping the Tap here link in the home page banner.

What's coming

•Message center UI onboarding. As part of the migration of Intune into the Office 365 Management portal, we will begin taking advantage of their Message Center to communicate new features and other notifications. Also, by installing the companion Office 365 Admin mobile app, you can receive notifications on your mobile phone and easily forward any messages to users or a distribution alias. We will begin using the Message Center with our May release to notify you when updates are completed and will include information on new and improved Intune features. Check out the Message Center today by logging into the Office 365 Management portal and choosing the MESSAGE CENTER option in the left navigation pane.

•Changes to Device Enrollment Managers accounts. To improve performance and scale, Intune is no longer showing all Device Enrollment Managers (DEM) devices in the My Devices pane of the iOS Company Portal app. Only the local device running the app is displayed, and only if it is enrolled via the Company Portal app. The DEM user may perform actions on the local device, but remote management of other enrolled devices can only be performed from the Intune admin console. Additionally, Intune is deprecating use of DEM accounts with either the Apple Device Enrollment Program or the Apple Configurator tool. Both these enrollment methods already support user-less enrollment for shared iOS devices. Only use DEM accounts when user-less enrollment for shared devices is unavailable.

Cloud roadmap

Keep informed about upcoming developments for Intune with the Cloud Platform roadmap.

Service deprecation

•Intune Viewer apps. With the release of the new RMS sharing app, we are removing the following Intune Viewer apps, beginning August, 2016:
◦Intune AV Viewer
◦Intune PDF Viewer
◦Intune Image Viewer for Android from Google Play

Instead of using the Intune Viewer apps, we recommend using the new Rights Management app (RMS sharing) for Android, which allows you to deploy one app instead of three separate apps to securely view corporate files on Android devices. Learn more about the RMS sharing app (with link to documentation).

•Custom Group Targeting of Notification Rules Removal. Intune notification rules define who an email alert will be sent to from Intune. Currently, you can configure notification rules to send emails to all users of devices in an Intune device group that you created. From around June 1st 2016 moving forward, targeting user-created groups will no longer be supported.

Today, to target a notification rule to a group you created from the Microsoft Intune administration console, you would take the following steps:

In the Admin workspace, click Notification Rules > Create New Rule

In step two of the Create Notification Rule Wizard, select the device groups which the rule will target. This step, “select device groups”, is being removed from the Intune Console.

The preliminary timeline for this change is as follows:
◦In June, 2016, new tenants will not see step two of the Create Notification Rule Wizard. Exiting tenants are unaffected.
◦Around August, 2016, some existing tenants will not see the “select device groups” in the wizard.
◦Around October, 2016, we expect that all tenants will not see the “select device groups” in the wizard.

•Changes in support for the iOS Company Portal app. In the coming months, there will be an update for the Microsoft Intune Company Portal app for iOS that will only support devices running iOS 8.0 or later. Users won’t be able to enroll new devices running versions below iOS 8.0. Enrolled devices running versions below iOS 8.0 will continue to be managed and will, for a limited time, be able to continue using the Company Portal app. However, devices must be on iOS 8.0 or later to access the latest versions of the Company Portal app. We encourage you to notify users to update to iOS 8.0 or later to take full advantage of new Intune features.

Previous Intune releases

If you want to see what's released in Intune during the last six months, they are listed in the Previous Intune releases article.
Click to expand...

Source: https://docs.microsoft.com/en-us/int...ntune#may-2016

Brink · Feb 4, 2021

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

Brink · Feb 4, 2021

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:

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: Intune device configuration Windows 10 + after restriction deployment status is "Not...

Intune device configuration Windows 10 + after restriction deployment status is "Not...

Intune device configuration Windows 10 + after restriction deployment status is "Not...

Intune device configuration Windows 10 + after restriction deployment status is "Not...

Intune device configuration Windows 10 + after restriction deployment status is "Not... - Similar Threads - Intune device configuration

Intune configuration policy not working on some devices

Intune configuration policy not working on some devices

after deploy via intune a firewall rule to client i get "primary status: inactive"

after deploy via intune a firewall rule to client i get "primary status: inactive"

Intune App Deployment - Required install

Intune App Deployment - Required install

Intune App Deployment - Required install

Windows 10 devices can’t sync with Intune after enrollment

Windows 10 SCCM Deployment status stuck on Installing state

Users found this page by searching for:

intune error. not applicable