1. Enable Remote Desktop Windows 7

There are a lot of third party remote control pieces software around such as the popular freeware tools, and, but there are times when the built-in Remote Desktop Connection feature in Windows 7 is the most useful since it’s already present in Windows and you don’t need to install any third party software. All you need to do is to enable it because the Remote Desktop function is disabled by default. And allow connection from other computers by going to Control Panel - System - Advanced System Settings - click on the Remote tab.

From there, you can either select “Allow connections from computers running any version of Remote Desktop” which is less secure or “Allow connections only from computers running Remote Desktop with Network Level Authentication”. If you are setting up a connection to a different Windows version such as XP or Vista from your Windows 7 machine, then you need to choose the less secure option. Tip: Pressing the WIN Key+ Pause/Break keys simultaneously brings up the System window. If you only see the Remote Assistance box in the Remote tab but not Remote Desktop, that is because there are some restrictions that Microsoft has implemented in your version of Windows. Only Windows 7 Professional, Ultimate and Enterprise can accept connections from Remote Desktop but NOT for Windows 7 Starter, Home Basic and Home Premium. You can however, use Remote Desktop to initiate a connection from any edition of Windows 7.

Description of the Remote Desktop Connection 7.0 client update for Remote Desktop Services (RDS) for Windows XP SP3, Windows Vista SP1, and Windows Vista SP2. Oct 19, 2009 This package lets you to run many Windows Vista productivity applications from Windows 7-based PC using Windows Virtual PC or Remote Desktop.

Many branded laptops and computers come with Windows 7 Home Premium or possibly Home Basic pre-installed, but not to worry because there is a hack patch that can enable the Remote Desktop Connection in Windows 7 Home Premium with a single click. There is a tool called Concurrent RDP Patcher which is meant to enable concurrent remote desktop connections, which means multiple logons per user.

When you log in using the Remote Desktop Connection, the computer that is being controlled will show a message saying “Logged on remotely from COMPUTERNAME”. If you click on the user icon to login, the remote connection will be terminated with the popup: Your Remote Desktop session has ended. Another user connected to the remote computer, so your connection was lost. Try connecting again, or contact your network administrator or technical support group. This allows multiple users to control the remote computer using Remote Desktop.

Amazingly, this tool also enables the Remote Desktop Connection for Windows 7 Home Premium. The good thing about this patcher is you can revert the changes back to the way it was by clicking the Unpatch button. There are some scripts that can also do the same by patching termsvr.dll file but it doesn’t provide a way to undo the patch. By default a Remote Desktop Connection only allows you to login with a user account that has a password assigned to it. User accounts with a with a Remote Desktop Connection.

You can handily bypass that restriction by checking the “ Enable blank password logons” checkbox. The Concurrent RDP Patcher tool is released at forums, which if you never heard of it before, is the official Windows Media Center Community forum. The patcher was updated a while ago and is confirmed to work on Windows 7 Service Pack 1. It is also compatible with both 32bit and 64bit versions of Windows 7. Important Update Oct/Nov 2014 Although the original Concurrent RDP Patcher has worked fine since Windows 7 Service Pack 1 was released, in late 2014 Microsoft has again started to updated the termsrv.dll which is patched by the program.

As it appears to have been abandoned long ago, the original patcher will probably never get updated by its author to work with these new hotfixes. Luckily the Concurrent RDP Patcher source code was made available and we have updated the program to patch the latest termsrv.dll file. Currently Microsoft Hotfix KB3003743 (released on the 11th November) is the latest to break the original patcher. If you have this update installed you can try the updated program. Please note that this update to the patcher has not been fully tested so you should use it with care and at your own risk, although it should work without issue on all versions of Windows 7 except Enterprise. Any feedback on how well it works is welcome. We will try to update the Concurrent RDP Patcher in future if the are any more updates to the termsrv.dll library.

YOU GOT NO IDea how much stress I had. In the freaking middle of the night. Still 2hours to make this freaking server with 25 employees work. Stressed out. 2 hours left as they will start to work, since I’m on a different time zone. The entire company would be on production hold.

