We are trying to package Office 2003 for citrix server. when we install the raw media of the office 2003 it is self healing everytime a new users logs in. Can anybody tell me a way to rectify this problem in citrix environment. If an application is self-healing for a particular user and at the same time the application is being used by some other user then what will happen?
what all things we need to be take care if an application is to be packaged for a multiuser environment like a citrix server. Kindly give some suggestions.
0 Comments   [ - ] Hide 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.
Answer this question or Comment on this question for clarity


If you select the Installation Expert Tab and the Package Options -> Administrator Options... Makesure that the "Install for Profile" has per-machine installation selected. Try that and let me know
Answered 12/06/2005 by: LawrenceTucker
Yellow Belt

Please log in to comment
I have tried that still it is giving the same problem.

Can anybody send me any document or a link where i an find out how a server application needs to be packaged. what needs to be thought of when u are packaging applications for win2k3 server.
Answered 12/07/2005 by: sidverma
Senior Yellow Belt

Please log in to comment
You can get some good information on this subject from the Citrix support site itself.

Office2003 should only repair (if ever) the first time a new user logs onto that particular server. This is because the MSI is attempting to write the HKEY_CURRENT_USER registry information.

When Office2003 is installed properly onto a Terminal Services server, it should write these HKCU keys to the Terminal Services SOFTWARE key stored un the HKEY_LOCAL_MACHINE hive. When a user logs on, Terminal Services copies these keys over to the HKCU hive for that particular user.

Check the application event log on the server to see which component the MSI is trying to repair/check etc. Then match this up in the MSI, and troubleshoot.
Answered 12/20/2005 by: brenthunter2005
Fifth Degree Brown Belt

Please log in to comment