I’ve deployed MS08-012 to a client machine. The action completes & the status changes to Pending Restart. The client machine is restarted & the status changes to Waiting. It eventually will fail. When I go into the view action info & action script execution detail, all the actions are complete, none of the actions have failed.
I check the client log & at 12:47:25 the action 32094 is relevant.
At 12:49:14 it’s Not Relevant but the Fixlet is still listed in the Relevant Fixlet Massages tab for this client.
I’ve completed the following guidelines & all are ok from the server.
From the client machine when I try ‘net use \servername\sharename /users:’ I get a “system error 53 has occurred. The network patch was not found”. I checked a another client that the office patch did install on successfully & it gets the same error. Windows firewall is switched off on both machines & they are both a standard build.
This is only one office patch that has failed but there are others. I’m hoping getting to the bottom of this issue will fix the others.
You have previously installed OFFICE 2003 from the admin point.
You have patched that administrative installation point.
Here is more you can do, given you have access to the client machine:
Before you take the action at the console, you can take out “/Q” in the first line of the action script. When the action is executed at the client machine, the UI will pop up, and you can see what goes wrong from there.
wait … REBOOT=REALLYSUPPRESS /Q
Administrative Install is basicall reinstall from the adminPoint. With that said, you can modify the registry key value “Comments” under the below key. For example, add some random string. If the admin install finishes successfully, the string you put in will be overwritten.