 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
Windows Server Forum / Windows NT / Terminal Server / April 2006can an application be fooled into not detecting TS?
Can an application be fooled into not detecting that it is running on a terminal server? I need to try something remotely while I'm out of town (or I can't go!) but it says that it can't run over TS. Why that is I don't know but if I can fool it maybe I'll find out why it cant run. I imagine it was the color limitation or some other trivial issue. But I'll never know if I don't try. Can it be done fairly easily? Sorry for the multipost Can an application be fooled into not detecting that it is running on a terminal server? I need to try something remotely while I'm out of town (or I can't go!) but it says that it can't run over TS. Why that is I don't know but if I can fool it maybe I'll find out why it cant run. I imagine it was the color limitation or some other trivial issue. But I'll never know if I don't try. Can it be done fairly easily ... or at all?? Have you tried running the install process from the console, or assigned via Group Policy. Have you tried w/ & w/o putting the server in install mode?  SignaturePatrick Rouse Microsoft MVP - Terminal Server http://www.sessioncomputing.com > Sorry for the multipost > [quoted text clipped - 6 lines] > don't try. Can it be done fairly easily ... or at all?? > The installation works as does the program locally but the program won't open from another machine over the TS connection. I'm not sure what you mean by "putting the server in install mode" > Have you tried running the install process from the console, or assigned > via [quoted text clipped - 14 lines] >> I >> don't try. Can it be done fairly easily ... or at all?? Sorry about that. Sometimes I make assumptions that I shouldn't. Install mode is what you do, or an MSI does automatically when installing on a 2003 terminal server. We used to have to do "change user /install" before installing a program that needs to store individual user settings, and do "change user /execute" when the install is complete. In 2000, this functionality was enabled via the Add/Remove Programs Control Panel Applet, and in 2003 this is enabled by default when launching any MSI based install. That being said, most of us still do thigs the old fashioned way, as we do NOT assume anything. When enabling this setting from the cmd prompt, you can verify which mode you're in via "change user /query". If your server is 2003, try connecting to the console session with your Remote Desktop Client, by launching mstsc.exe /console. This may fix your problem, if you're the only one who needs to run this application. SignaturePatrick Rouse Microsoft MVP - Terminal Server http://www.sessioncomputing.com > The installation works as does the program locally but the program won't > open from another machine over the TS connection. [quoted text clipped - 18 lines] > >> I > >> don't try. Can it be done fairly easily ... or at all?? I had no idea... Explains an installations wierdness sometimes however... Thanks, I'll give it a whirl > Sorry about that. Sometimes I make assumptions that I shouldn't. Install > mode is what you do, or an MSI does automatically when installing on a [quoted text clipped - 44 lines] >> >> I >> >> don't try. Can it be done fairly easily ... or at all?? |
Reply to this Message |
 Sign In
 Join
 My Latest Posts My Monitored Threads My Blog My Photo Gallery My Profile My Homepage Start New Thread Enable EMail Alerts Rate this Thread
|
©2009 Advenet LLC Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.