[wpkg-users] Strange behavior of WPKG Client

[chiddie]

Ri-hello everybody (i know you hate me from the bottom of your hearts),

i have another awesome question for you.

I finally decided to deploy the WPKG Client x64 edition via Global Domain
Policy. I did not use the default domain policy, i created a new one -
called WPKG Client Deployment - that:
1. Is applied to domain computers only
2. Only contains an entry in Computer Configuration -> Windows Settings ->
Scripts -> Startup. The script contains the following lines:
Script name: \\serverip\WPKG\wpkg.js
Script paremeters: /install:WPKG_Client /quiet /nonotify /noreboot

The WPKG_Client package is put in a file called
"WPKG_Client_install_package.xml" that is into \\serverip\WPKG\packages
folder and contains the following instructions:


<?xml version="1.0" encoding="UTF-8"?>

<packages>
	
	<package
		id="WPKG_Client"
		name="WPKG_Client"
		revision="1.3.14 x64"
		reboot="false"
		priority="5">
 
		<!-- because the client hasn't been installed yet we cannot use the
SOFTWARE parameter for paths -->
		<variable name="PKG_PATH" value="\\servername\wpkg\software\WPKG Client"
/>
 
		<check type="uninstall" condition="exists" path="WPKG" />
		<check type="file" condition="versionequalto"
path="%PROGRAMFILES%\wpkg\wpkginst.exe" value="1.0.0.22" />
  
		<install cmd='msiexec /i "%PKG_PATH%\WPKG_Client_1.3.14-x64.msi" /qn
SETTINGSFILE="%PKG_PATH%\settings.xml"' />
		
		<upgrade cmd='msiexec /i "%PKG_PATH%\WPKG_Client_1.3.14-x64.msi" /qn
SETTINGSFILE="%PKG_PATH%\settings.xml"' />
	
		<remove cmd='MsiExec /x{0FAE4D7E-551C-4C50-8935-C05408A49A73} /qn' />
 
	</package>
	
</packages>

The hosts.xml file contains, for now, only the following lines, in order to
make the Domain Policy script above work (if i leave the hosts empty WPKG
says that it does not find any package to apply and i think it's correct):

<wpkg>
	
	<host group="Domain Computers" profile-id="WPKG_Client" />	

</wpkg>

The profile-id WPKG_Client is set in a .xml file called
WPKG_Client_install_profile.xml, put into \\servername\WPKG\profiles folder
and contains only the following lines:

<?xml version="1.0" encoding="UTF-8"?>

<profiles>

    <profile id="WPKG_Client">
	
		<package package-id="WPKG_Client" />

	</profile>

</profiles>

This said, here we go with the question. There are a few machines of the
network on which WPKG Client behave in a strange manner. Almost all of them,
after the post-installation reboot, correctly see that WPKG is already
installed and thus, as expected, the last line of their log is:

2011-12-16 08:59:55, DEBUG   : Package 'WPKG_Client' (WPKG_Client): Already
installed.

On other machines, apparently WPKG client apparently re-install itself at
reboot even if installed:

2011-12-16 08:56:12, DEBUG   : Package 'WPKG_Client' (WPKG_Client): Already
installed.
2011-12-16 08:56:12, DEBUG   : Going to install package 'WPKG_Client'
(WPKG_Client), Revision 1.3.14 x64, (execute flag is '', notify flag is
'true').
2011-12-16 08:56:12, DEBUG   : Package 'WPKG_Client' (WPKG_Client): Already
installed once during this session.|Checking if package is properly
installed.
2011-12-16 08:56:12, DEBUG   : Comparing version: '1.3.14 x64' <=> '1.3.14
x64'.
2011-12-16 08:56:12, DEBUG   : Package 'WPKG_Client' (WPKG_Client):
Verified; package successfully installed during this session.

Is there a way to try and track the reason why on these machines WPKG Client
cannot see that is installed yet (of course i can provide the full debug log
if needed)?
-- 
View this message in context: http://old.nabble.com/Strange-behavior-of-WPKG-Client-tp32986763p32986763.html
Sent from the WPKG - Users mailing list archive at Nabble.com.