|
| | | Supreme Being
Group: Advanced Members
Last Login: 1/21/2004 10:48:00 AM
Posts: 154, Visits: 1 |
| Hello Support,
I know the possibility to set some requirements in a package.(size harddisk, type OS) But, is it also possible to set a variable requirement. For example, you like to distribute a package with a upgrade for a specified videocard brand XXX. It would be nice to distribute this package to everybody, and the package will only be installed on the pc's with this specified videocard. Maybe there is a possibility to look for a registry-key on the client-pc before installing. (a specific key that only the client has with videocard XXX) Is this possible in the standard way, or do you have to make a script? And how? With regards,
Sup
|
| |
| | | Supreme Being
Group: Advanced Members
Last Login: 1/21/2004 10:48:00 AM
Posts: 154, Visits: 1 |
| | I suggest that you start from an clean Pc, take a snapshot and install the videocard(the old one or old driver) take the after snapshot and there you have all regkeys etc. Pic one that you think might fit and do the first step again but now with the new driver or card. Add the key you picked as a variable (more of that in the manual) and be sure to set "Path must exist" Perhaps you might check the rules.ini fiel before snapshot depending on what videocard you are using.
|
| |
| | | 
Supreme Being
Group: Moderators
Last Login: 9/3/2008 9:40:39 PM
Posts: 654, Visits: 800 |
| | With Prism Deploy version 4.x the only pre-installation requirements that may be set inside of a Package are the Minimum KB Free per Drive and the target machine's Operating System. Using variables and scripts, Prism allows much greater flexibilty. A new Tech Notes has been posted that goes through an example of installing a Package depending the existance of a registry value. http://www.newboundary.com/support/docs/Tips_and_Tricks/regkey_exist_tip.htm
New Boundary Technologies Support
support@newboundary.com |
| |
| | |
Supreme Being
Group: Moderators
Last Login: 9/3/2008 9:40:39 PM
Posts: 654, Visits: 800 |
| | The ability to set requirements on a package has been vastly improved in versions 5.0 and 5.1 of Prism Deploy and Prism Pack. In addition, the interface for setting OS version and required disk space has been totally redesigned and expanded. To try the new Installation Rules feature, download the latest version of Prism Deploy or Prism Pack from http://www.newboundary.com. Once it is installed, open a package in the Prism Editor, choose "Properties", then click on the new "Requirements" tab. This is where you can specify the existence of a registry key or registry value, along with many other options. Please contact support@newboundary.com if you'd like any assistance or ideas for using the new features.
New Boundary Technologies Support
support@newboundary.com |
| |
|
|