Linked by David Adams on Thu 29th Sep 2011 23:47 UTC, submitted by lucas_maximus
Thread beginning with comment 491496
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
Features
Linked by Thom Holwerda on 05/18/13 21:33 UTC
Linked by David Adams on 05/16/13 4:23 UTC
Linked by Thom Holwerda on 05/11/13 21:41 UTC
Linked by Thom Holwerda on 05/08/13 14:22 UTC
Linked by Thom Holwerda on 05/02/13 15:28 UTC
Linked by Thom Holwerda on 04/29/13 21:06 UTC
Linked by Thom Holwerda on 04/24/13 22:24 UTC
Linked by Thom Holwerda on 04/18/13 11:21 UTC
Linked by Thom Holwerda on 04/16/13 9:29 UTC
Linked by Thom Holwerda on 04/15/13 22:44 UTC
More Features »
Sponsored Links



Member since:
2007-09-06
My desktop used to be in a seporate room from my TV. I would regularily work in the TV room through a notebook "thinkclient" giving me my power/apps/data and session login on the desktop. I've even seen a browser crash out only to recover the session when I next logged into the desktop directly.
The catch here is that any other valid user could go sit infront of the desktop and use it normally without noticing that I was also logged in and using it.
I've also seen several developers logged in and working on the same desktop through local and remote connections.
With a Windows desktop, it's one user at a time. With a Windows server it's one user at a time unless you shell out the cost of Terminal Server CALs.