I’m talking about manufacture in a huge scale. What could I do??! Found this site.and it worked. Man If I ever knew who had this solution patch? I would personally send them a beer!! I am running Windows 7 Home Premium. Using information posted with the original patch (Concurrent RDP Patcher2-22-2011) I uninstalled Patch KB2984972 and then tried patching, but the patch said “unknown checksum”.

Enable Remote Desktop Windows 7

I Then found this post and I see that I do have KB3003743 installed (termsrv.dll is version 18637). I ran this patch ConcurrentRDPPatcherKB3003743Fix.zip. The Patcher says “termsrv.dll is patched”. However SystemProperties–Remote still only shows Allow Remote Assistance (and I can’t connect from another system). I’ve rebooted multiple times and tried uppatch/repatch but no luck. Any suggestions?

I can connect and fully remote in from my android tablet but only to the main user. I have a total of three users and when i try to remote into to ano other users it just keeps re-asking me for the password as if I had typed in the wrong passwords. I’m starting to think that it only works with one users. I tried to make two users to be administrators with passwords and it still only allows remoting to the first user that was originally the administrator. I have 64 bit windows 7 Premium and the android table uses the app called “Microsoft Remote Desktop”.

It works super good but only for one user in the desktop. Thank you for any help! Hi all, I’m still looking for a resolution for this.

I’ve been looking for the past 2 days and still having no joy. I’m trying to connect to a Windows 7 Home Premium from a Mac. Is there still not way to accomplish this without using a third party application? Would I need to upgrade to a newer version of windows? I like Windows 7 though. Forgot to mention, I’m trying to connect over the internet, outside the network.

I’ve setup port forwarding on the router. I cannot see remote desktop options in system preferences. Thank you for this. Works like a charm on my windows 7 home premium.

I have a quick question. How can I login to a same RDP session if I left it with unfinished work. For example if I login with user X and worked on a word document.

Can u close the RDP session without logging out and then log back into the same session so I can continue my work? Also on the desktop where I installed the patch, if I have my main user logged in with multiple programs running with my current work opened.

If I want to remote into that users desktop and preserve the work so I can continue remotely, what’s the best way to do that? Right now when I log in with the same user, it creates a new session and hence does not take me to the current working window.

Thank you again for this tool. Thanks for taking your time to update this tool. After installing your updated version on my RDP host, I can get to the screen where I enter the user name and password from my RDP client but nothing happens after that. I’m wondering if this might have to do with using Windows 7 Home Premium ‘K’ version (K for Korean).

It would help tremendously to get this to work so I can do part of my work at home. If the patching process just involves changing some of the codes in Termsvc can you please show which codes I need to replace? First of all, I’d appreciate your patch. But, unfortunately, after windows updates(Windows 7 Home Premium), I’ve failed to connect (Of course, before windows updated, I can login using RDP without any problem. After windows update, And also, I repatched it with KB3003743.) As colin said, I also have same symptom, it accept username and password, but then it never show any messages, no response just as like blocked by something. Could you please let me know what is problem? Thank you in advance.

Thank you for keeping this up to date. Some of the other versions of this have since stopped working, but after pulling the troublesome updates, your updated version does the job. I am having a problem with changing the ports, though. I’ve changed the port in the Registry, changed the forwarded port, and entered the connection in the IP Address:Port method, as well as restarting the services (and even the PCs themselves). For whatever reason, I can’t connect even with all the proper port changes.

This used to be possible with the now defunct MissingRemote version, but it doesn’t seem to take on this version. If you have any thoughts on the matter, it’d be much appreciated. Thanks again for keeping this up! Quick Heal is obviously talking rubbish, i.e. A false positive.

I compiled the Concurrent RDP patcher myself and it’s not malicious in any way. It’s flagged as malicious by some antivirus because it patches a system file (termsrv.dll) The result at Virustotal for the last released test version: virustotal.com/en/file/629af3522e7c32f63c304ad743f3f617d24b6a11c4703d41ad199f/analysis/ You’ll note both detections there have “gen” or “generic” in the result, that means they are making a guess at detecting it’s malicious, and getting it wrong. You are of course free to not use the program if you are in any way unsure about its safety. Thanks for writing this up, it’s working for me in Windows 7 Home Premium SP1. I have a question though about the resolution of the remote desktop, when I connect remotely the resolution of the Remote Desktop window is only 1024×768.How can I increase that? In the remote desktop session, in Control Panel Display Screen Resolution, the Display is shown as: 1.

