Hello,
I am deploying software using 2 scripts, here is the basics of what the script does :
Script1 : Sets runonce key for Script2, uninstalls existing software for XP, reboots or if the computer is windows 7 installs new software
Script2 : Installs software for Windows XP
Script1 is "working" in that it does uninstall the existing or if the device is Windows 7 will install the new software.
Script2, being set in the HKLM\.....\RunOnce, is failing when the installation starts after the user logs in for Windows XP, Doesnt matter if the user is admin or not, which I would guess when run this way will be system account? Here is a step by step process of what the scripts do :
Check the OS, If Windows XP - Set RunOnce key to point to script2, Uninstall 3 Components using WMI, reboot, else if Windows 7 installs the MSI's for the new software.
After the XP computer reboots Script 2 starts (I know it is launching because it is echoing using cscript its progress), when it gets to installing the first MSI it starts, then fails. This is the log file of the MSI.
=== Verbose logging started: 6/27/2012 6:45:37 Build type: SHIP UNICODE 3.01.4001.5512 Calling process: C:\WINDOWS\system32\msiexec.exe ===
MSI (c) (64:6C) [06:45:37:127]: Resetting cached policy values
MSI (c) (64:6C) [06:45:37:127]: Machine policy value 'Debug' is 0
MSI (c) (64:6C) [06:45:37:127]: ******* RunEngine:
******* Product: DesktopComponents\WindowsXPInstallers\SentillionVergenceDesktopComponents.msi
******* Action:
******* CommandLine: **********
MSI (c) (64:6C) [06:45:37:127]: Client-side and UI is none or basic: Running entire install on the server.
MSI (c) (64:6C) [06:45:37:127]: Grabbed execution mutex.
MSI (c) (64:6C) [06:45:37:175]: Cloaking enabled.
MSI (c) (64:6C) [06:45:37:175]: Attempting to enable all disabled priveleges before calling Install on Server
MSI (c) (64:6C) [06:45:37:206]: Incrementing counter to disable shutdown. Counter after increment: 0
MSI (s) (98:F4) [06:45:37:222]: Grabbed execution mutex.
MSI (s) (98:88) [06:45:37:222]: Resetting cached policy values
MSI (s) (98:88) [06:45:37:222]: Machine policy value 'Debug' is 0
MSI (s) (98:88) [06:45:37:222]: ******* RunEngine:
******* Product: C:\Documents and Settings\a_cgilbert\DesktopComponents\WindowsXPInstallers\SentillionVergenceDesktopComponents.msi
******* Action:
******* CommandLine: **********
MSI (s) (98:88) [06:45:37:237]: Note: 1: 2203 2: C:\Documents and Settings\a_cgilbert\DesktopComponents\WindowsXPInstallers\SentillionVergenceDesktopComponents.msi 3: -2147287037
MSI (s) (98:88) [06:45:37:237]: MainEngineThread is returning 3
MSI (c) (64:6C) [06:45:37:237]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (c) (64:6C) [06:45:37:237]: MainEngineThread is returning 3
=== Verbose logging stopped: 6/27/2012 6:45:37 ===
Am I doing this the rights way? I would rather not use a Task Sequence because it seems like the source files remove from the system when the task is done, causing issues with repair or uninstalling, also I have not had great luck with a Task Sequence re-starting right away when the computer reboots. The second script does work when run after the user has logged in.