Software Deployment

seems to me that if you want a VBscript to execute against a machine that there wouldn't be any reason to put it into an MSI unless it's facilitating the installation or uninstallation of the rest that same MSI. If you want to execute a VBscript maybe you should consider using the Login Script portion of a GPO. You can even add a VB script to an already linked GPO.

So let's say you have the following:
GPO named: APP Snowball
and in its scope is a group called:
LS APP Snowball 1.0 - Users
and in the GPO's User Configuration > Software Settings portion you have Snowball1.MSI assigned

And the problem is the MSI doesn't uninstall properly for whatever reason, and you've written a VBscript that WILL effectively remove Snowball, then I guess I'd remove the MSI from the GPO, but leave the GPO linked and leave that AD group in its scope, and simply add your VBscript that uninstalls Snowball to the Login Script portion under the Windows Settings portion of the GPO. - No need to nest your VBscript via a Custom Action into an otherwise useless MSI.

Not a bad idea !!! but we going to use AD to deploy this program., AD will take MSI i have already created msi that would uninstall old version of appl & install new version back in... but now i have to created just one msi for uninstall for those users ( few not getting new version ).. add ODBC drivers for some other application.. using wise i can't execute any appl to capture inorder to uninstall .. only way this can done by inserting vbscript for uninstall & adding ODBC for some in MSI .. Any suggestion

In Windows Installer Editor (Wise) you can simply create a new (blank) msi when you choose from the right template "Windows Application". And then just add your VB Script (and if applicable) put a condition to it - that's it.

SO i can just ignore the captured software window in wise ? add my vbscript to msi.. i did try this method but gave me error, will try to do it again & see what happens... Let me ask you , is there way i can add ODBC settings to get install in same MSI..

SO i can just ignore the captured software window in wise ? add my vbscript to msi.. i did try this method but gave me error, will try to do it again & see what happens... Let me ask you , is there way i can add ODBC settings to get install in same MSI..


Just start "Windows Installer Editor", go to File - New and choose the "Windows Application" template. Then you can just put in your VB Script. But you will probably get an error if your package doesn't have a component. When you have the msi open, just go to "Setup Editor", choose the "Components" tab, right-click and select new component. Just give it a name and save it.
And yes, you can put the ODBC settings in the same file. Just make sure things run in the correct order.

sikkert is right. You need to add a component to your blank msi. In addition, I recommend to add a dummy file to prevent the error ICE70 (Media Table empty).

We use to add ODBC information through the registry tables only (not the ODBC tables). Sometimes you get problems with the ODBC tables. If you deploy ODBC information through the registry table, it gets removed during uninstallation of the msi.

If the problem is solved its good. Otherwise you may just try this option -

--- Run Setup Cature
--- Use Snapshot option with SmartMonitor
--- Re-run the initial scan
--- Do not give any .EXE Name or Command line value, just click "Next"
--- Excule all files and registry values, if any are captured
--- Give a package name and click "Finish"

You will get an empty .WSI file. Now you may add a VB Script to the file and compile it into a .MSI file.

Hope this helps.

Regards,
Nilo.

Thanks a lot i was able to insert script into my blank MSI & it works fine.... but i'm having problems adding ODBC to the same msi can someone help me out.. thanks