(Default Monitor) on RDPDD Chained DD. Resolution: 1024 x 768. Both are greyed out and not changeable.

At the top of that window is a yellow box with the message: The display setting can’t be changed from a remote session. The system I’m accessing actually has a 1280×1024 LCD attached, so it appears that 1024 x 768 is hard coded somewhere as the resolution to use for remote sessions? Does anyone know how I can increase that resolution? BTW, I’m using CoRD on OSX as the RD client. Have run patch on my genuine Win7 Home Premium x64 SP1 without problems. It now says patched.

However, any RDP connection (local or remote) starts, asks for username+password, then brings up the remote desktop for 2 seconds and then TERMINATES immediately (closes remote desktop window). Only help seems to be to uninstall KB3003743 update. Is it possible the patch only works on cracked Win7 and fails on genuine ones? I have tried also the “RDP Wrapper”, same results – works only with KB update uninstalled.

Thanks for any ideas. Great work, thanks a bunch!

Last Patch Tuesday’s update killed it though. Not sure which update it was, but I got it working again with the patches below. Maybe you can include them in the next version? Original termsrv.dll MD5: 008CD4EBFABCF78D0F648C Patched termsrv.dll MD5: D3BABE04C2789C4C8D058B316C05E5A3 File offset 000173C0: Change 8B 87 38 06 00 00 39 87 3C 06 00 00 0F 84 EB C2 00 00 to B8 00 01 00 00 90 89 87 38 06 00 00 90 90 90 90 90 90 Offset 000176FA: Change 01 to 00 Offset 0005AD7E: Change 74 to EB (Same patches as in previous version, just different offsets.). THANK YOU SO MUCH!

Never been a big fan of using VPN software, and Don’t want to muck around with upgrading the OS on an OEM laptop. There always seems to be some problem with some software when you go this route. I can not thank you enough for the folks that made this tool.

RDP may not be the end all of how to remote in, but it is the best way to do it sometimes. And for me, I just don’t want to get up and mess with the laptop that is right next to me. Thanks to this software, I can put on movies for my kid, or Music for him to go to bed to all from the comfort of my chair. This just made windows 7 just that much better. As a user of 8, I have to say, there are just some things that Windows 8 just can’t do. Well, at least not without tons of help.

Again, You really just made my day. And my sons too! Hi Raymond, I met a problem of “asking of credential” input windows. Client: windows 7 prof host: windows 7 home premium Connection: LAN I have ran the patcher in the host computer, then, it installed successfully.

Then, I ran the Remote Desktop Connection in client computer, input the ip addresses, click connect, but a “windows security” dialogue prompted out asking for password. So, there is no password set on the host computer. May I know how to disable the feature of asking credential from the client computer in order to connect the host computer?

Hi I am using this patch on my win7 premium machine which is running my mailserver. For two / three weeks worked perfectly but has now taken to bombing out. The symptom is that the client cannot pick up mail “Outlook cannot connect to.” and at the same time RDP stops working. I am running MDaemon. If I go to the machine it all looks normal no sign of a crash. The mailserver is still running etc. The temporary solution is to start a configuration session for MDaemon – that unlocks everything.

But it isn’t elegant. Maybe I ought to buy VNC but before I do has anyone had this experience? Hi, I’ve come across this post & tried the above & it partially works! Hoping someone could please shed some light into why it won’t work completely. Much appreciated in advance.

Firstly, I’m using the RD Client on my iPad 2. The computer I’m remotely controlling runs 7 Home Prem & has wireless internet connection. When I access thru my iPad 2 on the same wireless connection (at home in another room) it works perfectly – I’m able to remotely access the computer, however, when I’m on another wireless connection (away from home) than I can’t login at all. Hope that makes sense as I can’t see why it doesn’t work!

UPDATE 10 May 2010: I finally discovered where the Remote Desktop team documented this process last December and thought it might be useful; UDPATE 20 February 2010: Sorry for how long the final solution took to discover, but thanks to Aaron Parker's blog entry at we now have the final missing pieces that allow remote applications to be hosted within a standard Windows XP SP3 virtual machine. UPDATE 5 July 2011: Kim Knight has now written a GUI tool for configuring remote apps which makes the process a lot easier and less error prone,.

