Hi,
We have a fairly large amount of servers in our RDM database. Most are Windows servers and they are added to RDM as an RDP session. Before we used VisionApp and it was possible to rightclick a server and select "Connect with protocols" and then select ICA (for instance).
I understand we can add all our Citrix servers as an ICA connection, but then we'd have all our servers double (once RDP and once ICA). Is there some clever workaround?
Thanx!
Rob.
Hi Rob,
It's really simple with RDM as well. All you need is to create a template and a session script tool. We have a tips and tricks about that:
http://help.remotedesktopmanager.com/tipsandtricks_typesconnections.htm
David Hervieux
Thanx David, exactly what I was looking for. I do have a new issue, when I connect to a ICA connection and disconnect I get the following error:
COM object that has been separated from its underlying RCW cannot be used. I have 2 options, Go Offline and OK. If I click OK, everything works fine. If I click Go Offline, the obvious happens, it goes offline from my SQL datasource.
I've tried to reinstall the Citrix Receiver, doesn't change anything. All my users have the same issue.
Any idea?
Hi,
It seems to be an error when the ActiveX is disconnected. I will do some research to verify if there a solution but for now just click on OK and ignore the error.
David Hervieux
Could you verify the application log in Help. You might find more details (stack trace) about the error.
David Hervieux
The log stays empty. I've saved the log, cleared it and generated the error again. The log stays empty.
Could you go in File->Option and set the debug to 1 and reverify the log
David Hervieux
Ok, now i've got a different error:
System.Runtime.InteropServices.InvalidComObjectException: COM object that has been separated from its underlying RCW cannot be used.
at WFICALib.IICAClient.IsConnected()
at AxWFICALib.AxICAClient.IsConnected()
at Devolutions.RemoteDesktopManager.Frames.Embedded.FreEmbeddedCitrix.Disconnecting()
Great. It's an easy fix. I know the problem we already seen that with RDP. This will be fixed for the next minor update.
David Hervieux
Ahh! Great, i'll mark as accepted after the next minor update.
Hum,
This is strange. The error is already handled. Do you get this in the log or in the UI?
David Hervieux
In the UI, the log stays empty