This is the best way to capture packages on the Snapshot PC due to how little it “pollutes” (aka its “footprint”) your CleanPC. You will need 3 PCs to build Packages. What follows are applicable to version 4.5 to 4.62 of Wise Package Studio.
This is a regular
workstation or fileserver that will have a Full install of Wise
Package Studio Pro. It will need to be able to share files. Once
setup, there is little need to touch it since you can do everything
by installing the WPSClient.exe on another PC. The PC can also be
used for the Share Point. (
Gotcha:
The STD version of Wise Package Studio (WPS) does not include
WPSclient.exe and therefore cannot be setup in client-server mode.)
Since the “Packaging Server” has a full install of WPS
you could use it to edit existing packages but don’t use it to
capture since you need re-image it between packages.
This is a “CleanPC” that runs the WPS software through a share from the “Packaging server” to capture the actions of a Setup.exe. The actual EXEs are located on the “Packaging Server” and you use the WPS Client on the Snapshot PC to get to them. In fact you will have this item in your start menu:
This PC will need to be re-imaged after each package and therefore will need a D drive formatted in FAT32 to store the images.
This is another “CleanPC” that you can test your packages on. The idea is to keep the original install intact on the Snapshot PC so that if your package fails on the Testing PC you can compare easily, change and compile again on the Snapshot PC while the Testing PC is being re-imaged. Once you are satisfied that your package works on the CleanPC, you can load the corporate image on the Testing PC and test again. As you can see this PC will need to be re-imaged after each package and therefore will need a D drive formatted in FAT32 to store the images.
Install Windows 2000/XP to C:
Create a folder called WPS, share it as “SHAREPOINT” with change permissions and map a drive letter (let’s say W) back to that folder, this will be for the Wise Share Point. (Why? This way you won’t have to re-install the snapshot PC if you need to move the Wise Share Point folder to another machine. Windows 2000/XP doesn’t care is you map to something you are sharing on the same machine. If this is too hard to understand or doesn’t make sense to you then just accept the defaults. (BTW: You can fix this it later.))
Start the installation and enter the serial number(s) as they are needed. Follow the defaults except for the screens below.
|
If you use the default D:\WiseSharePoint
|
If you use a mapped drive letter like W:
|
Note that I changed Wise Share Point to WiseSharePoint. Removing the spaces helps for scripting purposes and other snafus.
At the Clean Machine screen check the box
Gotcha:
Though not well explained, now is the time to check the box and not
when you are installing the WPSClient.exe on the Clean Machine. By
checking this option, WPS will create a bunch of .dat files instead
of creating a real database for the workbench database. If you
don’t do this now, you will NOT be able to use the minimal
installation of Wise Package studio later.
Another
gotcha includes the inability to convert to these .dat files later
without a re-install of the share point and loosing all of the
previous project entries in the workbench database. (NOTE: In WPS
5.0, .dat files are gone )
Minimal Client vs. Full Client:
Minimal Client installs fewer files on the Clean PC than a Full Client install.
The Full Client adds Crystal Report drivers and more. If your target application tries to install such things they will not be part of the resulting package. The Minimal Client does have less functionality but I never use those features.
Continue until completed.
Extract the merge modules to the Wise Share Point. (This is a one time thing)
-Run the MergeModules.MSI off the WPS CD and point it to a sub-directory called MergeModules in the Wise Share Point. You will need your serial number to unlock it. (You may be able to get an updated file from Wise Solutions Technical Support Center as them come out.)
Or
-Copy
the Merge Modules from the WPS CD to a sub-directory called
MergeModules in the Wise Share Point. (Gotcha:
You get fewer merge modules this way)
From the Start Menu, Launch WPS
In the Workbench, select the Edit menu -> Preferences
-Put a check in the box for “Run all tools in Full Screen Mode”
-Click Ok
-Exit WPS
Create the WPSDIR Share
Share C:\Program Files\Wise Package Studio as WPSDIR
NOTE: The Wise Share Point should already be shared as SHAREPOINT in step 2
Edit config.ini in the root of the Wise Share Point. This file is used by the WPSclient.exe to configure some parameters automatically upon install. The following assumes that the computer name of the Packaging server is WPS_SERVER and that you are going to map to the Wise Share Point using a drive letter. You can use UNC paths but that would force you to keep the Wise Share Point on the same computer.
[Share Point]
Version=5.01
[Edition]
PS=10
[Databases.Workbench]
1=workbench
[Workbench.1]
DSN=Workbench Database
Type=ACCESS
Name=workbench
Server=
SqlAuth=0
[DSN]
Workbench Database=Workbench.1
Wise Software Repository=Repository.1
[Databases.Repository]
1=repository
[Repository.1]
DSN=Wise Software Repository
Type=ACCESS
Name=repository
Server=
SqlAuth=0
Create a batch file called WPSclient_install.BAT in the root of the Wise Share Point.
::REM The following is suppose to be one line
\\WPSSERVER\WPSDIR\wpsclient.exe SERIALNUM="0123456789" PREVSERIAL="0123456789" SHAREPOINT="W:\WiseSharePoint" WPSDIR="\\WPSSERVER\WPSDIR\" MODULESPATH="W:\WiseSharePoint\Merge Modules" NOCRYSTAL=1 /Qb
::Disable update check, etc.
regedit /s WPS_Custom_settings.reg
Not all desired settings are automated. So we improvise. Create a file called WPS_Custom_settings.reg in the root of the Wise Share Point.
Windows Registry Editor Version 5.00
;stop nagging to check for updates on every launch
[HKEY_CURRENT_USER\Software\Wise Solutions\Workbench\Settings]
"UpgradeRemind"=dword:00000000
;Make all tools fullscreen upon launch
"Fullscreen"=dword:00000001
