msra.exe (remote assistance) refuses to connect - for non-admins

Last week one of our admins in a remote location came across an odd issue. They were not able to send a remote assistance request (msra.exe /offerra <pcname>) to an employee that needed some help. They tried other computers and everything was working. They tried it again with a different account that has admin permissions on the target (first) machine and that worked too.

Our helpdesk checked all the permissions but was not able to find any faults. A coworker of mine checked everything again but also was not able to find any configuration issues. Everything looked like it was supposed to.

[SCCM] SMS Agent Host (ccmexec) hangs on Windows 10 1903/1909 – no updates/software are being installed

Update 18.02.2020: I have gotten some new information that suggests that you might be able to solve this issue not only by enabling the Windows Defender Antivirus service on the client, but also by disabling the Endpoint Protection feature on the SCCM server instead. But since I do not have access to our SCCM server (as stated below) I cannot test this approach myself. Feel free to leave a comment below if this actually works too.

Disclaimer: I am not an expert in all things SCCM. I have not had any kind of training and I have no access to our local SCCM server at all, not even read-only access. Everything I know is self-taught from bits and pieces I have picked up here and there. A huge jigsaw puzzle with lots of holes to fill – not to mention all the pieces I have dropped under the table by now.

Our resident SCCM guy has been working on deploying Windows 10 1909 to our clients for a couple of weeks now and after overcoming an issue (with my help) that prematurely killed the task sequence (a story for another time) he finally managed to deploy a system that satisfied the requirements I had set.

But even before that, he had accidentally deployed the “1909 Insider Preview” package to a total of seven machines. In addition to those, we had of course manually upgraded a handful machines to 1909 to test it out or to fix other random issues with Windows 10 clients here and there.

Right after the accidental deployment of the Insider Preview version of 1909 we noticed that the SCCM Software Center was in English, and not our usual German locale. A repair installation of the SCCM Client fixed that issue.

[Hardware] Fujitsu Esprimo Q958 will not power down with USB device connected

A couple of months ago, around August-September I believe, we got a new model of Fujitsu Mini-PCs – the Esprimo Q958. We had already been using the Q957 without any troubles for a while so we did not expect to face any problems with this new iteration either. Besides a newer CPU generation (Core i5 8^th Gen compared to Core i5 7^th Gen) nothing had really changed, we thought.

But soon after deploying a number of those new Fujitsu Esprimo Q958 machines to our users we got weird reports of machines not fully powering down when shutting down Windows.

The machines would simply stay powered on when you pressed the “Shut down” button in Windows. The machines would keep running, with power management disabled, and thus the CPU would soon get warmer and warmer, making the fan turn on to 100%, which in turn resulted in a lot of noise thanks to the very small fan.