If someone else who has an S1 could double-check to see if they have this same issue I would appreciate it.
The issue is that with the factory installation of Windows 11 on the S1, I am not seeing an options on Start to Sleep, Shut down, or Restart the system when connected via Remote Desktop.
Here is what I see when connected directly to the Mini PC:
This is what I see when I connect to the Mini PC via Remote Desktop:
I use Remote Desktop on all my systems and I have never seen this issue. I am aware that there is a Group Policy setting that can cause this this issue, but that setting is not enabled on this system.
For the moment, all I am really looking for is to see if anyone else who still has their factory installation of Windows on an S1 Mini PC is experiencing the same issue.
Another S1 issue - Shutdown not available via a Remote Desktop connection
-
- Posts: 91
- Joined: Sat Mar 04, 2023 4:36 am
- Been thanked: 12 times
Re: Another S1 issue - Shutdown not available via a Remote Desktop connection
This is an RDP thing, not an S1 thing. I've had the same thing with my Windows systems, for years across different OS versions. Make sure your RDP connection is across an Admin Console session (the way to do this depends on your application and version, but mstsc /console should do it).
GK3V (J4125/8GB/128GB) | AMR5 (R5 5600U/16GB/512GB NVMe) | JK06 (N5100/8GB/256GB) | AK1Pro (N5105/8GB/256GB) | T8Pro (N5095/8GB/256GB) | AD03 (N95/8GB/256GB) | CK10 (i7-10810U/16GB/512GB) | S1 (N95/16GB/512GB)
-
- Posts: 91
- Joined: Sat Mar 04, 2023 4:36 am
- Been thanked: 12 times
Re: Another S1 issue - Shutdown not available via a Remote Desktop connection
This NOT an RDP thing. I literally use RDP with dozens of machines and have NEVER had this issue on any of them.
In any case, whatever the cause was, reinstalling the OS using the provided factory image resolved the issue as does performing a clean install of Windows from a standard retail image.
In any case, whatever the cause was, reinstalling the OS using the provided factory image resolved the issue as does performing a clean install of Windows from a standard retail image.