Has anyone silently deployed WSH5.6 at all?

I'm looking at it and have found a few issues.

If I run the scripten.exe program with the /q switch, it either wants to prompt for a reboot which I can't supress and/or it creates some "runonceex" reg keys to register the dll's the next time someone logs in. The problem is that the runonceex keys don't work if the person logging in is a standard "user" which is what all our users are and they keep getting errors coming up as a result.

I then tried repackaging it doing a snapshot, but on SP3 machines, Windows File protection keeps "healing" WSH back to v5.1 and on SP4 machines the DLL's fail to register correctly sometimes.

Does anyone have any ideas or is it all just something strange in our environment?

0 Comments   [ - ] Hide Comments


Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
Answer this question or Comment on this question for clarity


I don't think this is just you. Registrations following reboot are not uncommon, however this is complicated by the fact that you cannot repackage it with all those Windows protected files. Short of automating an admin logon following reboot, I would recommend using the commandd line installation followed by your own script to perform the actions and then remove what you see in the runonce values.

To silence the reboot request- you tried /q and /qn? I think this uses IExpress for the installation and IExpress supports the /R switch:

R = /R:A (Default)
/R:= /R:A (Default)
/R:N -- Never reboot, overrides INF settings in package
/R:A -- Always reboot, prompt user with reboot choice
/R:I -- Reboot if needed, prompt user with reboot choice
/R:AS -- Always reboot, silent and don't prompt user
/R:IS -- Silent reboot if needed, silent and don't prompt user
/R:ND -- Tell Wextract to check for reboot state before running any RegisterOCX sections. If machine is in reboot state before the install and that state wasn't caused by the package then queue up registrations in Runonce automatically. This usually is used for cases where an install depends on something that was installed earlier, but maybe hasn't finished for some reason.

I'd give /R:N a try!

Let us know how it goes!
Answered 12/03/2003 by: bkelly
Red Belt

Please log in to comment
Love the undocumented switches... That seems to have made everything work just how I needed it to....

One package database entry coming up!
Answered 12/03/2003 by: thewspot
Senior Yellow Belt

Please log in to comment
No problem! Thank you for adding these details to the Package Knowledge Base. It is sure to save others some serious time!
Answered 12/03/2003 by: bkelly
Red Belt

Please log in to comment