In Windows based devices, the RDP protocol is capable of having a few sessions available of which the MSP360 Connect agent defaults to session 0. I would propose being able to connect to a named session or be given the option to spawn a session not as session 0. I use Windows Server 2019/2022 and frequently use RDP sessions and leave them open with apps running scripts or other activities that don't necessarily warrant me running it as RMM task. It would be nice to have this and not have to worry about it being on console session 0 that an end user could potentially affect if they are physically by the server in question.