(Note: new URL as of 9 Sep 2011) I have just tested the settings from Aaron on a Windows XP SP3 image running under VirtualBox 3.1.2 which previously failed with the dreaded ' The remote computer does not support RemoteApp.' As soon as the two extra settings were added to the RDP file (see steps c and d below), I could run Notepad via RemoteApp quite happily. I'll be doing more research into this and will update some of the screen shots in this post, but I thought I'd post this update as soon as possible to help people right away. What is RemoteApp? This is used within the XP Mode within Windows 7 to provide seamless application integration where applications running under Windows XP appear as application windows floating over the Windows 7 desktop. RemoteApp is only the remote display technology which enables this to occur.

It should be noted that XP Mode also includes logic to integrate start menu items and saving of documents and files which are not covered by RemoteApp alone. Why would you want RemoteApp? For all those people using XP Mode to run a nicely sandboxed IE6 for testing purposes, you can now achieve exactly the same result without having to install Virtual PC. This is important if you are already running virtual machines in another platform, such as VirtualBox or VMWare Workstation (or Player) as running Virtual PC XP Mode has a habit of causing your other virtual machines to crash with very little warning.

Also, unlike XP Mode, seamless mode in VirtualBox or ‘unity’ mode in VMWare Workstation, you can use this on a non local virtual machine. So you could happily have a network server with IE6 instances pooled for all developers. With VirtualBox and VMWare Workstation this also means we can use an application on 64-bit or multi CPU installations which XP Mode does not support. Step 1 - Configuring the guest virtual machine to allow RemoteApp access For Windows Vista and Windows XP you will need to install updates on the guest to enable RemoteApp (see below). Windows 7 requires now such updates.

This example uses a completely clean version of Windows 7 Ultimate RTM 64-bit, dual CPU, running under VirtualBox 3.1. We are going to enable Notepad to be run as a RemoteApp. The connecting client is Windows 7 Ultimate RC 64-bit, dual CPU.

This solution involved directly editing the registry, and this is not the ideal way of enabling RemoteApp, and I have omitted numerous registry keys which would be required by XP Mode (see resources for full registry value list). This is a minimal bootstrap to enable RemoteApp until the virtualisation and remote desktop teams provide suitable tools and fully document the process. Enable remote desktop connections on the guest. Run regedit (registry editor) and locate the key TsAppAllowList a) New Key, Applications. B) Under Applications, create New Key, 1234567 (the key name is not important, we just need any key for next two steps) c) In the new key, Create New - String Value, Name. Set value to Notepad d) Also in the new key, Create New - String Value, Path. Set to c: windows system32 Notepad.exe 3.

