Zenworks 6.5 SP2, Netware Client 4.91 SP2 on a Windows XP SP2 workstation
(Dell Latitude laptop)

[rant]One of my complaints about Novell documentation is the assumptions.
It's like they assume you've got intimate knowledge of the product and will
be able to figure out what's missing or implied if they don't mention it
explicitly. Case in point: putting an add-on image on a workstation image.
The manual basically states you use your existing application object, go to
the common->imaging tab, specify where to save it and how to push it (force
run, start menu, etc.) and click create image. You then add that into the
eDirectory base image object as an add-on image and it just works.[/rant]

I'm testing Zenworks imaging with one base workstation image and two add-on
apps. The base image is Windows XP, the laptop specific drivers, Netware
client, and Zenworks agent. The apps are Groupwise 7 SP1 client and
Symantec Antivirus 10.1 client. As it appears that many of the tabs on the
Application's eDirectory object affect this distribution I will highlight
what I've modified on each object.


Groupwise 7 SP1 (using an exe)
Identification->Icon: disconnectable and show progress
Distribution options->Options: version #1, reboot if needed, prompt for
reboot
Run options->Application: path to file: m:\groupwise\win32\setup.exe with a
/u parameter and a force run as user if application is workstation
associated
Associations: app launcher for the users' OU
Common->Imaging: app size: 10.23 kb, m:\images\groupwise7.zmg, image
association location: start menu, desktop, force cache


Symantec Antivirus 10.1 (using an msi)
Identification->Package Information: path: m:\symantec antivirus 10
Identification->Icon: disconnectable, wait on force run, determine force run
order (set to #50) and show progress
Distribution options->Options: version #4, reboot if needed, prompt for
reboot
Run options: install only, run application once, force run as user if
application is workstation associated
Associations: app launcher for the users' OU
Common->Imaging: app size: 32 MB, location:
m:\images\SymantecAntivirus10.zmg, image association location: force run
Common->Sources: m:\symantec antivirus 10
MSI->Transforms: m:\symantec antivirus 10\sav.mst


Some Dell computers have a small diagnostic partition on them. Thanks to
another newsgroup post I found that I needed to do a scripted installation
and specify the add-on images to go to partition 2. My script looks like
this:

img restorep [server name] //[server]/images/dell.zmg
img restorep [server name] //[server]/images/SymantecAntivirus10.zmg a1:p2
img restorep [server name] //[server]/images/groupwise7.zmg a1:p2


I know that, since this is using Linux, it is case sensitive and I need to
use forward slashes.

When I run a Zenworks imaging program the files get pushed out to the
laptop. When imaging is complete and it automatically reboots I can put in
Knoppix and verify that the Symantec Antivirus installation files have been
copied down to c:\nalcache. The computer will run through Windows Sysprep
mini setup, reboot, zenworks will rename the computer and reboot. When I
get to the Netware login box I can login to eDirectory and nothing will
happen. The apps will not be forcefully installed, they won't appear in the
Start Menu, nothing. I read on some previous posts that you needed to login
as an administrator to the local workstation and not eDirectory. I tried
that and ran naldesk.exe. This tried to install the applications but SAV
got an MSI error (#1612) and Groupwise errored as it was looking for a
network drive.

I also learned from another post that if you want "force run" to work for an
add-on image you need to make sure the app is set to be disconnectable,
which it is.


My questions are:

1. What am I missing on the MSI installation? It copied down the setup
files so why didn't it install?

2. What am I missing with the EXE installation? Why didn't it bundle all
the setup files together into one zmg file and instead just took the exe
file? Do I need to create different application objects from the ones I
use normally? Do I need to list a path on the local hard drive, such as
c:\nalcahe instead of one on the network?

3. That forum post I found about logging in to the workstation only, and
avoiding eDirectory, was from a couple of years ago. Is that still a
requirement? If so, where does it say that in the manual? And how would
that be practical if you're reimaging a user's computer out in the office?
They'd need to know a Windows administrator account in order to get their
programs.


I'm sorry for this post being so long. I've been working on this for a
couple of days and have been getting more and more frustrated. I've
searched the forums via Google Groups and others have had problems with this
but no definitive answer could be found.


Matthew