This is a niche use case. just to report, not asking for a fix, but hopefully in the future.
use win srv 2022 in a hyper-v virtual machine (with GPU enabled). install remotly in admin account only, not in any user account. connect only via PC_Name/administrator instance. everything works fine, can connect to login screen after reboot, can login to user account, can logout and login etc. i.e. only use the boot service.
problem -1 : remote desktop to the admin account, close the connection (w/o logout), then connect remotly to PC/administrator instance, remotly is black screen. this probably is expected.
problem -2: logoff from remote desktop, PC_name/administrator becomes offline
sometimes, login admin account via hyper-v terminal can get it back. sometimes can't.
when can't, remotly icon does not show up in admin account, need to manually kill all remotly processes, include the boot process (SYSTEM), then logout and login again, to get it back online. after that, logout admin account (hyper-v terminal), PC_name/administrator remains online, everything back to normal.
I remember similar issue discussed last year, and was told that remote desktop logoff process was too fast for remotly to hand-off from interactive instance to boot service. not sure if this is the still the issue.
use win srv 2022 in a hyper-v virtual machine (with GPU enabled). install remotly in admin account only, not in any user account. connect only via PC_Name/administrator instance. everything works fine, can connect to login screen after reboot, can login to user account, can logout and login etc. i.e. only use the boot service.
problem -1 : remote desktop to the admin account, close the connection (w/o logout), then connect remotly to PC/administrator instance, remotly is black screen. this probably is expected.
problem -2: logoff from remote desktop, PC_name/administrator becomes offline
sometimes, login admin account via hyper-v terminal can get it back. sometimes can't.
when can't, remotly icon does not show up in admin account, need to manually kill all remotly processes, include the boot process (SYSTEM), then logout and login again, to get it back online. after that, logout admin account (hyper-v terminal), PC_name/administrator remains online, everything back to normal.
I remember similar issue discussed last year, and was told that remote desktop logoff process was too fast for remotly to hand-off from interactive instance to boot service. not sure if this is the still the issue.