Navigate back to the TsAppAllowList branch a) Edit fDisableAllowList value, and set to 1 Step 2 – Creating the RDP file to access the RemoteApp Now the guest operating system has a RemoteApp created we need to use a Remote Desktop Connection to access that application. Run remote desktop connection, setup your desired settings as you would in a normal connection 2. Save the settings to an RDP file. 3) Use Notepad to open the RDP file to edit the configuration file, a) Modify the setting; remoteapplicationmode:i:0 to remoteapplicationmode:i:1 b) Add the setting; remoteapplicationprogram:s:Notepad c) Add the setting; disableremoteappcapscheck:i:1 d) Add the setting; alternate shell:s:rdpinit.exe e) Save the RDP file ( 20th February 2010 - thanks again to Aaron Parker's blog for steps c and d) 4. You can now use the RemoteApp by double clicking on the RDP to open with Remote Desktop Connection, a) Click on Connect when you see the security warning b) And after a short start to initiate the remote desktop session you will be running notepad floating over your VM Setting a Timeout for RDP connections When using RemoteApp one of the issues you may find is that when you exit the application that does not close the Remote session on the guest machine. This is clear on a desktop operating system as you will receive warning messages about users already being logged into the system. Clearly this is less than ideal, so I decided to find out how to ensure that closing the application caused the user to logout in a very short time period.

This is configured on the guest operating system. Windows key, Edit Group Policy. Computer Configuration - Administrative Templates - Windows Components - Remote Desktop Session Host - Session Time Limits 3.Double click 'Set time limit for disconnected sessions', change to Enabled, set to 1 Minute. Final thought Similar to VirtualBox seamless mode, you will not be able to move the floating guest application window between monitors, unless you save the RDP to use all monitors available. Either set this option prior to saving the RDP file, or edit the RDP setting multimon:i:1.

Summary As the keen eyed may have spotted, my laptop is still running the Release Candidate of Windows 7 as I have been too busy recently to upgrade to the RTM version. However, over Christmas I will be upgrading the laptop to RTM and I’m glad I did, because I RemoteApp means there will be absolutely no need to install Virtual PC and XP Mode when I can just run IE6 under VMWare or VirtualBox instead. Patches for Windows XP and Vista To enable Windows XP SP3 or Vista SP1 (or higher) to host remote applications you will need to install one of the following patches. Update for Windows® XP SP3 to enable RemoteApp™ (KB961742) Update for Windows® Vista SP1 or above to enable RemoteApp™, (KB961741) Resources The original article which started all this, from Ben Armstrong, Virtualization Program Manager at Microsoft ‘Virtual PC Guy’s blog’,. Which led to Remote Desktop Services (Terminal Services) Team Blog that revealed it’s all an RDP 7.0 thing, and not Hyper-V is just an enabling technology.

As Aaron Parker suggested by including a VirtualBox example on his stealthpuppy blog, 20th February 2010 update. And it was Aaron Parker's blog post that revealed the final missing settings in the RDP file that allowed me to finally run a RemoteApp from within a Windows XP SP3 virtual machine. Once I knew the TsAllowAppList registry key was involved I Bing later I found the very useful XP Mode analysis of this key at the C# Snippets blog, And for RDP configuration file editing, I found an excellent clue in Paul Monaghan’s article here. Which helped me guess that changing the remoteapplicationmode:i:0 value to 1 would help, and if you Bing remoteapplicationmode:i:1 then the careless folk at financelogix.com have kindly published their RDP file with the application name key within it, which gave me the last piece of the jigsaw. Finally the ‘Set time limit for disconnected sessions’, example may be for Windows XP but gave enough information for Windows 7,. Clayton, Sorry for delay in my reply, the Christmas holidays have been keeping me away from the keyboard.

In a spare moment I did try using a Windows XP image running under Virtual Box 3.1. I installed SP3 (it was previously only SP1), the RDP 7.0 patch for Windows XP (WindowsXP-KB969084-x86) and the patch listed in my post above (KB961742) but I couldn't get it working either. Next week I might have a go at running the Windows XP Mode VHD I have from Windows 7 RC, to run under Virtual Box 3.1. If that works, there are either extra configuration/firewall settings I haven't spotted, or the KB961742 patch isn't quite enough to make it work. Also, I might try that XP SP3 patched VHD under Hyper-V Server R2 and see if that helps.

That way we can isolate the issue to either the guest operating system configuration or the virtualisation platform. I will keep everyone informed of my progress. Trying to get remote app to publish a rdp connection to a hyper-v guest running windows 2003 terminal server. Basically i have an app 'Fuji Synapse' that cannot run in 2008 because of its requirement to have internet explorer 7 or below. I am trying to use 'remoteapp' and the hyper-v support to publish access to a working install on 2003 server. It works when i create an rdp file that specifies to run the app with the proper path.

However im trying to get it published under RDWEB for ease of access. Anyone done this before? Can I use this method to make Windows 7 into a RemoteApp 'server'?

I just want to be able to RemoteApp particular apps on my HTPC, as though it was a 2008/R2 server, with no virtualizing directly involved. I tried these instructions on my Win7 Ultimate HTPC, but I could not RemoteApp RDP into Notepad from my Win7 laptop, like I can with apps on my Win2008 R2 server. Nothing happens when I click the.rdp files, but a full RDP desktop connection works fine. Should I be able to do this or not? Some tips from my fiddling. First, do not set fDisableAllowList=1 or else you lose any control on what you allow remote users to run.

Remoteapplicationprogram:s:evenadirectpathtoanyexewilldo) Second, use a double pipe before the key name on the rdp file (eg. Remoteapplicationprogram:s: 1234567) Last, the step 'Create New - String Value, Name. Set value to Notepad' is not required. 'Path' is the only one really needed. Resuming, remoteapplicationprogram will cause a lookup for ' ' + any keyname inside TSAppAllowList Applications, and run whatever is pointed by it's 'Path'.

