I will probably solve the issue not using psexec (nobody seems to know why
it's not working via psexec and i can't wait weeks hoping that someone makes
a test and find what's wrong with psexec) but using a startup script
deployed via gdp (global domain policy). The instructions are basically the
same as the ones reported in the wiki page "http://wpkg.org/WPKG_Client"; at
the paragraph "installing via Group Policy".
================================================================
1. Create a package called WPKG_Client or something like that
2. Modify the package provided in the above page (Group Policy WPKG mix
section) changing data to match the last wpkg_client version avaiable
(1.3.14 as of now):
* in the check tipe file = condition line modify the value in 1.0.0.22
* in the remove line modify the uninstall string in
{0FAE4D7E-551C-4C50-8935-C05408A49A73}. WARNING: THIS STRING REFERS TO THE
1.3.14 X64 CLIENT INSTALLER. IF YOU HAVE TO DEPLOY THE X32 VERSION, YOU HAVE
TO GO TO THE REGISTRY OF A MACHINE WITH THAT VERSION INSTALLED AND CHECK FOR
THE RIGHT STRING (you can find it by searching the string "Artur Majuch"
and then looking in the uninstallString row in that registry folder).
3. Open the policy you want to modify by adding the script to deploy the
wpkg client (the global domain policy in my case, but you can create
another, of course, if yoy want).
4. Go to Computer Configuration -> Windows Settings ->
Scripts(startup/shutdown) -> Startup
* Script: \\myserver\myshare\wpkg.js (network path where the wpkg.js is)
* Parameters: /install:package_id /quiet (package_id is the id of the
package just created in point 1)
5. Save and you're done.
===============================================================
I have 3 questions:
1. Logging: is it possible to make WPKG automatically create a folder with
the machine name in order to put each machine log in a different folder?
Example: now i have edited the config.xml in order to
* log everything ()
* create a log file with this name ()
* put the log files in a specific folder ()
I wonder if it is possible to tell the program to log under a
\\\\servername\\\wpkg\\logs\[HOSTNAME] folder, with the program itself
creating the subdir [HOSTNAME] for every machine if it does not exists.
2. WPKG Service: is it possible to add a command that starts the service
after installation/upgrade without having to reboot the target machine? I
tried to add the command:
<install cmd='net start "WPKG Service"' /> after the line <install
cmd='msiexec /i...............>. The command succeeds (code 0) but the
service does not start.
3. Is it possible, ONLY for this package_id that deploys WPKG Client to
suppress the notify "The automated software installation utility has
completed installing...." that appears when Windows starts up if the machine
has not the WPKG Client installed?
--
View this message in context:
http://old.nabble.com/Push-Install-WPKG-with-Psexec-tp32930057p32958553.html
Sent from the WPKG - Users mailing list archive at Nabble.com.
-------------------------------------------------------------------------
wpkg-users mailing list archives >> http://lists.wpkg.org/pipermail/wpkg-users/
_______________________________________________
wpkg-users mailing list
wpkg-users@lists.wpkg.org
http://lists.wpkg.org/mailman/listinfo/wpkg-users
