Video Screencast Help

Wise Package Studio, Part 1: Installing and Configuring Wise Package Studio 7

Created: 12 Dec 2008 • Updated: 21 May 2009 | 6 comments
Language Translations
erikw's picture
+9 9 Votes
Login to vote

In my own network I need Wise Package Studio installed to build custom MSI's, but I also want to use the Wise Virtual Package Editor to customize my VSA's. With the normal SVS admin we are able to build cool packages, but for the real stuff it is better to use Wise Package Studio.

In this series of articles I will explain the first use of Wise Package Studio for newbies.

This first article will help you installing Wise Package Studio, and will help you configuring it before you start using it. Take your time. It will take up to 3 hours before everything is configured and ready to go.

Get Prepared

To use Wise Package Studio, you need some prerequisites.

First of all we need a Windows 2003 server to install it on. In my network the SQL server is on a different server because all my SQL databases are on one server. The Wise Package Studio share needs lots of space. So make sure your hard disk is large enough. Also make sure your C partition where the OS and the installation are going will be is big enough. You need at least 15 to 20 GB to get you through to whole process. You also need to be sure you have the SQL server running. The SQL server can be every version of SQL.

The installation consists of a server installation and eventually you also can install it on a Windows XP client as a client packaging machine. The actual packaging will then be done on the Windows XP client, but all the files will reside on the server. It will prevent you form using more database servers.

First of all you need the software to install Wise Package Studio, and you need a license. If you do not have a license, you can install it with a 7 day's trial license.

The whole installation and configuration takes several steps to get completed.

Step 1: Install Wise Package Studio 7

Browse to the folder were you have stored the Wise installation.

Double click on the setup to start it.

Now the welcome screen appears. Click Next to continue.

Accept the license agreement and click Next to continue. When you do not accept the license file, you are not able to continue.

Now you have to add your license numbers. Depending on the license you have bought the functionality will be installed. If you have no number you can select the 7 Day Evaluation version. That will give you all the options.

Click Next to continue.

First of all we have to install the server. Select the server option, and click Next to continue.

Select the path where you want to install the files and click Next to continue.

Enter the administrator password. This password is needed to get the correct privileges for the service. Click Next to continue.

Then click Next to start the installation. The installation will take a while, so be patient, and do the same as I always do. Grab a cup of coffee.

Step 2: Configuring the Share Point and the database.

Our next step is to configure the Wise Share Point and the database. Before proceeding with this step you have to be sure that you have enough disk space and that you have a SQL server or q SQL eXpress server installed and configured.

Go to start, Programs, Altiris, Wise Package Studio and start the Wise Repository manager.

Select the path where you would like to install the Share Point Directory. I place it on my file server in the directory Wise. This share is available to all my server and my clients when I'm logged in as an administrator. Click next to continue.

Select a name for the Workbench Database and select the server where you like to install it.

Click Next to continue.

Give in the credentials for the SQL server and click Next to continue. In my case I always use the SA password. That makes things easier for me. Click Next to continue.

Repeat the steps again for the two other databases. Now when you click Next, the databases and the Share Point will be installed and configured.

When everything is finished, click Finish.

Step 3: Start Wise Package Studio for first use

Now everything is installed and configured, we have to prepare it for first use. Go to start, Programs, Altiris, Wise Package Studio and start Wise Package Studio.

Give in the admin password if needed, and click OK.

Before starting to use the Wise Package Studio we have to configure it further. This is our first and very important process. In the Active Project you see that the default Initial Workbench Setup is selected.

I installed the Professional version. The first steps are not activated.

My first step is to run the Define SetupCapture standards. Click on run to start.

Click on Next to start the process.

Select the options you want. I already added the options I need.

Click Next to continue.

Default the C:\ directory is already added. If you wish to use D also you can add it here.

Click Next to continue.

Select the option Automatically build exclusion list. This is the recommended option, and it is also a very good option. By selecting this it will save you a lot of extra work.

Click Next to continue and then again Next.

Do not click Next now. First of all we have to perform two steps to get the process completed correctly. First start Notepad, and close it again. Then restart your server. Be sure NOT to select the option install updates and shut down. This will build a wrong list.

