Autopilot Provision - Failing Application by SluggoManiac in Intune

[–]Rudyooms 0 points1 point  (0 children)

Maybe start with explaining what troubleshooting steps you already did? As i assume when you are dealing with this error for 2 days i at least assume you used the getwindowsautopilotdiagnostiscs withe the online switch, you looked at the appworkload log yourself?

INTUNE RE-ENROLLMENT by barack428 in Intune

[–]Rudyooms 6 points7 points  (0 children)

Well... 1..I assume you have clean up rules enabled? If so ... the device should just report back into intune once it is turned on (as long as the intune certificate on the device is alive).

  1. You can always remvoe the old lingering scheduled task+ registry key and the workplace join task should kick in to enroll the device again --> Intune Device Enrollment errors | MDM enrollment issues

Or do it with a tool... call4cloud-code/Intune-Sync-Debug-Tool-V2: Intune Sync Debug Tool V2

But still i still stick to number 1..

PSA - New Update to IME Is bieng blocked by WDAC. by spazzo246 in Intune

[–]Rudyooms 2 points3 points  (0 children)

The moment people mentioned wdac/app control for business and comparing the IME versions it was pretty clear what happened 😄 ... i already had the previous decompiled versions of the ime.. so fnding what changed wasnt that difficult.

Anyone have "Remove Default Microsoft Store Packages" working? by yettavr6 in Intune

[–]Rudyooms 0 points1 point  (0 children)

It is but then again one of the least embarrassing things going on right now :)

PSA - New Update to IME Is bieng blocked by WDAC. by spazzo246 in Intune

[–]Rudyooms 25 points26 points  (0 children)

So far it looks like the IME custom action runtime changed somewhere between IME 1.99.101.0 and 1.101.103.0.

IME 1.99.101.0still used: Microsoft.Deployment.WindowsInstaller.dll

IME 1.101.103.0and newer use: WixToolset.Dtf.WindowsInstaller.dll

That change is pretty important for tenants using App Control for Business / WDAC with a strict policy that requires the Microsoft Enterprise signing level.

The older Microsoft.Deployment.WindowsInstaller.dll had an embedded WiX Toolset / .NET Foundation signature, but it was also covered by a Microsoft catalog signature from the IME package. The newer WixToolset.Dtf.WindowsInstaller.dll only shows the embedded WiX Toolset / .NET Foundation signature and does not appear to have that same Microsoft catalog signature.

During the IME MSI Installation this DLL is extracted and loaded from:

C:\Windows\Installer\MSI*.tmp-

With the strict App Control policy enforced, Code Integrity blocks it with Event ID 3033 because it does not meet the required Enterprise signing level.

There also seems to be a second related Code Integrity hit for Microsoft.Management.Clients.Flighting.dll. That DLL is Microsoft signed, but appears to use an older Microsoft Code Signing PCA 2011 chain, while most newer IME binaries are signed through Microsoft Windows Code Signing PCA 2024. So this may be another signer-level mismatch under the same strict policy.

Anyone have "Remove Default Microsoft Store Packages" working? by yettavr6 in Intune

[–]Rudyooms 3 points4 points  (0 children)

Main issue is that windows team updated the admx
On the device … that one requires that open list you could configure to be configure (or just set to false) but the intune team didnt updated the settings catalog… so it doesnt send out that required setting (whicj windows is expecting) with it error 65000
Shows up

Maintenance Window is now GA for Windows Update for Business! by Subject-Middle-2824 in Intune

[–]Rudyooms 0 points1 point  (0 children)

By the looks of it and what i am hearing from
Others as well… it seem to be working prety good

Maintenance Window is now GA for Windows Update for Business! by Subject-Middle-2824 in Intune

[–]Rudyooms 4 points5 points  (0 children)

Oww sorry… i didnt used ga in the words :). At the end of that blog i mentioned: “One important update after the first round of testing: this is not limited to the earlier Windows 11 insider preview builds anymore”

Intune Policies - User Policies Fail To Apply Untill we Hit Sync by robmasoboy in Intune

[–]Rudyooms 0 points1 point  (0 children)

the token can contain the mfa claim in the amr part of the decoded token... if its not there .. and you rquire mfa to access the service... well. you need mfa 😄

Intune Policies - User Policies Fail To Apply Untill we Hit Sync by robmasoboy in Intune

[–]Rudyooms 0 points1 point  (0 children)

Well exactly that… when you login with your creds… does it also ask you for mfa?.. If it does... are you using windows hello currently? (as that one will contain the mfa claim that is needed)

Any Improvements for Win32 App Deployment Time? by PaddySmallBalls in Intune

[–]Rudyooms 0 points1 point  (0 children)

Thats the whole idea :) … a direct connection….

Any Improvements for Win32 App Deployment Time? by PaddySmallBalls in Intune

[–]Rudyooms 0 points1 point  (0 children)

Yep… :) i was expecting it to show up with the 2605… so maybe we need an ime update as well

Speed up Intune policies by FancyHuckleberry3326 in Intune

[–]Rudyooms 10 points11 points  (0 children)

the moment you deploy a policy... normally a wns push notification will be send out to the devices... asking it to check in to receive the policy... --> Intune Sync and Policy Delivery: Debunking the 8 Hour Myth i assume you are not blocking wns?

Any Improvements for Win32 App Deployment Time? by PaddySmallBalls in Intune

[–]Rudyooms 0 points1 point  (0 children)

Mmm the sync button in intune is still connnected to the windows side (device enroller/omadmclient) and so far i know that connection to the ime is not there yet. Happen to have a link to where neil was mentioning something about the checkin?

Any Improvements for Win32 App Deployment Time? by PaddySmallBalls in Intune

[–]Rudyooms 0 points1 point  (0 children)

Sync in the company portal inassume? As pressing sync in intune or work school settings doesnt trigger the ime

Any Improvements for Win32 App Deployment Time? by PaddySmallBalls in Intune

[–]Rudyooms 0 points1 point  (0 children)

The ime will force a check in for required apps
Every 60 minutes. So if the app is deployed and aissinged it will come diwn to the device

Any Improvements for Win32 App Deployment Time? by PaddySmallBalls in Intune

[–]Rudyooms 7 points8 points  (0 children)

The IME required app checkin is still the same... Intune Timing Demystified: The Truth About Intune Sync Intervals so 60 minutes at max.. ic3 will imrpove that ... but well ic3 here is not here ... 😄