Has anyone run into a situation where a package that installs on Windows 2000 Terminal Server doesn't install on Windows 2003 server? What are the differences in these two environments that would cause a script not to install[&:]?
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.


A LaunchCondition is the first thing that springs to mind.

Any more info? Event log? Log file?
Answered 08/17/2005 by: WiseUser
Fourth Degree Brown Belt

Please log in to comment
If you're talking about script as in vbscript there may be some security settings preventing unsigned scripts to be executed
Answered 08/17/2005 by: AngelD
Red Belt

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