Creating installers that include Symantec Workspace Virtualization Agent

I read through this mammoth post a few times but my brain has fried and I've not been able to upload my remaining brain cell with the actual problem areas.

So first of all, lets break this down into easy steps.
It looks like you wish to target Win2000 and WinXP targets.
Ignoring the virtualised apps for the moment, are you able to successfully install the virtualisation client on all your test machines?
That has to be the starting point in any further investigations, so lets get that aspect sorted first.

Can you check what version of Windows Installer your Windows 2000 machines are running?
I'm speculating as to whether the Virtual Package Editor setup is updating the version of Windows Installer before installing the virtualisation agent on W2K

Is there any mention in the release documentation for SWV 6.1 SP1 whether a minimum service pack level is required for Win2K, or even whether Win2K is supported at all. (Sorry I've not had time to research this for myself).

The loadlibrary error is a tricky one to solve - if you have worked with Procmon from Sysinternals (now Microsoft), it would be interesting to monitor whether the install process is failing due to a call to a DLL that is either failing or is too old a version to have the required entry points.

As you are in an eval situation, I would suggest giving the Symantec pre-sales support a call, as perhaps with the aid of the full install log, they may be able to advise you further.

When you are working with the Symantec Workspace Virtualisation client specifically, and not involving Wise Installation Studio, there is also a specific support forum which deals with SWV. Posting SWV-specific questions there will open your issues up to a larger audience with more direct experience of solving problems with the SWV client.

Installation of SWV works now on Windows 2000. Virtual Package Editor is still completely useless, though. I'm unable to create any kind of setup that creates registry entries and that includes the Workspace Virtualization Agent in runtime mode. I tried using SetupCapture with an msi installer created with Windows Installer Editor, opening (and converting to VRA) a VSA file created in Workspace Virtualization Admin and manually adding files and registry entries to a fresh WVP. I get the same result for all of them; registry entries just are not there. Programs running from the layer can't open the keys.

I'm starting to wonder whether anyone has ever used Virtual Package Editor to create a setup.exe that includes SWV Agent. The machine I'm using Virtual Package Editor on also has SWV (with admin) installed and does not have an internet connection. Apart from that it's a completely standard fresh install of Windows XP SP3 (german).

Let's try and break this down into smaller chunks.
If you create a virtual application with registry keys included, and deploy it to your German XP SP3 build with the SWV agent already installed - does it work correctly, and are the registry settings correctly installed?

Also, have you tried installing your setup which includes the SWV agent to an XP workstation running an ENGLISH version of XP SP3 ??
My reason for asking this is that over the years I have seen many different issues with operating systems that seem particularly to occur on German versions of windows. Don't know why this happens - perhaps Microsoft don't test non English builds to the same extent as the US build.
So at least testing on an English version of XP will establish whether the issue is generic or specific to a particular version of XP.

If I create a virtual application with SWV it works. If I create one with Virtual Package Editor it does not. If I take the working VSA and open it in Virtual Package Editor, the conversion to VRA seems to loose the registry entries. It won't work if I add them manually back in either.

I haven't tried using an English XP version. I'll do that later today and post the results.

Yes, I installed Wise *Installation* Studio and I just confirmed in Virtual Package Editor, Help -> About that I'm running build 7.3.0.250.

The SWV Version I installed is 6.1 SP1. SWV was installed before Wise Installation Studio. So maybe the latter overwrote the SWV agent version that is actually used? How can I check which SWV agent version is being used? Opening Help -> About in Symantec Workspace Virtualization Admin gives me version 6.1.5104 for application, library and driver. The version number in the metadata of the file C:\windows\system32\fsllib32.dll is 6.1.5104.0 as well.

I also tried uninstalling SWV after installing Wise Installation Studio to test whether that would work, but that resulted in a BSOD, so I restored the virtual machine. I can try installing only Wise Installation Studio on an English Windows XP SP3 VM later when I'm at home.

 Thanks for the idea; On a fresh English XP VM with only Wise Installation Studio installed everything works fine. I tried both installing the setup with Installation Studio installed and restoring the VM and then installing the setup. What I didn't try yet is to install SWV as well, either before or after installing Installation Studio. I'll try that tomorrow. Again, thanks a lot for your help.

It would be interesting to know how things work when you install SWV after a clean install of WIS7. If things again stop working as expected, I would recommend adding this to your thread in the SWV forum so that it gets visibility with the SVS guys also.

I've posted a new thread describing my results so far.
www.symantec.com/connect/forums/interaction-between-swv-and-wise-installation-studio

With Wise Package Studio 8 just being released, I have asked the question as to whether SWV 6.1 SP1 support was included in WPS8 before it shipped. Otherwise it is likely that WPS8 will not be compatible with SWV 6.1 SP1 in the same way as WIS 7 SP1, thanks to your research.