jjjbos

Hi David,

I can confirm that it is working now. Thanks.

Best regards,

Jeroen

Hi David,

You can find the sourcecode attached. Workarea.au3 is a program to calculate the workspace dimensions and the Terminal Manager.zip does contain the source code to define and start RDP sessions (Still a bit buggy). The program has serveral components, but the main progam is Terminal Manager.au3.

Regards,

Jeroen Bos

Sorry, but no.

I relocated the taskbar to the bottom of my screen and after that I logged off and to windows with the same result. So having the taskbar on the top or bottom of my screen doesn't make a difference.

I think somehow the calculation of the correction factor is failing and therefore 0. I'm really willing to help, so if it is possible that you could send me a small program containig your code displaying the results of the calculation in a message box, I'm willing to run it and send back the results.

Regards,

Jeroen Bos

PS: Attached is a screenshot of calculations on my current desktop.

Hi David,

I included both a print screen of the top and bottom of my screen because I put the taskbar of my workstation on the top of my screen and the taskbar of my RDP sessions on the bottom, so it is easy to click the right one.

Regards,

Jeroen Bos

Hi Maurice,

I will try it when I'm at home tonight, because from my current workplace it is impossible to set up the vPN connection.

Regards,

Jeroen Bos.

Hi David,

Here are the print screens. For your information, I'm working from a different location today, so the screen sizes have changed......

Regards,

Jeroen Bos

Hi Maurice,

I have the same problem.

What I noticed is that after FDM thinks it has send the characters to the command line screen, it shows a popup screen saying that it is waiting for the VPN connection to be established. Maybe a adjustable delay for the popup screen can solve this problem.

Best regards,

Jeroen Bos

Hi David,

I did read the release notes of the last free version and I saw that you did put the solutions. So I downloaded and installed that version, however the solution for the working area isn't working for me.

The monitor I'm using right now has a resolution of 1680 x 1050 and a working area of 1680 x 998. The "desktopheight" in the RDP file generated by RDM is 1020. So it seems that the calculation of the working area isn't still right.

Regards,

Jeroen Bos.

Hi David,

I found a solution for the working area, I did set the "Remote Desktop Size" to "Custom" and for the width and height, I did put in the dimesions of my working area. And in combination with the adjusted winposstr, I get what I wanted.

Never the less, I hope you can get the working area correct by compensating for the CYCAPTION.

Best regards,

Jeroen Bos

Hi,

I understand, but with storing the credentials in the Windows Credential Manager all the cryto is done by Microsoft (of course you'll have to trust them) and you don't have to worry about that.

For the developers of RDM:

There is possibility to store different credentials for the same machine in the Windows Credential Manager:

- Store the credentials with an own unique identifier per connection.

- On starting the RDP session, copy first the credentials to "TERM/DNS name or IP address" and then start the RDP session.

This mechanism does work, because I have used it in my own autoit script for manging RDP sessions.

Best regards,

Jeroen Bos

Hi David,

I changed my display settings (Use advanced location) and that caused my RDP session to start maximized (See attachment). So if only now the working area could be correctly calculated, then everything would be perfect.

Best regards,

Jeroen Bos

PS: Some documentation on winposstr: https://technet.microsoft.com/en-us/library/ff393696(v=ws.10).aspx

Hi David,

I have also looked at the RDP file you generate in the background and I have noticed that the working area is calculated wrong. In the RDP file you generate, you calculate for my screen a desktop height of 1170, while it should be 1148.

In the past, I have also written a program to manage RDP session with autoit and for the calcultion of the working area, I used this code:

#include <WinAPI.au3>

#include <WinAPIsysinfoConstants.au3>

#include <WindowsConstants.au3>

Local $aWorkArea = GetWorkArea()

Local $CaptionHeight = _WinAPI_GetSystemMetrics($SM_CYCAPTION)

Local $ScreenHeight = $aWorkArea[3] - $CaptionHeight

Local $ScreenWidth = $aWorkArea[2]

; Get the working visible area of the desktop, this doesn't include the area covered by the taskbar.

Func GetWorkArea()

Local $tWorkArea = DllStructCreate($tagRECT)

_WinAPI_SystemParametersInfo($SPI_GETWORKAREA, 0, $tWorkArea)

Local $aReturn[4] = [DllStructGetData($tWorkArea, 'Left'), DllStructGetData($tWorkArea, 'Top'), _

DllStructGetData($tWorkArea, 'Right') - DllStructGetData($tWorkArea, 'Left'), DllStructGetData($tWorkArea, 'Bottom') - DllStructGetData($tWorkArea, 'Top')]

Return $aReturn

EndFunc ;==>GetWorkArea

When I started with the script, I also had a problem with calculating the right working area and then I found out that I had to correct for the captionheight.

I also found how to start the RDP session maximized with the taskbar visible. In your RDP file this option is set:

winposstr:s:0,1,0,0,1920,1200

If you change it to

winposstr:s:0,3,0,0,1920,1200

the RDP session starts maximized without borders.

Best regards,

Jeroen Bos

That doesn't make a difference, Both result in a maximized screen with local taskbar.

Another difference that I have noted, is that when I start my RDP session via:

mstsc.exe "C:\xyz.rdp" /admin /w:1920 /h:1148 /control

The RDP session is maximized, and when I start it from RDM the RDP session is NOT maximized. Maybe this explaines why my RDP session started via RDM doesn't look smooth.......

Here are the screen prints.

To be more complete, I start mstsc.exe via the command line:

mstsc.exe "C:\xyz.rdp" /admin /w:1920 /h:1148 /control

Hi Jeff,

Thanks for your answer.

I have tried that, but it resulted in a full screen RDP session and I want to have my local taskbar always visible.

Regards,

Jeroen Bos

Hi,

I've setup some external RDP connections with remote desktop size set to current working area size. The problem is that the remote desktop doesn't look smooth, letters are blurred and icons are cropped. This is due to the fact that the external remote desktop is started with borders around the RDP session. If I start a RDP session via mstsc.exe and set the remote desktop size to the dimensions of my workspace, I don't have the borders and everything is looking smooth (Screen prints can be found in the attachments).

Is it possible to start an external RDP from RDM without borders around the remote destop?

To be complete, I'm running RDM 3.0.13.0 on windows 7 SP1

Regards,

Jeroen Bos