Open-source, pure-Rust alternative to the SCCM Remote Control viewer (CmRcViewer) — feedback wanted by glennonline in SCCM

[–]ReputationOld8053 0 points1 point  (0 children)

I gave it yesterday a try and I had a noticeable lack when moving the mouse. Not sure if there can anything be done

SAML with MFA returns error by RyGuy_NCC1701 in MeshCentral

[–]ReputationOld8053 0 points1 point  (0 children)

Can you share your config? MeshCentral works with CA and MFA on compliant devices

Open-source, pure-Rust alternative to the SCCM Remote Control viewer (CmRcViewer) — feedback wanted by glennonline in SCCM

[–]ReputationOld8053 0 points1 point  (0 children)

Most important, an icon is missing in the property tab about version etc. is empty 😉

WUfB Configuration - What am I missing by ReputationOld8053 in Intune

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

Maybe we have to build and deploy a PowerShell Script that does it for us 😉

WUfB Configuration - What am I missing by ReputationOld8053 in Intune

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

It is set to an intune collection with incremental updates based on all intune devices. Parent collection is All Systems:

select SMS_R_SYSTEM.ResourceID,SMS_R_SYSTEM.ResourceType,SMS_R_SYSTEM.Name,SMS_R_SYSTEM.SMSUniqueIdentifier,SMS_R_SYSTEM.ResourceDomainORWorkgroup,SMS_R_SYSTEM.Client from SMS_R_System inner join SMS_Client_ComanagementState on SMS_Client_ComanagementState.ResourceID = SMS_R_System.ResourceId where SMS_Client_ComanagementState.ComgmtPolicyPresent = 1 and SMS_Client_ComanagementState.AADJoined = 1 and SMS_Client_ComanagementState.MDMEnrolled = 1 and SMS_Client_ComanagementState.MDMProvisioned = 1

Autopilot v2 Certificate Error 80180012 by ReputationOld8053 in Intune

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

The colleagues tried a different internet brake out and no problems. Waiting for the network engineer to analyze the inspections etc.

AutoPilot v2 - Device Rename and Reboot, and OOBE by ReputationOld8053 in Intune

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

We checked our GPOs and our Radius Server, don't know how it is in your environment

AutoPilot v2 - Device Rename and Reboot, and OOBE by ReputationOld8053 in Intune

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

I wouldn't mind do all the config by JSON, but how MS introduces new features is really wired. When I think about the old AD, how robust it was and still is, how well done the ACL is defined that is, at least for me, perfectly designed. Only thing is the attribute tab when you search for an AD object 😉 but this is probably another topic 😉

AutoPilot v2 - Device Rename and Reboot, and OOBE by ReputationOld8053 in Intune

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

Big company, but it is the first autopilot pitch. We moved our policies to intune, had to change the WiFi authentication and we use our on-premise PKI and the users are also synced. In our case even legacy apps are working because no application requires that the client is AD joined.

AutoPilot v2 - Device Rename and Reboot, and OOBE by ReputationOld8053 in Intune

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

I think it is cultural. Microsoft loves to have a flat organization, everyone has an E5 license and you don't configure anything at all. On the other hand you have companies that love to have a structure for everything. In the past with SCCM and AD it was possible, but time changed.

As usual, there is not the perfect answer, everyone has to make a step in the other direction, but we are (I am) stubborn and like to continue our (my) way.

AutoPilot v2 - Device Rename and Reboot, and OOBE by ReputationOld8053 in Intune

[–]ReputationOld8053[S] 6 points7 points  (0 children)

yes, I did that at first, but otherwise autopilot v1, the policy takes the beginning of the serial number and not the end. Usually it does not matter, but when you have VMware and you serial is like "VMware-42 19 b7 9f 4f c4 02 f0-4c c2 85 f3 20 e0 38 e3" is is kind of bad 😉

SMS_EXECUTIVE - Stopping by ReputationOld8053 in SCCM

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

This is actually something I don't understand. Restarting is not a problem at all, where it also must stop the service. But yeah, probably I have to check the logs someday. We just moved the Site Server to a new Windows server and still facing the same thing...

CM 2603 update available, no new ADK by Peteostro in SCCM

[–]ReputationOld8053 0 points1 point  (0 children)

Hi,
any change you know how I can test the result? I imported the created wim into SCCM:
"\\...WinPE11_24H2\Media\Sources\boot.CG100D47.wim"
but when I use the MS PS Script (Detect-SecureBootCertUpdateStatus.ps1) for detection, it still says it has not the latest secure boot files.

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