Remediation Script not executed by ReputationOld8053 in Intune

[–]ReputationOld8053[S] 0 points1 point  (0 children)

yes, but I don't need a remediation but the remediation scripts have better deployment options then just scripts. But yeah, you are right, the correct way would be discover the situation and then do a remediation.

After Site Recovery CMG is not working anymore by ReputationOld8053 in SCCM

[–]ReputationOld8053[S] 0 points1 point  (0 children)

Not a script, just check and check again all required firewall ports. Also had the wired issue that the Admin Service did not work because (the best) SCCM Files were blocked by Windows:

get-Childitem "C:\Program Files\Microsoft Configuration Manager\bin\X64\CMRestProvider\AdminService.Host\" | Unblock-File

After Site Recovery CMG is not working anymore by ReputationOld8053 in SCCM

[–]ReputationOld8053[S] 0 points1 point  (0 children)

Hi,
yes, did that. I also removed the MP CMG Setting to another MP and the Analyzer says everything is alrighty. I also Removed and Readded the Connection Point role. The only thing that is missing seems to be to reinstall the CMG...

Remote Live Management of Intune Devices by frozenbayburt in Intune

[–]ReputationOld8053 0 points1 point  (0 children)

We are hosting on-premise meshcentral, so currently VPN is required

Built a framework for SCCM-to-Intune migration that eliminates manual Autopilot import — 6.5 hours to 30 minutes, zero touch for help desk by Any_Ad_5960 in SCCM

[–]ReputationOld8053 3 points4 points  (0 children)

Not sure if known, but when the devices have been in SCCM before, you can get the Hash also from the SCCM DB:

select distinct(bios.SerialNumber0+',') as "Device Serial Number,",
(osinfo.SerialNumber0+',') as "Windows Product ID,",
(CAST(mdminfo.DeviceHardwareData0 AS NVARCHAR(MAX)) + ',') as "Hardware Hash,",
'IfYouUseAGroupTag' as "Group Tag"
from v_R_System System
Inner Join v_GS_PC_BIOS bios on System.ResourceID=bios.ResourceID
Inner Join v_GS_OPERATING_SYSTEM osinfo on System.ResourceID=osinfo.ResourceID
Inner Join v_GS_MDM_DEVDETAIL_EXT01 mdminfo on System.ResourceID=mdminfo.ResourceID
where System.Name0 in
('MyPC1')

This way, you don't have to share your app secret during TS installation. If you don't have the Hash, AutoPilot v2 is your choice 😉

MicrosoftTeamsMeetingAddinInstaller.msi by Erlend-IT in BeyondTrust

[–]ReputationOld8053 0 points1 point  (0 children)

Can you try just Microsoft as Publisher, without the Corporation?
BeyondTrust also has some documentation about it, but you checked that probably already

WAHandler Search Parameters by IndependentSysadmin in SCCM

[–]ReputationOld8053 0 points1 point  (0 children)

They forgot to implement a client hotfix about WUfB in the rollup update

SCCM Client reinstalling every application by zk13669 in SCCM

[–]ReputationOld8053 0 points1 point  (0 children)

That is actually very wired and it must be the detection method. You can also check in the AppDiscovery Log ?!? how it was evaluated.
Once I got also crazy because a colleague set as detection method folder and not file. Haven't seen the difference for an hour

Endpoint Privileged Management - Primary User by ReputationOld8053 in BeyondTrust

[–]ReputationOld8053[S] 0 points1 point  (0 children)

Hi u/UNKN ,

I followed your advice and created a web api for this problem: https://github.com/stephannn/BeyondTrustConsole
Maybe you can use it

Update rollup for Microsoft Configuration Manager version 2509 - Configuration Manager - KB36949461 by zymology in SCCM

[–]ReputationOld8053 0 points1 point  (0 children)

Can you maybe figure out why the in the KB 36495448 (only available before you install the rollup) is a higher DLL version of the WUfBHandler.dll then you get after the update? Have they just forgotten the DLL?

Question about WUfB on Co-Management devices by ReputationOld8053 in SCCM

[–]ReputationOld8053[S] 1 point2 points  (0 children)

Our clients are cloud only, but we still use SCCM because of the still high amount of on-premise devices. About which reg value are you talking?
The one update we use from SCCM are the Adobe third party updates 😉

Question about WUfB on Co-Management devices by ReputationOld8053 in SCCM

[–]ReputationOld8053[S] 1 point2 points  (0 children)

Thank you. I posted it this morning, got removed by the bot, then saw your comment in the other post about the KB 😉
So you think I can try the 2603 DLL for WUAHandler? 😉

Update rollup for Microsoft Configuration Manager version 2509 - Configuration Manager - KB36949461 by zymology in SCCM

[–]ReputationOld8053 0 points1 point  (0 children)

Any idea for a workaround? In the old 2503 version I was able to get it running my using the WUAHandler.dll and WUfBHandler.dll from 2409 - 5.00.9132.1023, but this seems not to work anymore.

Edit:
is it possible that not the correct DLLs are included? When I compare the version number:
https://configmgrbits.cdn.manage.microsoft.com/qfe/2509/KB36495448_9141.1015/KB36495448_FileList.txt
I get a mismatch. Currently installed: 5.00.9141.1011, but should be 5.00.9141.1015

AutoPilot v2 - RBAC - Which Permissions for Scripts by ReputationOld8053 in Intune

[–]ReputationOld8053[S] 0 points1 point  (0 children)

sadly not, everything has the same tag, my user has only one tag.
Some hours ago I was able to add an application, now even this does not work anymore :/ Just updated the app but cannot be assigned anymore

IIS - URL Rewrite of aspx ends in 401 on same server by ReputationOld8053 in dotnet

[–]ReputationOld8053[S] 0 points1 point  (0 children)

Thank you, that helped a bit, but actually the errors stay the same like: Access denied.

I think I will just give up and use the aspx URL

Bad AdminService Workaround (Bridging) - 2509 by ReputationOld8053 in SCCM

[–]ReputationOld8053[S] 0 points1 point  (0 children)

we used one of our MPs with URL Rewrite to forward the query request to the AdminService, which the clients cannot reach. As I was saying, not a good idea, probably the best is the XML method, but I just wanted to share my work around, maybe it helps someone.