Program Won't Launch in Terminal Server, Will Launch Otherwise

[Guest Rosman Computing]

My client is using Windows 2003 SR2, "relaxed" security. They are also

running Citrix on the server.

They just switched to this new Server...they are running a CRM program

called Maximizer which is supposed to launch a small word processor. It's a

relatively small program.

When you are at this machine from within the building, the program launches

normally. When you login as a client through Terminal Services, nothing

happens. I tried making this file an EXE and lanching it from out side the

program, but when you double-click it, nothing happens.

This program has a few DLL dependcies it uses...like Winfax.dll in the

\SYSTEM32 directory, a spelllcheck in the \COMMONFILES directory. I checked

and they all seem to be there.

Any one have an idea why this little mini program won't launch when

accessing a a remote client, but works fine when you're actually at the

machine?

thanks,bill

[Guest mst3in@gmail.com]

Re: Program Won't Launch in Terminal Server, Will Launch Otherwise

 

An app developer can deliberately prevent thier app from being used in

a TS environment with only a few lines of code...a call to

GetSystemMetrics to see if the sessions is a terminal session, and/or

an os version check to see if the OS is running in TS application

mode.

 

(these same API calls are also used by "good" devs to limit the amount

of resources used or otherwise alter app behavior)

 

However, big problems can occur (details dry and boring) if the app

was installed before "terminal server application mode" was enabled.

This issue does NOT apply to all apps, just a few (MS office for one)

 

Does it work on an XP machine using remote access? Does it run

properly on the console? How about using sysinternals tools filemon

and regmon to detect access denied issues...."relaxed security" does

not unnecessarily mean this is not a security related issue.

[Guest Rosman Computing]

Re: Program Won't Launch in Terminal Server, Will Launch Otherwise

 

I believe they had this program working properly on an olderversion of

WIndows Server with Terminal Server. They just upgraded the TS Server to a

newer versiosn and found this problem. The Maximizer CRM program works fine

except for this one little mini-app that the progrram calls.

I called Tech Support and they had me rename this mini-app into an EXE and

see if it would launch, and it didn't.

The program works fine if you launch it from the PC console itself, just not

in a TS session.

So I'm guessing that 1) the program has something in it that Windows Server

2003 doesn't like, or 2) there is some security setting somewhere preventing

it.

 

When I log into TS, I am logging in remotely into TS as an Administrator,

but it stoill doesn't launch.

br

 

"mst3in@gmail.com" wrote:

> An app developer can deliberately prevent thier app from being used in

> a TS environment with only a few lines of code...a call to

> GetSystemMetrics to see if the sessions is a terminal session, and/or

> an os version check to see if the OS is running in TS application

> mode.

>

> (these same API calls are also used by "good" devs to limit the amount

> of resources used or otherwise alter app behavior)

>

> However, big problems can occur (details dry and boring) if the app

> was installed before "terminal server application mode" was enabled.

> This issue does NOT apply to all apps, just a few (MS office for one)

>

> Does it work on an XP machine using remote access? Does it run

> properly on the console? How about using sysinternals tools filemon

> and regmon to detect access denied issues...."relaxed security" does

> not unnecessarily mean this is not a security related issue.

>

>