Hi,

I'm trying to package an old legacy application at present to work in a TS environment but I'm not sure if it's possible.
The application writes a file to the C:\Windows directory during the installation and this file is then updated with server settings depending on the department that you are deploying the software to.

When the application is run it reads the file in the C:\windows directory and from that creates a list of available servers to log on to.

Is there any way to get this working on TS? Do I need to put the file into the user's Windows directory? And if so, how?

Thanks in advance,
Rgds,
Mark
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
If you install the application in "install-mode" it should be redirected by default to the user's "windows folder" under his/her profile.
Answered 02/16/2009 by: AngelD
Red Belt

Please log in to comment
0
I haven't done any packaging for Terminal Server. Are there any guides/FAQs out there?
Answered 02/16/2009 by: turbokitty
Sixth Degree Black Belt

Please log in to comment
1
I think we have had some discussions regarding TS/Citrix and packaging in the past so try searching, one I found was
http://itninja.com/question/how-do-you-roll-out-new-machines?0164&mpage=1&key=&#20164

However; "Terminal Server application integration information" should be enuf as a starter
http://support.microsoft.com/kb/186498
Answered 02/16/2009 by: AngelD
Red Belt

Please log in to comment
0
Thanks!
Answered 02/17/2009 by: turbokitty
Sixth Degree Black Belt

Please log in to comment
0
Just want to mention a quick gotcha here, please don't forget that while Active Setup works great with RDP/TS it does not work by default when you publish "seamless" apps in Citrix XenApp, due how to its "limited" logon process works. We've had some technical discussion about this before ..

I actually went ahead and did what I suggested back then, built .. a custom solution (sigh ..) that will actually parse the already existing Active Setup keys in a similar manner to Active Setup itself, but from a login script. Happy to report that this approach has been a success so far :-)
Answered 02/17/2009 by: jib
Purple Belt

Please log in to comment
Answer this question or Comment on this question for clarity