RDP Wrapper does not patch termsrv.dll, it loads termsrv with different parameters.Source code is available, so you can build it on your own.If you have modified it before with other patchers, it may become unstable and crash in any moment. It's recommended to have original termsrv.dll file with the RDP Wrapper installation. This solution was inspired by Windows Product Policy Editor, big thanks to kost :) Also this method is very strong against Windows Update. RDP Wrapper works as a layer between Service Control Manager and Terminal Services, so the original termsrv.dll file remains untouched. So remember, if you're local res is 1440x900, you either need to run your RDP client in full screen mode (appears as if it is your local desktop), or, in order to run it as an obvious windowed app, you'll need to adjust your custom screen resolution to something slightly smaller, which will yield a window about the size of your entire desktop, but without appearing as if it is your local desktop - this is what many prefer, as they find it confusing otherwise.The goal of this project is to enable Remote Desktop Host support and concurrent RDP sessions on reduced functionality systems for home usage. You can also set 24bit color with a hack, because it's disabled by default, although there's really no need for most folks, and although some people like to disable printing, I find that using remote apps and printing locally via RDP is not only a dream, but part of my regular tasks on a daily basis. They don't follow the same set of rules as the rest of your desktop, so just make a note of that when setting your resolutions, and set your preferences according to how nicely the Windows desktop fits into your workspace, because you're just going to have to get used to moving those DOS-like windows about, as they'll always be a bit clunky. For all of us UNIX folks, we're going to be using things like vcenter, putty, etc., in our remote windows sessions, and whatver you want to call your DOS-like consoles, well. Many RDP clients also allow you to set a 'custom' res just prior to connect, and yes, most clients will remember your last sessions. To have your RDP client (Since we appear to be talking about MSTSC.exe here) session occur in a window itself, while avoiding the scroll bars (or the afore mentioned resolutions which are less than optimum), the /h:900 /w:1100 parameters suggested above are a great starting point, but with all things YMMV, so play with it until you get it just so ) Must more convenient is to choose to use your current desktop resolution, but in many clients this will yield less than desirable results (You get the scroll bars) unless you toggle full screen. yes, you could choose a smaller resolution, say, 1024x768 or 800圆00, and they would yield acceptable results - if what you're seeking is to avoid scroll bars withing the RDP instance itself. The 1440x900 laptop issue is quite common. I can't attach the manifest file so here is the contents: The RDP app is %windir%\System32\mstsc.exe so the manifest file is. Next is to provide a manifest file for a given application – the executable file name followed by. Enter a Value Data of 1 and select Decimal.Right-click PreferExternalManifest, and then click Modify.Type PreferExternalManifest, and then press Enter.Right-click, select NEW→ DWORD (32 bit) Value. HKEY_LOCAL_MACHINE→ SOFTWARE→ Microsoft→ Windows→ CurrentVersion→ SideBySide
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |