![]() ![]() The second WINE is installed, it can flawlessly run them. So I would not recommend this in any enterprise environment and will not post direct links here because I don not know the policy for such things here but there should be a patch for termsrv.dll for Terminal Server functionality which you can surely find with google and afaik there is also an RDP Wrapper Library that enables the functionality without modifying the dll.ĭownside here is that it's hard to say how the licenses are violated and whether these things work after a patch.Many programs work under WINE with absolutely no configuration. The downside with this method is additional lag by proxy and that it will not work unless there really is a person sitting in front of the Windows PC because you have to accept assistance.įinally there is a possibility to get terminal server functionality in Windows 7 but it is questionable how this violates any licensing agreements with microsoft. There you could run the command: msra.exe /offerra If you want to help other people with the remote session and require them to watch you could use "Windows Remote Assistance" instead, but would probably need to connect to a "proxy" windows computer first (unless there is linux support for it) This is helpful if the Windows PC is some kind of public info display, but not if you want to work on the computer and have others watch what you are doing. It will disconnect the RDP session and give it back to the console session. ![]() If it is ok to connect to the Windows 7 PC, lock the screen and then unlock it after leaving you can use the command: tscon.exe %sessionname% /dest:console ![]() There are several possible workarounds but each one has a different catch, so it might still not be possible to get you what you want. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |