modifying unpackaged applications installs using vbscript?
Hi. I work for a large engineering company in the UK as an application deployment analyst.
This entails, doing initial discovery of application, writing up instruction for installation for packagers, then doing i initial quality assurance\uat, then distributing the appllication via sms. Most applications are packaged, but then due to sla's there are some that we don't package, and just deploy direct from media onto sms.
Some of these applications (that are not packaged) do not install very well, e.g. instead of installing to c:\program files, they install to root of c: drive. There are some which do not create shortcut on start menu.
Is there any vbscript that can be run to remedy this so that a vendor msi or vendor setup.exe file can be modified (without packaging) so that it installs to c:\program files, and creates shortcut on the start menu, and removes shortcuts from the desktop, and adds lock permissions.
Please advise. This would be very much appreciated
This entails, doing initial discovery of application, writing up instruction for installation for packagers, then doing i initial quality assurance\uat, then distributing the appllication via sms. Most applications are packaged, but then due to sla's there are some that we don't package, and just deploy direct from media onto sms.
Some of these applications (that are not packaged) do not install very well, e.g. instead of installing to c:\program files, they install to root of c: drive. There are some which do not create shortcut on start menu.
Is there any vbscript that can be run to remedy this so that a vendor msi or vendor setup.exe file can be modified (without packaging) so that it installs to c:\program files, and creates shortcut on the start menu, and removes shortcuts from the desktop, and adds lock permissions.
Please advise. This would be very much appreciated
0 Comments
[ + ] Show comments
Answers (1)
Please log in to answer
Posted by:
aogilmor
17 years ago
The approaches you'd take to a vendor MSI and EXE are totally different. For the MSI the best method is to transform it using your favorite tool (or Orca from Microsoft) to make it install to the directory you want.
For the EXE every vendor is different. Some support silent installations, which could be handled by scripts to varying degress, while others do not. If it does not you're stuck with either repackaging, or using some kludgy tool like autoIT (don't get me wrong, I love autoIT as far as it goes, but it's not a good tool for enterprise deployments. its author has said as much).
In short, no, there's no way you can be assured of doing all that you need with vbscript.
For the EXE every vendor is different. Some support silent installations, which could be handled by scripts to varying degress, while others do not. If it does not you're stuck with either repackaging, or using some kludgy tool like autoIT (don't get me wrong, I love autoIT as far as it goes, but it's not a good tool for enterprise deployments. its author has said as much).
In short, no, there's no way you can be assured of doing all that you need with vbscript.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.