Les nuits sans Kim Wilde (05:17) 14. Laurent voulzy youtube. Bopper en larmes (04:39) 12. Liebe (04:05) 11. Desir desir (05:00) 13.

Took me a couple of hours to nail this, but I'm pretty impressed by this feature. I have managed to get it working. I previously made a mistake in missing the step to make the 'Applications' key. But it only works when I set fDisableAllowList=1, and as Tester says, this allows any program to be run.

That's not very secure. When I set fDisableAllowList=0, it does not work. I get the following error: The path shown in the error dialogue is correct, and this time I have followed the instructions correctly, but it looks like the relevant key cannot be found. @Tester I am not sure what your double pipes are supposed to mean, and adding them does not help.

The error message just includes them at the beginning of the path. I am naming the key the same as the Name string, and I have tried just using that name in remoteapplicationprogram:s: as well as the full path. I've got it working with fDisableAllowList=0, so that only authorised programs can run through RemoteApp. I did this by following the original intructions, but: 1.

FDisableAllowList=0 2. I named the application keys the same as the program name, as in the Name string 3.

I used Tester's double pipe in the.rdp file, but with only the application name (as in the key name and Name string), and not the full path. Now I can my Win7 Ultimate HTPC just as though it was a Win2008/R2 RemoteApp terminal server, yeah! Later on I will see if I can get all these RemoteApps published on TS-Web (running on 2008 R2), so I can access them through the internet using TS-Gateway.

I also want to see if I can get Win2003 serving RemoteApps on it. @Synapse Glad you got it. Let me recap with two simple steps, 1) make HKLM SOFTWARE Microsoft Windows NT CurrentVersion Terminal Server TSAppAllowList Applications, now on on Applications create a key named 'Whatever', and within it, a String key named 'Path' with the full path to the application. That's all that's required on the server. 2), on the client rdp file: remoteapplicationmode:i:1 remoteapplicationprogram:s: Whatever RemoteApplicationCmdLine:s:AnyParameterToPass That's all it took.

The RemoteApp technology I described here is designed to replace the Windows 7 XP Mode scenario. Being based on Remote Desktop to a workstation it will always log out the currently logged in user when the remote application is created. If you want to have multiple users accessing a remote application server I think you're better off looking at something like Microsoft App-V for Remote Desktop Services. Try the following URL for a free eBook (PDF) describing App-V usage scenarios, (short version - http://bit.ly/9vjzmQ).

Hi, i have been playing around with this and i end up failing. The host is a win xp SP3 with hotfix and RDP 7.0 the client is a win 7 home premium. (the host is running as a VM on vmware.

My problem is thr RDP file opens to a desktop view when you hit the show details. It does not launch the app.

I have tried just going with the direct path instead of the registry to no avail. Please do help me out. I dont think my file config is wrong because i had taken it from arons site and modified it but it may be the issue. Is there a way to check if the hotfix was installed correctly?

I have problem with remoteapp on virtual box. With everything setted up like it is described in this thread I have rdp connecting window with after a while enabled details button.

The session seems to hang out but in those details there is a windows session showed up - like mirror of vm machine (what is made within connecting window is visible on vm and vice versa). Another thing is that there is no login form (just showed actual vm's windows session) and furthermore managing allowed apps in registry nothing changes (f.e. No window that there isn't avaiable app within remoteapp). What else must be done to achieve expected results? Is there is some another tasks that must be taken to consideration? I must add that there is urgent request.

And that this procedure works fine with virtual pc (but there is need to use usb smart card devices which isn't possible with vpc). I see here is known in depth RDP and RemoteApp.

So if I can ask here for little help.;) One of my computers win'7 pro works just fine with RemoteApp (which in fact is network app server share app.exe) till few days ago. The login window just close and nothing happens. If I zeroed in.rdp option 'remoteapplicationmode:i:0' I see some errors which seems like.exe can't find work directory. I know that error from shortcuts I've created long time ago and this is necessary 'work directory' option. Any way, now I'm looking how to erase all data, stored after install/use RemoteApp application.

But can't find this data, where are stored???