Brian Reese | 1 Dec 16:02 2008

Problem with consecutive package deployment (ProEngineer)

Hey all, 

I have an issue when installing 3 packages. I have install packages for ProEngineer WildFire 2, 3, and 4. On
all the Mechanical Engineer seats, I need to have each of these packages be installed. ProE provides their
own way of doing a silent install, by recording a trail file then calling it for the silent install. First, I
was wondering if anyone has made a package for these Apps already or has any experience with PTC and their
trailfiles. 

The real Issue is that these 3 installers do not wait for the first one to finish before starting the next one.
Once all the gui options have been chosen and the installation progress bar initializes (the trail file
finishes), the next ProE installation begins. I want them to wait until the installation is complete,
otherwise there are 3 concurrent installations and it slows the system and hence the overall length of the
install. Thanks guys, below are my package entries:

<package
   id="proengineer2"
   name="Pro/ENGINEER Wildfire 2.0"
   revision="2.0"
   reboot="false"
   priority="100">

   <check type="uninstall" condition="exists" path="Pro/ENGINEER Release Wildfire 2.0 Datecode M280" />
   <install cmd='%Software%\ProE\WildFire2\Disk1of3\setup.exe -uitrail
"%Software%\ProE\WildFire2\Disk1of3\WF2TrailFile.txt"' />
</package>

<package
   id="proengineer3"
   name="Pro/ENGINEER Wildfire 3.0"
   revision="3.0"
(Continue reading)

Paul McGrath | 1 Dec 16:06 2008
Picon

Re: Problem with consecutive package deployment(ProEngineer)

Brian,
  I would suggest doing <depends> for the second and third.  This would
mean that version 4 won't install unless 3 exists, and 3 won't install
unless 2 exists.

<package
   id="proengineer3"
   name="Pro/ENGINEER Wildfire 2.0"
   revision="2.0"
   reboot="false"
   priority="100">
   <depends package-id="proengineer2" /> 

<package
   id="proengineer4"
   name="Pro/ENGINEER Wildfire 2.0"
   revision="2.0"
   reboot="false"
   priority="100">
   <depends package-id="proengineer3" /> 

Test that out.
Paul

-----Original Message-----
From: wpkg-users-bounces <at> lists.wpkg.org
[mailto:wpkg-users-bounces <at> lists.wpkg.org] On Behalf Of Brian Reese
Sent: 01 December 2008 15:02
To: wpkg-users <at> lists.wpkg.org
Subject: [wpkg-users] Problem with consecutive package
(Continue reading)

Brian Reese | 1 Dec 17:21 2008

Re: Problem with consecutive package deployment(ProEngineer)

Hey Paul,
I tried doing that, But it didn't work well. It did what was intended, it only spawned installing
proengineer2, but for some reason the install hung halfway through and then wpkg.js quit. The install of 2
was incomplete and it never even started 3 or 4. Is there a timeout value that is set? Like after 5 minutes it
quits, no matter what the status? I remember something like this in a previous version under "advanced"
but i dont see the option now. I'm using version 1.3.6

----- "Paul McGrath" <J.P.McGrath <at> leeds.ac.uk> wrote:

> Brian,
>   I would suggest doing <depends> for the second and third.  This
> would
> mean that version 4 won't install unless 3 exists, and 3 won't
> install
> unless 2 exists.
> 
> <package
>    id="proengineer3"
>    name="Pro/ENGINEER Wildfire 2.0"
>    revision="2.0"
>    reboot="false"
>    priority="100">
>    <depends package-id="proengineer2" /> 
> 
> 
> <package
>    id="proengineer4"
>    name="Pro/ENGINEER Wildfire 2.0"
>    revision="2.0"
>    reboot="false"
(Continue reading)

Jens Geile | 1 Dec 17:58 2008
Picon

Re: Problems with WPKG after settings update

Hi,

