Once upon a Clean Vista machine that was deployed via WDS and placed in correct OU a simple Computer based software installation Group policy was applied. Some of the MSI's were successfully deploy - mostly commercial ones eg flashplayer, clickview player, plus one or two of my created MSI's.
All the MSI's created by myself were created with appdeploy's repackager on a clean Vista machine. (Wininstall LE no longer works on Vista)
We also live in the land of Server 2003 with only standard security group policies applying at the level of this OU.
The system Event log records:
"The assignment of application clickview library location from policy standard software failed. The error was : %%1603"
In reading around it would appear that the 1603 error is possibly related to privileges in launching the installer script at start up, as per post http://www.experts-exchange.com/OS/Microsoft_Operating_Systems/Windows/XP/Q_24299878.html
However Vista does not appear to have the InstallShield InstallDriver config options under DCOM config. From reading http://msdn.microsoft.com/en-us/magazine/cc163486.aspx#S6
I would suggest that the MSI's that failed all require changes to HKLM registry keys. Also there is some way to elevate the privilege of the MSI so that it doesn't require a token??
BTW - UAC is turned off on the machine and the MSI's in question will all install by manually starting them (without having to run as administrator).
I am somewhat at a loss for how to proceed. Suggestions welcome including, "Oh we do it this way, I thought everybody knew that..."