- January 1, 2012
- 588
- 216
- Home Country
- Germany
I repeatedly have the need to access my HTPC from remote locations via Remote desktop, e.g. when something is wrong and my wife cannot use MP but also several other cases. As it is a standalone HTPC, MP is set to autostart on windows.
So it'll start when I login via RDP (multiuserlogon enabled).
Here are my improvement suggestions
- MP hangs on the splash screen when RDPing to the HTPC and needs to be shut down by the task manager. (All recent versions at least back to 1.2, tested with streamedMP). Best thing would be if it wouldn't hang, but it may still give you issues when User 1 and User 2 are using MP with the same databases on the same machine. Suggestion is to recognize RDP logons and not to autostart MP then.
- With 1.8.1, when I use MP Config in an RDP session, it'll throw a .NET runtime error upon save&quit, didn't have that before.
As this is a "special use" which surely not everyone needs, priority is low at best. BUt please note it as a "it would be nice to have".
So it'll start when I login via RDP (multiuserlogon enabled).
Here are my improvement suggestions
- MP hangs on the splash screen when RDPing to the HTPC and needs to be shut down by the task manager. (All recent versions at least back to 1.2, tested with streamedMP). Best thing would be if it wouldn't hang, but it may still give you issues when User 1 and User 2 are using MP with the same databases on the same machine. Suggestion is to recognize RDP logons and not to autostart MP then.
- With 1.8.1, when I use MP Config in an RDP session, it'll throw a .NET runtime error upon save&quit, didn't have that before.
As this is a "special use" which surely not everyone needs, priority is low at best. BUt please note it as a "it would be nice to have".