> WPKG Client version is 1.2.1. (I'd prefer using the 1.3.x branch but people are kinda picky about beta
state software -.- ... I'll try this with 1.3.6. now and report back once the installation is done.)
Ok, I'm a little late with reporting back but better late than never. ;)
So I tested 1.3.6. and loked for the same error to occure and you know what? It appeared! And what's worse, it
even appears to be worse than with 1.2.1. One client didn't want to sync at all at start-up (tried it 5 or 6
times) but after starting the sync manually once it also worked on start-up again... This thing is driving
me nuts.

For completeness' sake here is my settings.xml ... i have one straw left to test, let's see how this works out tomorrow.

<?xml version="1.0" encoding="utf-8"?>
<configuration>
  <file>\\server\install\wpkg\wpkg.js</file>
  <path-user>LAN2\server-user</path-user>
  <path-password>supersecretpassword</path-password>
  <exec-user>SYSTEM</exec-user>
  <exec-password></exec-password>
  <parameters>/synchronize</parameters>
  <silent>YES</silent>
  <pre-action>\\server\install\wpkg\test.bat</pre-action>
  <post-action></post-action>
  <show-GUI>NO</show-GUI>
  <logon-delay>2</logon-delay>
  <logon-message-1>Software wird installiert</logon-message-1>
  <logon-message-2>Bitte warten...</logon-message-2>
  <script-variable name="SOFTWARE">\\server\install\software</script-variable>
  <script-variable name="SOFTWARE_ISERV">\\server\install\software\packaged</script-variable>
  <script-variable name="SOFTWARE_CUSTOM">\\server\install\software\custom</script-variable>
(Continue reading)

Greg Kavanagh | 1 Dec 18:06 2008

How to Deploy WPKG client with group policy??

Hi,

My first strategy was to deploy the WPKG client with group policy and
then upadte the settings afterwards using Windows 2008 server onto
Vista clients.

"%PROGRAMFILES%\WPKG\wpkginst.exe
--SETTINGSFILE=f:\wpkg\images\setup\settings.xml"

but the initial installation fails with:

"Software Installation encountered an unexpected error while reading
from the MSI file \\CCSERVER\Install\WPKG\WPKG Client 1.2.1.msi.  The
error was not serious enough to justify halting the operation.  The
following error was encountered: The operation completed
successfully."

I have checked the 'ignore language when deploying this package"

My next strategy was to create a .bat file than ran the line

"msiexec /qb /i WPKGSetup.msi
SETTINGSFILE=\\server\deploy\settings\settings.xml ALLUSERS=1"

this runs fine when logged on and I double click on the .bat file but
when I run in at logon with group policy it fails saying the msi is
not valid.

Has anyone got a solution? It'd be much appreciated.

(Continue reading)

David Davies | 2 Dec 14:40 2008

Re: Problem with consecutive package deployment (ProEngineer)

Wow, I thought I was the only one who needs to install three separate versions of Pro/ENGINEER on systems, and Im surprised that there are others doing it with WPKG, let alone down the road in Waltham (Im in Concord).

PTCs installation technology is awful from a sysadmin perspective. Note that youll probably need to tweak your installation trail file in odd ways to deal with locations of different installationdisks (who installs from CDs any more?) and/or different installation drive letters on your systems.

I have WPKG execute a batch file to install Pro/E, and this gives me more flexibility. To address your specific problem with the Pro/E installers handing control back to early, I simply have my batch file wait a safe amount of time (30 minutes) after the installer is started. I know that the installation should take less than that amount of time, so Im safe. My batch file for Pro/ENGINEER Wildfire 2.0 is:

set WFVER=2

set RELCODE=M280

set FREESPACE=4GB

::First, see if there is enough free space to copy the data locally and then install the application.

"%WPKGROOT%\tools\freedisk.exe" /D %SystemDrive% %FREESPACE% > NUL

if errorlevel 1 goto :END

::Proceed with the installation if there is enough space

if %PROCESSOR_ARCHITECTURE%==x86   set ARCH=32

if %PROCESSOR_ARCHITECTURE%==AMD64 set ARCH=64

if %SYSTEMDRIVE%==C: set DR=c

if %SYSTEMDRIVE%==D: set DR=d

::The below parameters make robocopy produce no console output. WPKG does not deal with robocopy's console output well.

