Scripting Question

Is there a way that a VB Script can edit an Ini file created at the time of launching an application for the 1st time and the place it in the user profile.

11/03/2017 691 views

I have repackaged an .msi using Wise package studio. When this msi is launched for the first time after installation, it creates a .ini file which contains Licensing server details, port number & a location where user can save his/her work in a private folder. 

While checking the .ini file created by .msi after launch, I found out that it contains incorrect license server details & was pointing to my user profile. Hence I want to know, is there a way through which I can overwrite the .ini file created by .msi and copy it to the user profile path. 

Thanks in advance !!

0 Comments   [ + ] Show comments


All Answers

Does the MSI use the INIfile table or does it treat it as a file? If the former, use a transform to:

- create a property or properties containing the server details
- reference the property/properties in the INIFile table's values.

If the MSI contains any advertised entry-points (e.g. advertised shortcut(s)) you'll need to re-jig the feature tree in order to use self-healing so that the INI goes in to the user's profile.

If the latter, it gets a little more complicated.

Seek out the rather wonderful JSWare INI file class (search ITNinja for 'clsINI'). Create a VB Script to edit the relevant section's values and set up your transform to run it using Active Setup.
Answered 11/03/2017 by: VBScab
Red Belt

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login

View more:


This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