If anyone knows about terminal server packaging rules please provide me the information about what are the ground rules for the applications which we package to run from terminal servers.
0 Comments   [ + ] Show 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.


Users are not able to trigger self-healing due to permission on executing msiexec.
So you will need to handle the userprofile files in some other way; loginscript, Active Setup (non-msi stub) or similar.
The HKCU registry will be handled by the shadow registry.
Install every packages as per-machine and make have as less HKCU entries as possible in the package.

You could also search the forum; as if I recall correct this has been up in the open before.
Answered 10/23/2007 by: AngelD
Red Belt

Please log in to comment
I think ActiveSetup will only work for for published desktops and not seamless applications. I've seen all sorts of creative solutions to populate the user profile but most sites I go to will use some sort of launch script to populate the user profile. I would make a WiseScript.exe to populate the user profile via launch script but I would also have a marker to act as a key path in the user profile so that if the user profile is reset that the profile will be populated.
Answered 10/23/2007 by: kkaminsk
Ninth Degree Black Belt

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