Terminal Server application

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I have a TS that is not on my SBS server and having probmles installing
application. I can install it on and admin account and it will not work any
were else. If I try run it any were but the admin account it asking for an
INI file .. says X INI not found.. This is what I do go to command prompt and
type change user -install,
it then put the ts server in install mode and then I install the app. I can
use the app in an admin account cuse only admins can install but if I go to
another account if gives me that error. I have tried clopy the profile that
it works in to the profile that it dose not work in but still dose not work?
What I am doing worng?
 
Where is the ini file located after you have installed the program?
When you logon as a normal user, is the ini file that copied to the
\windows folder in the users home directory, as it should?
Could it be that the application has hardcoded the search path to the
ini file?
 
I'm beginning to think that this application is not TS-compatible
at all, and will need some serious hacking to make it work, if at
all possible.

Here are some relevant parts of the KB article
186498 - Terminal Server Application Integration Information
http://support.microsoft.com/?kbid=186498

<quote>
If you put a user's session in installation mode before you install
an application, the application is installed in the %SystemRoot%
directory instead of the user's home directory. If a user's session
is in installation mode, all changes that are made to an
application's INI files are written to this central location.
Putting the session in installation mode permits Terminal Server to
keep track of the user-specific application registry entries and
any INI files that the application may install during installation.
This permits Terminal Server to automatically propagate these
registry keys and files to each user as they are needed by
applications while they are in execute mode.

* If an application queries the WINDOWS directory by using the
GetWindowsDirectory API, Terminal Server returns the %SystemRoot%
Directory. If any INI file entries are added by using the
WritePrivateProfileString API, they are added to the INI files in
the %SystemRoot% directory.
* If the application does not use these APIs for modifying INI
files, the results cannot be predicted and can cause performance or
usability problems.
</quote>

So I'm suspecting that the application doesn't use the Windows APIs
and thus the INI file synchronization features of Terminal Server
don't work.

What you can do is to find out the exact location where the
application expects the INI file, when it is run from a normal user
account. Then make sure that every user can reach this location and
make sure that the INI file is there. If it is a location somewhere
in the user profile or home directory, that's fine. All you have to
do then is to copy the initial INI file in there, in your logon
script. If it is a location which is common to all users, like C:
\my_bad_app\bad_app.ini, then it will only work if all users can
work with the same shared INI file. In that case, you will have to
make it Read-Only.

--
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
--- please respond in newsgroup, NOT by private email ---
 
Vara

Thank you for your help it looks like I will need to do some change I saw on
this site that other people have had a slimer probmle with the app.. It is
Peachtree 2003
good thing this is only temp. Now I have reinstalled TS need to put it in
app mode.. I have look here on the site and have not seen it.. Can you help.??

Thank you..
 
Back
Top