/build/static/layout/Breadcrumb_cap_w.png

WTS 2003 server vs 2000

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

Answers (2)

Posted by: WiseUser 19 years ago
Fourth Degree Brown Belt
0
A LaunchCondition is the first thing that springs to mind.

Any more info? Event log? Log file?
Posted by: AngelD 19 years ago
Red Belt
0
If you're talking about script as in vbscript there may be some security settings preventing unsigned scripts to be executed
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login

View more:

Share

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