Wise Package Studio, Part 4: Start Guide for the Virtual Package Editor
In the previous article we saw how to use the Windows Installer Package Editor. That is only one of the cool tools in Wise Package Studio. But there is another cool tool that can really help you building better professional packages for Altiris SVS.
The SVS administration console is a cool tool to build VSA packages that can be exported to other clients and then can be used. For home packages and lots of professional it is more then enough. But if you need to do tasks that will be started when you do a specific action the Virtual Package Editor is your tool.
Using the Virtual Package Editor will help you to create the best scripts inside your VSA. When an Application needs a reboot during capturing this is the only correct way to do this.
In one of my previous articles I guided you through the packaging of Daemon Tools that needed a restart. But then you have to be aware what happens, and you have to follow the right steps. When you use the Virtual Package Editor the process is much simpler and it will get you a good and complete package.
In this fourth article I'm going to guide you through one of the best additions in Wise Package Studio 7, the Virtual Package Editor.
With this Virtual Package Editor we can build the best and the most difficult VSA's simply and easily.
Start the Wise Virtual Package Editor by double clicking on it. Unlike the Windows Installer Editor that uses the information from the currently built MSI, we have to build the package first.
So when the Virtual Package Editor starts, it shows you a screen asking what you would like to do.
We are going to build a Set-up-Capture, so that is what we select. As the output type you already can select Create Virtual layer. But we are building a WVP (Wise Virtual Package) first so we select that option. Click OK to continue.
We are going to do a Single Program Capture. Click Next to continue.
Now we have to select the executable that we need to get virtualised. Click Next to continue.
The installation starts. Select the language you need and click next to continue. Again this language is only the language that helps you through the set-up process. It is not the language that you will have when the package is ready. The language you have when the package is ready is selected during the installation process.
Click Next to confirm the welcome screen.
Click Next to agree with the License agreement.
I associate Abiword with the .doc extension. Also I'm going to select the additional dictionaries that I need in my package for the users.
Then I give up the installation path where I would like the files to be in the program files. Click Next to continue.
Do the same for the shortcuts, and select Next to continue.
Now I select the download mirror for the extra dictionaries, and then I click Install.
When you have selected a download mirror that is not available at the time, you can simply select a different one during the process. That will not disable your package.
Click next when the installation is ready. De-select the option to start Abiword when the installation is finished, and then Click Finish to end the installation of your package.
Now we have to clean up some parts that we do not need in our package. In this case we select the files named index.dat and we click on exclude.
We also remove uninstall. Bat.
Click Next to go to the next screen.
Now you see everything I excluded from the package. Click Next to continue. When you select registry in the Exclusion Type field you see the entire registry keys that are excluded.
I created a new folder in the Wise repository named Virtual Packages.
Click Next to finish.
In the files tab we see all the files. To make it easier we select: Hide Empty folders. Now you only see the folders that contain files.
Do the same in the registry tab.
Now you can edit, remove or add files or folders into your project.
When you have finished the steps, click on the events button in the left.
Now we are able to build the On-events. In this example we build a Pre Activate. Click on Add in the right, and select Wise Script.
Now we select Check Configuration.
When you double clicked on the Check Configuration you can let the software check for specific things.
In the example above we select: If system doesn't have Windows XP running, Abort Installation.
Then we can give a popup with a title and a customized message text explaining to the user why the package does not work.
Now When you click OK, the On-event is added to the package.
In the example the Virtual Software Archive will only run when it is imported on a Windows XP machine.
There are 97 preconfigured Wise scripts available that will help you doing specific tasks.
Using and evaluating these Wise script lines will help you do the best things in your layers.
Now that we have built our On-events, we have to build the VSA. Selecting the "Compile" button in the bottom right in the screen should do that.
Select the location where you would like to place the VSA, and give the VSA a name.
Now when you go to the location where you located the software, you see that there are two files built. The first one is the VSA that can be used on all the computers. The second is the WVP file that can be used in the Virtual Package editor to add files or to build new On-events.
As you see, there are very cool solutions available in the On-event when you use Wise script.
You can check if there is another layer on the system that is needed to let your layer work perfectly.
When the software has a dependency, for instance a specific Dot Net version or a Java version, then you can use the On-event to import and activate the layer every time when this layer is used.
This will help you greatly in doing your job as a system administrator or packager.
In one of the following articles I will build an VSA that has a MSI inside.
The layer will start an installation that installs a specific MSI that installs the driver for some hardware that is needed. The MSI will get installed when you start Import the VSA. The MSI will be uninstalled when we delete the VSA.
By using the Software Conflict Manager we can make sure that the driver does not affect other software on the computers in your network.