Windows 10: Intune configuration profile says successful, but setting does not show up/apply to windows

I am attempting to apply the following Intune configuration profile:I applied it to a group that only has users, me and it says Succeeded:Here is the information event logged on my event viewer:I tried to troubleshoot this with Intune support, but they said it was a windows desktop issue. I have tried this on two separate computers and received the same result.

:)

 

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.

 

Azure configuration profile not applicable for user accounts logged into desktops and iPhones

We're facing such a strange issue,

We're applying screen lock policy via configuration profiles for devices Windows 10 and later. This is successful for all profiles signed into a desktop, but if a profile is signed into a phone and a desktop, the policy shows "not applicable" (even though policy should not apply to phones).

We're setting screen lock using OMA-URI settings, by using ./Device/Vendor/MSFT/Policy/Config/DeviceLock/MaxInactivityTimeDeviceLock and setting integer to 15.

We point the policy at groups whose members are devices. Once the device syncs, the system profile shows as "successful" for policy, and then the user profile (*** Email address is removed for privacy ***) will show as successful.

As soon as *** Email address is removed for privacy *** signs into a company iPhone, the user goes from "successful" in screen lock configuration profile to "not applicable", even though policy is directed at Windows10 devices.

Why is it that configuration profile works until a user signs into two different devices at the same time? The system account will show as successful, but user account "not applicable"

 

What's new in Microsoft Intune


What's new in Microsoft Intune

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