i will look at that
thank you
If I am reading your post correctly, are trying to install LMI on a Terminal Server in Application mode or just via a remote desktop connection(RDC)?
We ran into issues with installing LMI via an RDC connection. You can elliminate this by installing LMI from the server desktop or change to the console connection by using- Start-Run- mstsc /console and this may work.
If this is a real terminal server then it is my recommendation not to use it on the server. We found major performance issues on Terminal Servers and Citrix servers. In this setup we use a different machine to LMI into and then RDC to the server.
The other reason that LMI works everywhere is that it creates an outbound connection on Port 80 that is used to get back to the machine. Remote Desktop does not create an outbound connection and therefore you firewall must be setup to forward the traffic to the correct computer.
Not 100% on what your asking here exactly but, I can tell you what we do and maybe it will help.
We typically run LMI Free or Reach on the servers we work on. WIth LMI Free installed you can access the server and do basic normal computer operations. If at that point you need to have more control of the server you can launch a Rescue session from within your LMI Free connection. Just point a web browser to www.logmein123.com enter pin code and go. After your LMI Rescue authnticates and you have cllicked the allow prompt from your LMI Free connection you just log out of the LMI Free part and continue on with your now established Rescue session. Rescue is nice in that it can pull the event id messages and system specs for help in troubleshooting specific issues.
The other option we sometimes use is the calling card feature. What you do is from your LMI Rescue session you start the file manager and transfer your Calling Card installer over to the Server and then run it from you LMI Free side. After this is setup the Calling Card icon will be on the desktop. You just have to double click the icon now to establish an LMI Rescue session. Doing this will emliminate the web browser step mentioned above but the rest is bascially the same.
We have found that LMI will work even on pc's or servers that have RDP connection issues. I questioned tech support on this and they said that LMI operates on port 80 and RDP operares on port 3389. Sometimes all ports outside of 80 and a few others including 3389 will be blocked by a firewall or router and not work. Port 80 is regular old internet traffic and therefore it is not blocked.
Hope this helps a little.
Just my two,
If you found this discussion useful, why not register/sign-in? It only takes a minute to share your feedback, ask a question, or vote for a new feature!