set ROBOCOPYFLAGS=/NP /NS /NC /NFL /NDL /NJH /NJS /Z

::Delete the preferences file to avoid extra prompts that message up the silent installer.

if exist "%PROGRAMFILES%\PTC\proeWildfire %WFVER%.0\bin\proe1.psf" del "%PROGRAMFILES%\PTC\proeWildfire %WFVER%.0\bin\proe1.psf"

::Copy over data for installation

"%WPKGROOT%\tools\robocopy.exe" /MIR %ROBOCOPYFLAGS% ""%SOFTWARE%\PTC\ProENGINEER\Wildfire%WFVER%\win%ARCH%\%RELCODE%" "%WINDIR%\temp\%RELCODE%"

copy /Y "%SOFTWARE%\PTC\ProENGINEER\WF%WFVER%\installtrail%RELCODE%%DR%.txt" "%WINDIR%\TEMP\%RELCODE%\."

::Install the application

%WINDIR%\temp\%RELCODE%\setup.exe -nographics -uitrail %WINDIR%\TEMP\%RELCODE%\installtrail%RELCODE%%DR%.txt

::Wait 30 minutes for the installation to complete.

"%WPKGROOT%\tools\sleep.exe" 1800

rd /S /Q "%WINDIR%\temp\%RELCODE%"

:END

Note that this relies on sleep.exe and freedisk.exe, which are part of the Windows Server 2003 Resource Kit Tools. These are located in %WPKGROOT%\tools.

This batch file includes some other interesting features:

1.      The variables in the first three lines set parameters that I can change in order to use this script with other versions of Pro/E. Now that I think about it, I could specify that stuff in the command line instead, and then I would not need separate installation batch files for each Pro/E version.

2.      This installs a 32-bit version of Pro/E if the OS is 32-bit, and a 64-bit version if the OS is 32-bit.

3.      It will install on the C or D drive, whichever is the boot volume.

4.      I copy all the installation files to the local system and then run the installer locally.

5.      A Pro/E upgrades screens are different from a fresh installations screens, so the same trail file does not work for both. To deal with this, I make sure that Pro/E is always doing a fresh installation by deleting an active proe1.psf file.

My actual WPKG installation command is a one-liner where I ignore the exit code:

<install cmd='%SOFTWARE%\PTC\ProENGINEER\WF2\install-silent.bat'>

        <exit code="any" />

</install>

-------------------------------------------------------------------------
wpkg-users mailing list archives >> http://lists.wpkg.org/pipermail/wpkg-users/
_______________________________________________
wpkg-users mailing list
wpkg-users <at> lists.wpkg.org
http://lists.wpkg.org/mailman/listinfo/wpkg-users
Rainer Meier | 2 Dec 17:41 2008

Re: Problem with consecutive package deployment (ProEngineer)

Hi David

David Davies wrote:
> I have WPKG execute a batch file to install Pro/E, and this gives me
> more flexibility. To address your specific problem with the Pro/E
> installers handing control back to early, I simply have my batch file
> wait a safe amount of time (30 minutes) after the installer is started.
> I know that the installation should take less than that amount of time,
> so I’m safe. My batch file for Pro/ENGINEER Wildfire 2.0 is:
[snip]

Yes, looks like a good job you've done. Thanks for sharing this. Let me
suggest that you insert this information to the wiki at wpkg.org in
order to be available at our fingertips when somebody needs to install
this software.

In addition you might consider not to tell WPKG that "any" return code
is just fine. Instead you should probably insert some checks
(file/directory exists after waiting time or similar) and exit with a
specific error code. Or just exit with code 0 any time and capture just
this result. So in case execution of cmd script unexpectedly fails in a
terrible way it will probably exit with a different code. So you at
least gain the advantage to know if the script terminated properly.

WPKG checks can be made very specific to check if the software is
actually installed correclty (verify uninstall, key file versions and/or
registry values).

