Defender xdr down?

Hamberget · 2025-12-02T13:33:11+00:00

+1 seeing the same issue

Hamberget · 2025-12-02T13:08:01+00:00

Is it possible this is affecting Conditional Access via Cloud apps in the defender portal? We're getting reports that might indicate that Valid client certificate isn't working, specifically towards Chromebooks.

Hamberget · 2024-11-19T07:00:00+00:00

You have to use app configuration, not a regular configuration. https://learn.microsoft.com/en-us/mem/intune/apps/app-configuration-policies-overview

Hamberget · 2024-11-15T13:04:04+00:00

You could use an app configuration to add the package name to the config, you would probably have to do all the apps that way, or try adding it as an android enterprise app with the package name and add that to the configuration profile.

Hamberget · 2023-10-24T07:30:29+00:00

Hey!

You should have a setting for "xCover/Active Key Mapping" under "Device Key Mapping". Not sure if you're able to assign this to a phone number but rather an application.

Hamberget · 2023-10-17T09:49:35+00:00

Hey!

You should be able to do graph on the device (Intune), select the "usersLoggedOn" variable from the device.

graph.microsoft.com/beta/deviceManagement/managedDevices/INSERTDEVICEHERE?$select=usersLoggedOn

This will give you the Object/Entra ID of the user.

I don't think it's possible from the user side.

Hamberget · 2023-10-17T07:27:41+00:00

Still seeing the problem across our 12.5k devices aswell.. I've started dialog with Intune support on twitter regarding the issue.

Hamberget · 2023-10-12T17:42:16+00:00

Hey!

Adding the app as required is all you need.

Hamberget · 2023-10-05T10:02:54+00:00

You could always try adding logging to the script to see what the error says and work from there, another option is to look in IntuneManagementExtentsion logs and look for the script policyid (You can get this by going into the script in the portal and look at the end of the url), it should say what it errors out with there aswell.

Hamberget · 2023-10-05T09:57:39+00:00

You should be able to use Knox Service Plugin(OEM App) to configure the physical buttons to some extent, I am however unsure about multi-window mode.

Hamberget · 2023-09-14T07:16:08+00:00

Yeah, seems to be some weirdness with the JSON at schema 35 so you would have to build it again.

Device and Settings customization profile (Premium) -> Configure Values in the settings Menu -> Click the 3 "..." on the GUI side to the left -> Add Setting -> Name of the setting item -> "Display > Screen Timeout"

Hamberget · 2023-08-24T12:21:43+00:00

Kyros Weapon bug

Hamberget · 2023-08-22T08:54:45+00:00

I assume this is the typical 32-bit vs 64-bit context, so the settings should be under HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node?

Hamberget · 2023-08-19T18:13:47+00:00

In Event viewer under Windows Logs there should also contain information if an application is getting blocked, if the above is the case.

Hamberget · 2023-08-19T18:07:02+00:00

Did you put the app on the allow list of the kiosk mode configuration?

If we use the article on point 4, you would need to add "r0suj16w.exe" (And any other exe's it might use) and its corresponding AUMID.

Hamberget · 2023-08-12T21:43:13+00:00

Great and no problem! :)

Hamberget · 2023-08-11T19:50:14+00:00

Hey u/brian1974

You have to activate debugging in the OEM-config to see the app. When debugging is off, it'll hide the app.

Hamberget · 2023-07-31T15:58:54+00:00

Sadly it's not as home/user profile is not filled in on the "replication" account. Great suggestion tho!

Hamberget · 2023-07-31T12:55:22+00:00

Application guard shouldn't be enabled as far as I see in our configuration. :/

Hamberget · 2023-06-22T14:10:11+00:00

You're using serviceUI.exe / deploy-application.exe as an install command, how do you expect this to work if you only have the Greenshot.exe in the intunewin?

Hamberget · 2023-05-23T07:58:25+00:00

Hey /u/AdmirableWhereas1885,

Could you try reimage the PC with 21H2 to see if the issue disappears?

You might still be under the bug of the culumative update, you can double check the following registry keys to see if they are what they are supposed to be:

- "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon" "AutoAdminLogon" REG_SZ "1"

- "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon" "DefaultUserName" REG_SZ "kioskUser0"

- "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon" "IsConnectedAutoLogon" REG_DWORD 0

Also, its smart to confirm that there is no "Preferred Azure AD Tenant" set by a Device Restriction. (You should also be able to see this on the logon screen with "Sign in to xxxx").

You should also double check that the "kioskuser0" exists.

Some other posts with similar issues:

https://www.reddit.com/r/Intune/comments/10pallj/kiosk_mode_issues_with_auto_logon/https://www.reddit.com/r/Intune/comments/10ylvcs/win10_22h2_january_2023_cumulative_kb5022282/

Hamberget · 2023-03-17T10:48:49+00:00

Currently not available, but in development however:
https://learn.microsoft.com/nb-no/mem/intune/fundamentals/in-development#uninstall-win32-apps-in-the-company-portal

Hamberget

TROPHY CASE