jeroen

The ext file is (and was) on the usb. It doesn't seem to contain any registration information other then:

<UUIDRegistered>true</UUIDRegistered>

The daily reminder still appears with the message that I have zero days left to register.

In the RemoteDesktopManager.cfg file both the RegistrationName and the RegistrationSerial values are empty.

The StandardRegistrationDate, StandardRegistrationEmail and StandardRegistrationTag are correctly filled.

Changing the Creationdate value to a more recent date will reset the 30 day counter to the corresponding remaining time. However, at the end of the changed 30 day trial the registration message will reappear.

I use Remote Desktop Manager 8.2.0.0 in portable mode (standard edition).

I have created the override.cfg file and entered a single dot in it as instructed.

I also moved the connections.xml file to the program folder.

Each time I log in to a new system or reset my Windows user profile I have to reregister because 0 trial days are left.

While troubleshooting I discoverd my portable configuration still writes registration information to the registry. (HKCU\Software\RemoteDesktopManager) with keys "Registrationdate", "RegistrationEmail" and "RegistrationTag".

However even if I import this information in the registry before starting RDM I still have to register with 0 days left.

In the remotedesktopmanager.cfg file I can't find any registration information, only a creation date which corresponds with the date the zero days left message appeared minus 30 trial days.

Hi,

We seem to have the same problem (still version 7.1.0), with a daily reboot and daily registration for the free version. The cfg file doesn't contain the previously mentioned StandardRegistrationTag. The registry does contain the registrationdate, registrationemail and registationtag values.

Can you help us?

OK, thank you for your time.

I just tested for this error with Visionapp Remote Desktop 1.5 (freeware) and 2009 (evaluation), it works just fime with UltraMon.

(I switched to your software because the old unlimited visionapp doesn't support the /admin switch and the new 2009 version is limited to 3 concurrent connections)

Because Visionapp also uses the RDP protocol, pretty much like the RDM does I suppose it will more likely be an error somewhere in the Devolutions Remote Desktop Manager than in UltraMon.

Please don't give it a very high priority, unless this is a larger problem than I can see now. I can work around the error easily by excluding RDM in ultramon and using normal drag and drop.

At the moment I'm not realy sure on which side the problem exists. I just tested moving a normal RDP window (from mstsc.exe) between my screens with UltaMon. That doesn't give any problems with the keyboard response. Obviously I can't check for the error when opening a session, I only get a movable rdp window after starting the connection.

Later today I will do some more testing with Visionapp in combination with Ultramon and see what happens there.

Update:

I tested for both errors on my other dual screen system where I use Splitview 2009. With Splitview everything appears to work just fine.

I have Remote Desktop Manager Standard 5.5.0.3 installed on a dual screen desktop (Windows XP SP3). On this system I run UltraMon 2.7.1.0 to control my window behavior.

When I use the UltraMon buttons to move my RDM window between my screens I get the following 2 problems:

1) When starting an embedded session in the session list the server becomes bold with a green arrow as normal. However the session doesn't open and the session name doesn't apperar above the embedded window.

2) The keyboard stops responding in any allready opened embedded session. (The mouse continues to work properly)

The problem exists only with embedded sessions and is also present in version 5.5.0.1 (which I used untill this morning)

When using normal drag and drop and resize functionality from Windows XP to control my window positioning everything works fine.

For now I've (temporarily) solved the issue by excluding the RDM in UltraMon, however I would like to be able to use UltraMon for my RDM window.