We are using the free version of ScriptX v7.0.0.8.  Our enterprise users are migrating from Windows XP with administrator privileges to Windows 7 with non-administrator privileges.  Our application now prompts the users for elevated UAC credentials when they encouter an smsx.cab object ScriptX reference.  We want to supress this prompting and allow ScriptX to install.  To accomplish this, we have implemented an ActiveX installer group policy change for our internal server to allow it to install (http://technet.microsoft.com/en-us/library/cc721964(v=ws.10).aspx).  However it is still prompting for UAC after this policy is applied.  We noticed that the ScriptX certificate is expired as of 3/7/2011.  Does this prevent the unprompted install?  Is there a new certificate available?

v7.0.0.8 of smsx.cab is signed with our Class 3 cert that expires on 08/6/2014. Are you sure you have the right file?

  http://my.meadroid.com/scriptx/bits/7.0.0.8/smsx.cab

For a successful install you still need to be logged ln with full local admin privileges.

Please do NOT attempt an install without access to local admin privileges (i.e. someone must be logged on as a member of your PC's computer administrator user group. NOT 'domain' or 'virtual' or 'remote' or any other sort of admin, this must be *local*).

Jerry

The Quick PDF Library DLL Edition from Debenu pty ltd (QuickPDFDLL0812.dll) in the msi in the cab is not signed.  Is there a cab with a signed version of this dll?

Thanks for the spot.

>> Is there a cab with a signed version of this dll? <<

Well not now (otherwise I guess that we'd be using it!) but we will get this fixed.

Is it causing you a problem, and - if so - specifically what?



Jerry



An update from Pete:

I am not sure if the technique they have deployed (ActiveX installer group policy change) will work because although smsx.cab is using Internet Component Download (aka cab) as the delivery mechanism, the install procedure launches scriptx.msi to install via the Windows Installer Service. I expect this service will give rise to the UAC prompt. As I read the group policy change it only works for self-reg dlls. We no longer supply self-reg dlls. Any attempt to deconstruct the MSI and/or grab the dlls and use self-reg with them is doomed to failure and - as we have long said - is completely unsupported.

I hope that this helps

Jerry