I am running the following action script to install WinXP SP3. Although it runs and installs successfully I am getting a failure on the status.
Within the actionscript custom success criteria I have tried options of ’ … all lines of the action script have completed successfully’ and '…the following relevance clause evaluates to false. Either way although the command runs successfully and installs WinXP SP3 and reboots I still get a failuire.
I am running the install locally via a DOS command.
Relevance:
(name of operating system = “WinXP”) AND (platform id of operating system = 2) AND (free space of drive of parent folder of system folder /1000 /1000 > 1500) AND (exists file “WindowsXP-KB936929-SP3-x86-ENU.exe” of folder “C:\Local\System\packages\XPsp3”)
Action script:
DOS “C:\Local\System\packages\XPsp3\WindowsXP-KB936929-SP3-x86-ENU.exe /quiet /passive /log:C:\Local\System\packages\XPsp3 /forcerestart”
If you see failed until the next reboot, try adding a “action requires restart” to the end of your action. I’m not even sure this will help because your SP is restarting the machine before the action completes.
lmpymilk is correct. However, if you just add ‘action requires restart’ the client will report ‘pending restart’ prior to the actual install completing and you may accidentally reboot the machine prematurely.
Instead of using the ‘DOS’ command, try launching it with “waithidden”. That way the client will wait for the installer to complete before reporting a post-action status. You should also still add the ‘action requires reboot’ line.
An even better option would be to use the upgrade Fixlets BigFix has published:
I have tried the ‘waithidden’ with the ‘action requires restart’
Although the service pack installs and the action script restarts the machine the Fixlet status still reports ‘Failed’.
Again I have also tried setting the custom success criteria to ‘all lines of the script have completed successfully’ and ‘the applicability relevance evaluates to false’.
The log file also reports that the Fixlet is no longer relevant.
well if you look in the console I am going to bet it starts failing after your SP install. This is because you have your SP restarting the machine in the middle of the action. So the action did fail as in never completed.
If this is the case you might want to remove the “/forcerestart” and use either shutdown from the system folder of the target or use a reboot message from the BigFix action.
I think the the BigFix "restart " will always be 1 minute or more.
If you want to restart now you can use “wait shutdown -r -t 00”