<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Hi wpkg-community,<br>
<br>
i´am new to wpkg and struggling with a problem for a few days now,
so i decided to post this question.<br>
<br>
We have a couple of computer pools (~100 PCs). We have deployed a
Windows 7 image (fat image, software<br>
already included, but was not installed with wpkg) to those PCs. Now
we want do deploy multiple updates (.msp-Updates, let´s call<br>
them "Patch1", "Patch2", ...) for one application, let´s call it
"App 1.1" (actually it´s ArcGIS for Desktop 10.2.2).<br>
So "App 1.1" is already installed and since it´s a big installation,
we do not want a reinstallation.<br>
What we want is:<br>
<ol>
<li>Check, if "App 1.1" is installed. If not, don´´t even try to
install "Patch1" and so far to avoid errors (one some computers,
"App 1.2" or "App 1.3" might be installed)<br>
If yes, go to point 2.<br>
</li>
<li>Check, if "Patch1", "Patch2", etc. is already installed for
"App 1.1". If yes, do nothing, else install the patch(es).</li>
</ol>
<p>With wpkg it´s easy to either check point 1 or point 2, but i
don´t know how to check point 1 in combination with point 2. I
already tried some <check>-combinations.<br>
Is it ok, to put all the patches in one package or is it better to
create a package for every patch (i would prefer one big package,
since there are >10 patches)?<br>
</p>
<p>I guess, this only works, when i create separate packages for
each patch:<br>
</p>
<p> <package <br>
id="App 1.1 Patch1" <br>
name="Patch1 for App 1.1" <br>
revision="2"<br>
reboot="false" <br>
priority="1"><br>
<br>
<check type="uninstall" condition="exists" path="Patch
1.1" /><br>
<commands><br>
<command type="install" cmd='msiexec /p
"\\10.10.10.10\deploy$\Patch1.msp" /passive'><br>
<exit code="0" /><br>
<condition><br>
<check type="uninstall"
condition="exists" path="App 1.1" /><br>
</condition><br>
<br>
</command><br>
</commands><br>
</package></p>
<p><br>
Or should i work with package dependencies? E.g. create one
package for App 1.1 with no installation instructions, only the
<check type="uninstall" condition="exists" path="App 1.1" />
condition. The patch packages then depend on this package. But
this might throw errors, if on one computer App 1.1 i s not
installed?<br>
</p>
<p>Thank you,<br>
H. Kröber<br>
</p>
</body>
</html>