br,
Rainer
-------------------------------------------------------------------------
wpkg-users mailing list archives >> http://lists.wpkg.org/pipermail/wpkg-users/
_______________________________________________
wpkg-users mailing list
wpkg-users <at> lists.wpkg.org
http://lists.wpkg.org/mailman/listinfo/wpkg-users
Brian May | 3 Dec 03:57 2008

Re: Silently drop a package

Andreas Heinlein wrote:
> I had deployed Adobe Reader 8.1.2 as package, and since I was still
> quite new to WPKG, I later deployed Adobe Reader 8.1.2 SU1 as a separate
> package (depending on Adobe Reader 8.1.2), which was obviously not the
> best choice. Now I deployed Adobe Reader 9, which automatically
> uninstalls 8.1.2 and the SU1. I increased revision number of the Adobe
> Reader package and updated the checks and commands, which worked just
> fine. But what now with the SU1 package?

As was previously explained to me it is better not to append the package 
version into the package id. So you only have one package definition for 
Adobe Reader. This means upgrades will work properly.

Some of the examples on the wiki don't comply with this, unfortunately.

Brian May

-------------------------------------------------------------------------
wpkg-users mailing list archives >> http://lists.wpkg.org/pipermail/wpkg-users/
Brian May | 3 Dec 04:02 2008

Re: WPKG Agent Blocks Shutdown

Leon Hedding (ICT) wrote:
> I am running into issues where a package install/upgrade command fails 
> to complete. It hangs on an setup.exe process indefinitely.

I would hazard a guess this is because the setup.exe is waiting for user 
input, and you have the show GUI option turned off so it is hidden.

I have seen at least several setup programs which will throw up an error 
dialog box if anything goes wrong, despite the non-interactive 
parameters being set.

Brian May

-------------------------------------------------------------------------
wpkg-users mailing list archives >> http://lists.wpkg.org/pipermail/wpkg-users/
Brian May | 4 Dec 03:48 2008

truecrypt

Hello,

Have had another go at getting this working, based on instructions at
<http://forums.truecrypt.org/viewtopic.php?p=11726#11726>.

First run the installer, and select the unpack option to unpack the 
files. I put them in %SOFTWARE%\truecrypt\%VERSION%

hq packages # cat truecrypt.xml
<packages>
<package id="truecrypt"
          name="Truecrypt 6.1a"
          revision="1"
          reboot="false"
          priority="0">
        <install cmd='%SOFTWARE%\truecrypt\install.cmd 6.1a' />
        <upgrade cmd='%SOFTWARE%\truecrypt\install.cmd 6.1a' />
        <remove cmd='%SOFTWARE%\truecrypt\remove.cmd 6.1a' />
</package>
</packages>

hq truecrypt # cat install.cmd
"%SystemRoot%\System32\sc.exe" stop truecrypt
copy "%SOFTWARE%\truecrypt\%1\truecrypt.sys" "%SystemRoot%\System32\Drivers"
"%SystemRoot%\System32\sc.exe" create truecrypt type= kernel start= auto 
error= normal binPath= "%SystemRoot%\System32\Drivers\truecrypt.sys" 
DisplayName= truecrypt
"%SystemRoot%\System32\sc.exe" start truecrypt
xcopy /E /I /Y "%SOFTWARE%\truecrypt\%1" "%ProgramFiles%\truecrypt"

hq truecrypt # cat remove.cmd
"%SystemRoot%\System32\sc.exe" delete truecrypt
del "%SystemRoot%\System32\Drivers\truecrypt.sys"
rmdir /S /Q "%ProgramFiles%\truecrypt"

Issues:

* Not sure how to create shortcuts for the start menu.
* The above may not work for 64bit installations. There is a supplied 
truecrypt-x64.sys, maybe this is meant to be used instead of 
truecrypt.sys - if so I wouldn't know how to tell wpkg to use it instead.
* The first line in the install script stops the service (maybe this 
should delete the service?) in case it is already running so it can be 
reinstalled. Not absolutely happy with this.
* The SC create command line looks weird with lots of spaces but these 
are required.

Comments?

Brian May

-------------------------------------------------------------------------
wpkg-users mailing list archives >> http://lists.wpkg.org/pipermail/wpkg-users/

Gmane