Problem deploying update to script engine 5.7
For those who may not know, MS released patches to update it's VBScript and JScript engines for XP, Windows 2003, and Windows 2000 a few days ago (links available here: http://bink.nu/Article10749.bink). I'm hitting a snag in deploment though. When I attempt to deploy remotely, the install fails every time. The last lines at the end of the install log are quite telling:
24.687: This operation requires an interactive window station.
24.687: Windows Script installation did not complete.
Select 'OK' to undo the changes that have been made.
24.687: Starting process: C:\WINDOWS\$NtUninstallscripten$\spuninst\spuninst.exe /~ -q -z
26.484: Software Update Rollback has completed successfully. The original error message was: 0x0
Seems very silly that it pretty much requires install at the console, given that much of the scripting that is done happens in enterprise environments where all installs have to be automated. Anyone have a workaround for this behavior by chance?
24.687: This operation requires an interactive window station.
24.687: Windows Script installation did not complete.
Select 'OK' to undo the changes that have been made.
24.687: Starting process: C:\WINDOWS\$NtUninstallscripten$\spuninst\spuninst.exe /~ -q -z
26.484: Software Update Rollback has completed successfully. The original error message was: 0x0
Seems very silly that it pretty much requires install at the console, given that much of the scripting that is done happens in enterprise environments where all installs have to be automated. Anyone have a workaround for this behavior by chance?
0 Comments
[ + ] Show comments
Answers (3)
Please log in to answer
Posted by:
rohowo
16 years ago
Hi Babscoole
Did you ever fix the problem you were having deploying WSE5.7 as I have the same issue but cannot find a solution anywhere.
Did you ever fix the problem you were having deploying WSE5.7 as I have the same issue but cannot find a solution anywhere.
Posted by:
Babscoole
16 years ago
Yep, I do remember my solution. I had to log into each system and install individually. Blah.
Posted by:
rohowo
16 years ago
Hi Babscoole
I seem to havee found an answer to your original post and as I hate to see incomplete blogs I thought I'd up date this. I found that to deploy windows Scripting Engine 5.7 using SMS you need to select the following options when creating the package. scripten /qiuet /norestart /overwriteoem. Its the overwriteoem switch that seems to fix the problem. The other option I found was within SMS itself where by I created the package with Allow User Interaction with Application (or something similar) even though the script installs silently. The machine will require a reboot for the oem files to be replaced but that can be automatic or scheduled using SMS if you want.
Hope this helps, if anyone else has this problem and my fix works that will be great.
Cheers
Robert
I seem to havee found an answer to your original post and as I hate to see incomplete blogs I thought I'd up date this. I found that to deploy windows Scripting Engine 5.7 using SMS you need to select the following options when creating the package. scripten /qiuet /norestart /overwriteoem. Its the overwriteoem switch that seems to fix the problem. The other option I found was within SMS itself where by I created the package with Allow User Interaction with Application (or something similar) even though the script installs silently. The machine will require a reboot for the oem files to be replaced but that can be automatic or scheduled using SMS if you want.
Hope this helps, if anyone else has this problem and my fix works that will be great.
Cheers
Robert
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.