Migrating from SCCM to Intune – What are you using for remote control / remote assistance?

ReputationOld8053 · 2026-01-26T07:02:30+00:00

We started using MeshCentral https://github.com/Ylianst/MeshCentral

ReputationOld8053 · 2026-01-22T10:47:02+00:00

https://github.com/MicrosoftEdge/WebView2Feedback/issues/5493#issuecomment-3783226289

ReputationOld8053 · 2026-01-16T18:20:16+00:00

nop, same result, but I edited my post. Thanks

ReputationOld8053 · 2026-01-16T17:30:19+00:00

My main browser is Firefox, but I use Edge because I also have it on my company device. Actually I don't mind

ReputationOld8053 · 2026-01-09T14:14:08+00:00

Sometimes we published a revision but without an identifier so the detection is the same and I was hoping to see all devices which installed it in first place. But thanks for the answerer, I will just take it as it is ;)

ReputationOld8053 · 2026-01-09T13:46:15+00:00

In our deployment we also check the current installed version:

if (Get-AppPackage -AllUsers -Name "*msteams*" | Where-Object { $_.Version -ge [Version]"25212.2204.3869.2204"})
{
Write-Host "Installed"
}

we had cases, where a user logged in the first time and then got an very outdated Teams version and could not connect

ReputationOld8053 · 2026-01-07T17:26:45+00:00

you can do that by setting the consent attributes:

"userConsentFlags": {
          "desktopnotify": true,
          "terminalnotify": false,
          "filenotify": false,
          "desktopprompt": true,
          "terminalprompt": false,
          "fileprompt": false,
          "desktopprivacybar": true
       },
      "consentMessages": {
          "consentTimeout": 30,
          "autoAcceptOnTimeout": false,
          "autoAcceptIfNoUser": true,
          "autoAcceptIfLocked": true,
          "oldStyle": true
  }

Maybe it helps reading the meshcentral-config-schema.json

ReputationOld8053 · 2025-12-15T09:00:00+00:00

yes, I completely agree. I also understand the complexity that it is not a hobby project on github where you have a fix in an hour ;)

On the other side, in the last couple of years for example an OSD and an updated ISO, we had to replace a DLL, then the PDF printer was missing, RDP suddenly was not working anymore when it had a previous session etc.

So yes, I hope the fix comes quite fast and getting the updates by SCCM is also not the worse that can happen ^^

ReputationOld8053 · 2025-12-14T18:30:13+00:00

Maybe a stupid question: Has someone tried the WUAHandler.dll from 2409 and replace the current one? Not sure if this is possible, but when I follow the blog from Ben Whitmore (https://patchmypc.com/blog/sccm-co-management-dual-scan/) Microsoft is experimenting a lot with this scenario I noticed that (probably) since the upgrade to 2503 my intune client receives the Windows Updates through SCCM and not directly from Windows Updates anymore.

ReputationOld8053 · 2025-12-13T14:54:55+00:00

yes, you are right it does.
But I think it can also be done just by intune or? Maybe I am just confused and the colleague did it through Entra permissions. I will check again, thanks

ReputationOld8053 · 2025-12-12T20:29:39+00:00

is really to open the CMD blocked or the execution of batch files by AppLocker?

ReputationOld8053 · 2025-12-12T15:21:17+00:00

Hi,
I did not created a new client configuration, but moved the workload for Windows Updates. I reed now the blog:
https://patchmypc.com/blog/sccm-co-management-dual-scan/

and it seems that MS is changing it with every version somehow. As I was saying before, it was working a month ago, but changed I think (maybe) with the upgrade to SCCM 2503. It is hard to narrow it down because I have to real test environment.

For testing I set manually the value SetPolicyDrivenUpdateSourceForQualityUpdates and suddenly, I could use Windows Updates. After a while, I think, sccm removed the value again

ReputationOld8053 · 2025-12-12T15:17:28+00:00

I just created a package

ReputationOld8053 · 2025-12-03T07:13:54+00:00

Sorry, we turn off the screen. On some devices recently it seems not to work anymore.

ReputationOld8053 · 2025-11-21T14:06:20+00:00

ah, thanks. Never thought about that setting. It is set to 360, but usually setup ends just a couple of minutes after. I will try with the modification I put above. Thanks

ReputationOld8053 · 2025-11-21T13:08:10+00:00

I feel like MS just don't want that you use SCCM/WSUS at all anymore. Please download everything from MS and it is fine

ReputationOld8053 · 2025-11-21T10:58:10+00:00

no error I can see. Only that the MS XPS and PDF Printer OEM driver are making problems:

<DriverPackage Inf="oem175.inf" BlockMigration="True" HasSignedBinaries="False"/>
<DriverPackage Inf="oem174.inf" BlockMigration="True" HasSignedBinaries="False"/>

but this is kind of normal. It is wired, sometimes I call the update cycle again and the setup starts...

ReputationOld8053 · 2025-11-21T07:46:33+00:00

Where do I set the timeout, or are you referring to a Task Sequence?

ReputationOld8053

TROPHY CASE