I Locked my PC?
-
Hi All, Not a programming question but a Windows WTF, Locked my PC before lunch which was running a Remote Desktop to a test rig, went to the PC I'm running the remote desktop into to upgrade the Hardware widget's firmware. Closed the remote desktop session updated it, had lunch, went back to my PC and it's unlocked?.. :wtf: Anybody else seen that with remote desktop?, not really a big user of it.
-
First thought would be: how sure are you that you locked your PC, and not just locked the PC you were remoted into?
That was my first thought...
-
Hi All, Not a programming question but a Windows WTF, Locked my PC before lunch which was running a Remote Desktop to a test rig, went to the PC I'm running the remote desktop into to upgrade the Hardware widget's firmware. Closed the remote desktop session updated it, had lunch, went back to my PC and it's unlocked?.. :wtf: Anybody else seen that with remote desktop?, not really a big user of it.
Not exactly sure if this is what you did, but if you press ⊞ + L, it will not lock your remote session. Pressing the windows button isn't passed on to the remote desktop. More on that here: Passing the Windows key to a remote RDP session with #WindowsServer2012 – KeithMayer.com[^]
Wrong is evil and must be defeated. - Jeff Ello
-
Not exactly sure if this is what you did, but if you press ⊞ + L, it will not lock your remote session. Pressing the windows button isn't passed on to the remote desktop. More on that here: Passing the Windows key to a remote RDP session with #WindowsServer2012 – KeithMayer.com[^]
Wrong is evil and must be defeated. - Jeff Ello
I don't think glenn was trying to lock his remote system, but the local one, in which case, Winkey+L is still the correct approach. It does sound like his local system got unlocked when it lost the RDP session to the remote system however...which isn't something that should happen...
-
I don't think glenn was trying to lock his remote system, but the local one, in which case, Winkey+L is still the correct approach. It does sound like his local system got unlocked when it lost the RDP session to the remote system however...which isn't something that should happen...
Yeah, I was just hoping I was misunderstanding him.
Wrong is evil and must be defeated. - Jeff Ello
-
Yeah, I was just hoping I was misunderstanding him.
Wrong is evil and must be defeated. - Jeff Ello
Strangest thing I've ever seen with RDP: Had some app opened (in the RDP session) that displayed a combo box. Found out that somehow, even if I minimized the app, the combo box was still being drawn on the screen (floating on the desktop on its own) and I could interact with it (open/close the expandable list, pick an item...). Although I've had witnessed that sort of thing a couple of times in my decades of using Windows. But what makes this situation unique--when I minimized the RDP window, the combo box was still there (on the host's screen!) and I could still interact with it. How this was even possible, still to this day I can't even begin to speculate.
-
Not exactly sure if this is what you did, but if you press ⊞ + L, it will not lock your remote session. Pressing the windows button isn't passed on to the remote desktop. More on that here: Passing the Windows key to a remote RDP session with #WindowsServer2012 – KeithMayer.com[^]
Wrong is evil and must be defeated. - Jeff Ello
Jörgen Andersson wrote:
Pressing the windows button isn't passed on to the remote desktop.
That isn't quite correct. If I RDP on to a server, I can press windows key and it will bring up the windows start menu (on the server). So it does get the key press. However, if I press WIN + L, then it does seem to lock MY machine, as opposed to the server.
-
Jörgen Andersson wrote:
Pressing the windows button isn't passed on to the remote desktop.
That isn't quite correct. If I RDP on to a server, I can press windows key and it will bring up the windows start menu (on the server). So it does get the key press. However, if I press WIN + L, then it does seem to lock MY machine, as opposed to the server.
So it isn't the Win-button as such, but the mapped command
Wrong is evil and must be defeated. - Jeff Ello
-
Strangest thing I've ever seen with RDP: Had some app opened (in the RDP session) that displayed a combo box. Found out that somehow, even if I minimized the app, the combo box was still being drawn on the screen (floating on the desktop on its own) and I could interact with it (open/close the expandable list, pick an item...). Although I've had witnessed that sort of thing a couple of times in my decades of using Windows. But what makes this situation unique--when I minimized the RDP window, the combo box was still there (on the host's screen!) and I could still interact with it. How this was even possible, still to this day I can't even begin to speculate.
I remember that bug. This is possible because RDP isn't passing a picture between the computers but rather sends GDI commands to the host.
Wrong is evil and must be defeated. - Jeff Ello
-
So it isn't the Win-button as such, but the mapped command
Wrong is evil and must be defeated. - Jeff Ello
Hmmm, be more reason to skeptical of remote desktop...
-
Strangest thing I've ever seen with RDP: Had some app opened (in the RDP session) that displayed a combo box. Found out that somehow, even if I minimized the app, the combo box was still being drawn on the screen (floating on the desktop on its own) and I could interact with it (open/close the expandable list, pick an item...). Although I've had witnessed that sort of thing a couple of times in my decades of using Windows. But what makes this situation unique--when I minimized the RDP window, the combo box was still there (on the host's screen!) and I could still interact with it. How this was even possible, still to this day I can't even begin to speculate.
Have you used RDP with a windows server? You share the clipboard... I mean, when you copy something, another user logged in at that moment can paste your clipboard if the ctrl+v comes in something that can handle it as long as you remain logged in and no other user fills the clipboard.. It happened us a couple of times randomally, then I noticed it and could reproduce it.
M.D.V. ;) If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about? Help me to understand what I'm saying, and I'll explain it better to you Rating helpful answers is nice, but saying thanks can be even nicer.
-
I remember that bug. This is possible because RDP isn't passing a picture between the computers but rather sends GDI commands to the host.
Wrong is evil and must be defeated. - Jeff Ello
-
Have you used RDP with a windows server? You share the clipboard... I mean, when you copy something, another user logged in at that moment can paste your clipboard if the ctrl+v comes in something that can handle it as long as you remain logged in and no other user fills the clipboard.. It happened us a couple of times randomally, then I noticed it and could reproduce it.
M.D.V. ;) If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about? Help me to understand what I'm saying, and I'll explain it better to you Rating helpful answers is nice, but saying thanks can be even nicer.
Nelek wrote:
Have you used RDP with a windows server?
All the time. And clipboard sharing is definitely useful (between the local and remote systems), but you're right...two different people shouldn't be sharing the same clipboard content between themselves...
-
Have you used RDP with a windows server? You share the clipboard... I mean, when you copy something, another user logged in at that moment can paste your clipboard if the ctrl+v comes in something that can handle it as long as you remain logged in and no other user fills the clipboard.. It happened us a couple of times randomally, then I noticed it and could reproduce it.
M.D.V. ;) If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about? Help me to understand what I'm saying, and I'll explain it better to you Rating helpful answers is nice, but saying thanks can be even nicer.
Were you logged in as the same user on the server?
Wrong is evil and must be defeated. - Jeff Ello
-
Hi All, Not a programming question but a Windows WTF, Locked my PC before lunch which was running a Remote Desktop to a test rig, went to the PC I'm running the remote desktop into to upgrade the Hardware widget's firmware. Closed the remote desktop session updated it, had lunch, went back to my PC and it's unlocked?.. :wtf: Anybody else seen that with remote desktop?, not really a big user of it.
-
Were you logged in as the same user on the server?
Wrong is evil and must be defeated. - Jeff Ello
Nope, not even in same office (subnet), heck.. sometimes not even in same land.
M.D.V. ;) If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about? Help me to understand what I'm saying, and I'll explain it better to you Rating helpful answers is nice, but saying thanks can be even nicer.
-
Nelek wrote:
Have you used RDP with a windows server?
All the time. And clipboard sharing is definitely useful (between the local and remote systems), but you're right...two different people shouldn't be sharing the same clipboard content between themselves...
If I copied local and paste in RDP it was safe But if I copied in RDP, everyone could paste in RDP (not sure if paste local was crossed too)
M.D.V. ;) If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about? Help me to understand what I'm saying, and I'll explain it better to you Rating helpful answers is nice, but saying thanks can be even nicer.
-
That was my first thought...
-
Somewhere there must be a story of someone doing "format D:" thinking the cmd window was in the remote desktop, but was actually local.
I had thought of that :sigh:
-
Somewhere there must be a story of someone doing "format D:" thinking the cmd window was in the remote desktop, but was actually local.
I had thought of that :sigh: