Facebook Plunges Again
Tumblr 101: Tips And Tricks To Get Started
Run Windows 7 on two different computers from only one install
The Windows 7 beta has gotten a warm reception (to put it mildly). Still, what if you want to play with it on a second system without actually going through the lengthy install a second time?
Thanks to some enterprising enthusiasts, one option at your disposal is to enable concurrent sessions. For those of you not familiar with the term, here's a simplified explanation. It means you can have more than one user logged in to Windows at the same time, and neither one ever sees the other one's desktop.
It's done via RDP, the same way fancy (and expensive) MS Terminal Server setups work. This solution, however, has been generously made available to the public for free. Just download the Concurrent Sessions Enabler zip file (f you don't see the link, search for download here). Right-click install.cmd and choose run as administrator from the context menu.
Thanks to some enterprising enthusiasts, one option at your disposal is to enable concurrent sessions. For those of you not familiar with the term, here's a simplified explanation. It means you can have more than one user logged in to Windows at the same time, and neither one ever sees the other one's desktop.
It's done via RDP, the same way fancy (and expensive) MS Terminal Server setups work. This solution, however, has been generously made available to the public for free. Just download the Concurrent Sessions Enabler zip file (f you don't see the link, search for download here). Right-click install.cmd and choose run as administrator from the context menu.
Command line arguments are available: -multi allows multiple sessions per user, and -blank allows users with blank passwords to sign in via RDP. To utilize them, just create a shortcut and add them to the end of the target.
Obviously, there are some security risks with this especially if you allow remote logins with blank passwords. Make sure you've done your best to secure your network and PCs (which would likely involve not having any user accounts with blank passwords) before enabling concurrent sessions.
Thanks, Alan!
Comments
11
Subscribe to commentsRajFeb 3rd 2009 10:21AM
Looks Cool. Thanks for the link
Name:Feb 3rd 2009 10:48AM
This looks like it's illegal and against the EULA.
cubiclegangstaFeb 3rd 2009 11:29AM
"This looks like it's illegal and against the EULA."
This looks like it is ADVANTAGEOUS and SCREW the EULA."
- there, I fixed it for you.
User001Feb 3rd 2009 12:24PM
FYI, MissingRemote originally had this guide Jan 23rd.
http://www.missingremote.com/index.php?option=com_content&task=view&id=3293&Itemid=232
Lee MathewsFeb 3rd 2009 12:25PM
They sure did, and that's who sent us the tip. I like to take a little time to test stuff like this, though.
daveFeb 3rd 2009 5:32PM
Is RDP not included in the beta? I'm wondering why you wouldnt just use RDP straight up for this, instead of installing that concurrent enabler thingy.
PulsiveFeb 3rd 2009 2:21PM
Because, to use RDP you actually have to have an OS session running, this circumvents that.
master811Feb 3rd 2009 2:37PM
Actually you don't need to have an OS session running to use RDP, as long as the computer is turned on, you can login via RDP to your normal account just fine.
JamesFeb 3rd 2009 6:52PM
I think the point is that if Alice is logged in and Bob tries to RDP from another system, he must kick Alice out to log in. Concurrent use is more like the *NIX model -- the terminal "front end" is different from the "back end" that processes the session.
KirbyMeisterFeb 4th 2009 11:04AM
Actually the model is the same - the switch on concurrency is just an artificial restriction so that you have to use Windows Server 2008 and pay per-seat CAL charges.
master811Feb 3rd 2009 2:45PM
I should add the whole point of this, is that even though RDP is included, it only ever allows one user to be logged on at once, this way you can logon as a completely different user without forcing the other to get logged out.