Remotedsp windows 7

Click Connect. If you made your disk drives available see note above you will see a security warning about sharing disk drives. Click on OK. In the Log On to Windows dialog box, type your username, password, and domain just as you would if you were in your office and then click OK.

For employees, the domain is Hamilton-d. The Remote Desktop window will open and you will see the desktop settings, files, and programs that are on your office computer. Your office computer will remain locked and no one will be able to work at your office computer without a password, nor will anyone see the work you are doing on your office computer.

To improve performance, you will not see your usual desktop picture if one is in use. Instead it may be a solid color, usually black. Printing using Remote Desktop At home your printer is the default printer. To select your office printer, click on the drop-down menu where your printer is listed and select your office printer from the list. Click OK to print as you normally would. To log off and end a session In the Remote Desktop Session, click Start and select Disconnect You will be asked if you are sure you want to disconnect.

Click on Disconnect. Comments No comments yet. Last updated: February 27, Remote Access Windows 7. Close Search Hamilton. About Expand Navigation. Know Thyself. Just the Facts. Our Region. Our Diverse Community. Contact Us.

The offending update is Rollup update KB released in February We have created a new patcher that should work for this latest update. Please use it with care and at your own risk.

Of course, we welcome any feedback on how this latest patcher version works for you. We will do our best to update the Concurrent RDP Patcher if there are any more updates to the termsrv. Microsoft has updated the dll for the second time in and enjoys making life more difficult!

Rollup update KB will break things again. The below patcher is a test version and should be treated as such on bit and bit Windows 7 so please take care when using it. Seems not to be working anymore. Checked the patches, removed a couple of them. Repatched but not working. Which version shall I install? Is it needed to restart the machine after the patch?

Am I the only one? I have this problem. Perfect…or almost…. It allow only 4 remote connections…. Hi, Worked like a charm on Win7 Home Premium! Did not see the Remote Desktop option, but connecting worked fine anyway!

Thanks a lot! Hi, does this program run on windows 7 ultimate? Because when I use it it tells me that termsrv. The windows was last updated in Dig a little deeper,you will find the solution. RDP stopped working. Unpatching it did not fix it so RDP is down completely at this point.

Uncertain what else to try other than restoring OS from backup. Oh well, it was worth a try. I wrote that message too soon.

At first, I received an error message about TermServ. A couple of reboots and unpatch attempts failed to correct that. For some reason I tried again one more time and it worked … now logged in with 3 different users.

In fact, it seems to be working. Can access other desktops remotely using RDP client. Home can have RDP activated, it takes more work. Most Complaints are from people that do not understand how RDP works or is configured,just shoping for a button click solution. Have Widows 7 Home Premium. Install of the patch went fine.

I tried patching and unpatching each version for troubleshooting purposes. Here are my two observations. All I see is the Allow Remote Assistance checkbox. My client PC screen then shows the remote connection bar at the top of the screen looking like it is about to connect.

It even flashes a dark blue background with Waiting to Connect something like that on the screen. About a second later the connect screen then goes away.

The connection is closed. Hi I have downloaded the latest patcher to use with Win 7 Professional but i seem to be failing on attaining multi users.

Thank you man. You did a very good job. This saved my job! A beer is waiting for you. Thank you very very much. The only sad thing for me so far — it does not work for W7 Ultimate. After you have those Errors, search those and you will find people that also had those errors, and how to fix them. So tell me please. Running the patch tool gives me a message termsrv. I can toggle from patched to unpatched. Do I need to restart computer?

What am I missing if anything? Win 7 Home Premium Is there any fee for the release of the password? Do the Jan. Thank you! Then installed your successful April patch. Am also running in a VM so I have an easy image of the whole shebang…. If I am setting up from scratch, do I download the original and all patches and run them one by one? Concurrent sessions work again, thanks!!!! Hello, Thanks for that patch. I downloaded and ran the April patch termsrv. I have W7HP. Thank you. Maybe there will be an update soon?

I got an error that says termsrv. The concurrent patcher is a great tool thanks. It does not seem to work with the newest Bluekeep patch KB does it? I have a PC with all updates and this works fine. Thank you, thank you, thank you!!!! So today I took my time and read down and down and down through this web site and finally tried the final April patch and it works just as you would expect.

Maybe you should update your site and put the April patch at the top or even remove all the older patches. All I can say is thanks, thanks, thanks for keeping after Microsoft.

They are good at upsetting things. Thanks, Nick. This patcher version breaks the remote desktop by not letting me see anything that is currently open,program wise. Just desktop with my icons on it. It seems only 3 user can log in at the same time. But I have another problem. Fast check not double checked , Multiple Remote Desktop from 3 different user are working perfectly.

So the first user already connected will not be disconnected if there are same account login again from another PC. Just a little bit confused to change how many user can connect at the same time.

If already 3 user doing remote session at the same time, the 4th user totally can not RDP to this host. Am I missing something? Any chance for support? For me, the RDP patches failed after installing the Microsoft Security update for the critical wormable. The checksums have been updated for the Zips. It works with the latest April Security rollup patch for Windows 7 x64 and x Btw, do the patcher contain all earlier patches, or do I need the older versions for older win7 machines?

Each one supports the default Service Pack 1 dll, the KB patch from and whatever latest patch is listed in the article. If you want support for Windows 7 RTM, download the original patcher. Thanks for your work on this. Any help would be greatly appreciated. Thanks, HAL! I was thinking the SHA1: was the password but I see on the download page the password is listed.