When the server is rebooted, you will automatically get back to the previous screen.

Select next to continue and then again Next to run the initial scan.

This may take several minutes.

When the list is built, you get the screen above. You may add additional directories or files if you want. Browse through the list and you will see some files that have a yellow question mark in front of them. You may also add these to the exclusion list by double clicking on them and select exclude subdirectories.

Click Next when you are sure the list is complete.

Do the same for the screen with the registry keys, and also for the list with the ini files.

When you use Wise Package Studio to build MSI's, the software will get installed on the server or on the client. If you do not want this, then you can use the VirtualOS option. When you select this, the software will get installed in a virtualOS. After finishing the capturing of software packages, there will no residu stay on the server. This ensures our server to stay clean.

NOTE: Copy the file C:\Program Files\Altiris\Wise Package Studio\Workbench\VirtualOS.exe to the Wise Share if you also want to use this on your clients.

Click Next to start and then Finish.

Now go to the executable VirtualOS, and start it.

Give the OS a unique name and select the Share Point to store it so it is available for the other clients also that are used for packaging.

Click Next to continue.

The process of building the virtual OS takes a while, so be patient or grab another cup of coffee.

Click Finish when the Virtual OS is built.

Now we are going to configure the Standard Operating Environment. Click on Run to start the process.

Click Next to continue and then Next to start the scanning process.

When the process is finished, you can manually alter the files, registry keys, Ini files and Shortcuts. But it is not really necessary. Click next to continue and then Finish.

Now the Standard Operating Environment (SOE) will be builded. When the process is ready, click on Finish.

You may skip the other options.

Our Wise Package Studio Installation is now ready to run.

For testing purposes if everything works fine you can now go to the sample project. This will help you through the basics of Wise Package studio.

In the next article I'm going to guide you through the process of building your first custom MSI.

Even when this article and others help you through the process, it is very wise to get the 4 day Wise Package Studio training. That will explain in depth how the process works and goes much deeper then my articles will go. The biggest benefit of the course is that it enables you to get an answer on questions that you have while working with the software. I will not be able to answer all questions.

On the Symantec website you can always find a training center in your neighbourhood that can support you in getting the training and become the best Wise packager in the world.

Wise Package Studio for Beginners - Index of Articles

Wise Package Studio, Part 2: Building Your First Package
 

Article Filed Under:

Comments 6 CommentsJump to latest comment

bhillebrand@fhlbi.com's picture

Thanks for the info Eric. It is timely for us as we just purchased WPS7. My question is: Can we install the server components of WPS 7 on our existing NS or DS?

0
Login to vote
erikw's picture

Yes, you could install the server componentsn on the same bow were your NS an/or DS resides, but it will not integrate into the console anyway.
The reason to do this is to get a straigt forward functionality to get the deployment section see the NS, and create a job to get it in the DS.
On the other hand then you still have to do some manual work to get the job working because it will not create the script for you.

Regards
Erik
www.DinamiQs.com

Regards Erik www.DinamiQs.com Dinamiqs is the home of VirtualStorm (www.virtualstorm.org)

*************************************************************
If your issue has been solved, Please mark it as solved
***********

0
Login to vote
dvdzonenz's picture

virtual os doesn't support virtual os files greater than 2 gb. please use this utility on a clean machine.

My Os was Win 2003 Enterprise with SP2.

0
Login to vote
philbenson's picture

with the virtual OS?
There are so many virtualisation applications out there there is no real need.
Cheers
Phil

0
Login to vote
heyvoon's picture

It took me a little bit to figure it out specially because there is no info about this msg. It you google for it you gonna end up inthis post and that's it. lol

If you read the msg over a couple of times you can figure out that it translates to... "The machine you're running the VirtualOS.exe has a lot of stuff installed and thus VirtualOS cannot create a VirtualOS from it. It definately is going to be over 2gb (the max limit)."

Solution: Get a clean install of Windows 2003 and run the VirtualOS in it and it will create the VirtualOS based on that clean install and ithe file will be less then 2gb.

I hope I have helped anybody with this problem.

0
Login to vote
Watcher's picture

Thanks for the good and very clear information.

0
Login to vote