07/12/2016 1190 views

Still kind of new to packaging, so please be patient.
I am tasked with configuring a transform/.mst (installshield) for an MSI created from a capture. The capture was only files being added to a folder, also created during the capture. The executable needs to connect to the SQL Server and Database. The information provided to me to work with as follows:

SQL Server: Tabquery.prod.xxx.com  (xxx - to represent omitted characters)

Queries SQL Server: tabfusionrms.prod.xxx.com

Is this as simple as adding these as properties to Property Manager in the transform? I am not able to test as the servers are in Production and not available in our test environment.

Thank you in advance!

0 Comments   [ + ] Show comments


All Answers

This content is currently hidden from public view.
Reason: Removed by member request For more information, visit our FAQ's.
The easiest way to incorporate database configuration information into an MSI/MST is by exporting the registry keys from a known good machine and adding them.
Answered 07/12/2016 by: vjaneczko
8th Degree Black Belt


>exporting the registry keys
That advice assumes that the connection will be via ODBC which may not necessarily be the case.

With nothing in the test environment (I'm wondering, though, what's preventing you from running up a VM, installing WinServer and SQL Server Express in that environment...) you're going to have to take a 'Before' and 'After' snapshot on a Production machine. That's the only way you're going to know what the configuration involves, be that registry, INI or XML file, whatever...

Answered 07/13/2016 by: VBScab
Red Belt