Sorry for the confusion. Dear Sir, thanks for your effort but link to patcher April is srill the same: bit only. Just tested! April Test Version works perfect Windows 7 bit. Thank you so much! Keep up with great work! Thanks HAL This morning I tried 64bit and worked pergectly. Now this new version is asking for a password. Please, there are still many of us who have Windows 7 bit there are reasons for that! Please make bit version!

Thank you :. I came to report it after uninstalling both KBs and getting it back to work. I really appreciate your work sir! Not for me: KB Monthly rollup replaces termsrv.

Please update the RDP Patcher. Nope it does not — I get error message that termsrv. April Update has changed termsrv. Ran this today, 5th of April. I think there were some updates from April that are blocking this. I am also having issues with this. Is it alright, or it is some problem on my remote OS? Is there any other step I have to do? Also, thanks for your work on this project!

We have 5 RDP clients working concurrently after patching Termsrv. Not sure why the original author excluded Enterprise, must have been a valid reason for it though.

If you are having trouble with the patcher where it says it cannot access file termsrv. Once you Un-install this you will be able to use this patcher. I was finally able to update all the security patches and use this patcher.

It works with the March security updates. Thanks for confirming it works with the March updates. Yes, obviously if you have something like RDP Wrapper installed it will interfere with the operation of this tool. Thank you so much for your ongoing maintenance of this patch. System is Windows 7 Home. Is there any way commands to set the options automatically on this installer?

I cant push it automatically because of the two check mark options during install. I use thin clients with it but connects only two.. Im using windows7 profesional. You should probably warn people that if you use this to allow more than one user to connect to the system, at the same time, you are in violation of the Windows 7 EULA.

When I download it I get a warning:. Some security applications dislike tools like this because they patch system files and edit registry entries, which is similar to what malware might do. I tried the Feb patch on W7 Prof French version. Not working. When trying to remotly connect, the session start but then stop. If a running session on console, this session is not impacted at all.

I still have problems with a KB version of Windows 7 Professional, I tried all 3 version but got always the same error of inknow checksum. Find out what the version number of the dll is. As far as I recall, there were no new dlls between October and October , so you might have the dll.

This is a fantastic tool. Works flawlessly here following KB What am I doing wrong? I stopped Remote Desktop Services and still saying cannot access file termsrv. Are there other processes that need to be stopped? Hi HAL! Deinstallation of KB solved the to the state before. Do you have patch for KB?? Please we need patch. Hallo, Windows 7 x64 Home Premium 6. PS: Hal, any link with the info about what has to be changed and where?

I understand is something that has to be done with en hex editor to the file, correct? There is no specific page but several pages around the internet with plenty of old information about the bytes to change. The tool is, in fact, a mixture of functions. Ok, thanks you for the clarification. I assumed it was just a few bytes on the dll and though of not bothering you again. Zerox you are correct so thank you for that.

I notice that KB is optional anyway so I will leave it uninstalled for now. For a list of the files that are provided in this update, download the file information for update I just uninstalled KB and declined future installation for now on this machine.

Now my W7Pro termsrv. Microsoft just do it again KB updates termsrv. Hello again! Microsoft released a new termsrv. Is there someone that know what is that has to changed in the file so we can do it manually and be done with it? Or if HAL has the time to commit a new version that recognizes this new checksum. What an enormous time saver since I can now connect remotely as the admin user and fix things without disturbing the local user!

Do you have a tip jar? Thanks again! I have been trying to get RDP to work for weeks. I have Win 7 Home. I set a password on the target machine my home laptop. What more do I have to do? It needs updating again. I did a full update with the latest rollups and the patcher works.

It seems even smart enough to restart RDP service because no reboot required! Skip this step if this box is already checked. Add more users if necessary. If you want to allow Remote Desktop access to another user account on the target computer, do the following: Click Select Users…. Click Add. Click Advanced…. Click Find Now. Scroll down in the pane at the bottom of the window and double-click the name of the user you want to add.

Click OK on the top two open windows. Click OK. It's at the bottom of the window. Doing so saves your settings and enables Remote Desktop on your target computer. Part 2. Click Control Panel Home. Doing so takes you back to the main Control Panel window. If you closed Control Panel, re-open it before proceeding.

Click Windows Firewall. It's in the list of Control Panel options. Click Allow an app or feature through Windows Firewall. This link is in the top-left corner of the page. Click Change settings. It's at the top of the page, just above the list of programs in the middle. Scroll down and check the "Remote Desktop" box.

You'll find it in the "R" section of the list of programs. Doing so will allow Remote Desktop through the Windows Firewall. Go to source. This saves your changes. Part 3. Consider setting a static IP address. This is optional, but recommended. A static IP address won't change when your router disconnects or your computer reconnects to the network, meaning that the IP address you find now will work in the future; failing to do this means you'll need to find the IP address of the target computer whenever you want to connect to it.

Go to your router's IP address in a web browser and log in with your router's credentials if prompted. Find the list of currently connected computers and select your computer. Thank you Jose'! This is a perfect and easy solution!

Thursday, November 27, AM. I am not sure why some professionals cop such a 'holier than art thou' attitude. More than likely he is only a 'legend in his own mind' and knows less than most, but thinks he knows more than most.

Bradford W Brown. Tuesday, December 23, PM. Thank you so so so much. That should be the number 1 solution, not those lame comments. Saturday, December 27, AM. If not go to Start and there search for command prompt.

In command prompt type the below. Friday, February 13, PM. The answer you were looking for was to use Windows Security which appears on gui right above Logoff arrow after clicking Windows start button.

Wednesday, February 3, PM.