[wpkg-users] Creating a Folder in the Start Menu together with WPKG installed Program

Rainer Meier r.meier at wpkg.org
Fri May 27 09:17:49 CEST 2011


Hi Mikhail,

On 27.05.2011 03:47, mikhail tan wrote:
> I had successfully did what you taught of me.
> now here is the catch... some of our units have already an older versions of
> OpenOffice
> now I wanted to update this using the methods you taught me, and put something
> like this in the postinstall.cmd
> 
> rd /q /s "%MENUBASE%\%F_DOC%\OpenOffice.org 2.4"
> 
> and for some
> 
> 
> rd /q /s "%MENUBASE%\%F_DOC%\OpenOffice.org 3.0"

Well, when added to the postinstall.cmd script which I have posted then it
should work properly. Maybe you should use:


attrib -s -h -r "%MENUBASE%\%F_DOC%\OpenOffice.org 2.4"
rd /q /s "%MENUBASE%\%F_DOC%\OpenOffice.org 2.4"

attrib -s -h -r "%MENUBASE%\%F_DOC%\OpenOffice.org 3.0"
rd /q /s "%MENUBASE%\%F_DOC%\OpenOffice.org 3.0"



> but the problem is it did not install the package

So what exactly happens? Are the install/upgrade commands not executed?
Maybe you just forgot to increment the revision number within the package
specification:

<?xml version="1.0" encoding="utf-8" ?>
<packages>

<package id='OpenOffice' name='Open Office' revision='321' priority='50'
reboot='false' >
  <!-- Open Office free office suite -->
  <check type='uninstall' condition='exists' path='OpenOffice.org 3.3' />
  <install cmd='msiexec /qn /i "%SOFTWARE%\OOo\openofficeorg33.msi"' />
  <install cmd='"%SOFTWARE%\OOo\postinstall.cmd"' />
  <remove cmd='msiexec /qn /x "%SOFTWARE%\OOo\openofficeorg33.msi"' />
  <remove cmd='"%SOFTWARE%\OOo\postremove.cmd"' />
  <upgrade cmd='msiexec /qn /i "%SOFTWARE%\OOo\openofficeorg33.msi"' />
  <upgrade cmd='"%SOFTWARE%\OOo\postinstall.cmd"' />
</package>

</packages>


Remember that you have to increment the revision attribute to initiate an
upgrade on machines where OpenOffice.org has already been deployed using WPKG.

Check your application event log on Windows when WPKG is executed in order to
see what actions WPKG performs.

If this does not help you, you might post %systemroot%\system32\wpkg.xml (from
the client machine), your profile.xml, packages.xml and hosts.xml file as well
as a full debug log (see config.xml on details on logging) here.

br,
Rainer



More information about the wpkg-users mailing list