You have a couple options:

A) you can use orca to modify the msi to provide the correct default value. support.microsoft.com/.../255905

B) You can create a transform file and use the /t command line option to apply it. msdn.microsoft.com/.../aa367447%28v=vs.85%29.aspx

You should also know that the msi by itself DOES NOT install the prerequisites such as .NET and MSVC runtimes. These are installed by using the autorun.exe, so if your workstations don't have all of the prerequisites javascript:void(0);installed, you will run into problems. I think the prereqs all have msi installers too, but you need to find out which ones are actually required.

dlech I am currently in a similar situation as bkern where i am using Orca to try and edit the MSI for mass installation. Do you happen to know where in the MSI the argument for the "Server Name" and "UNC Path" are?  I was able to get the Port to answer correctly, but the places i thought i found for the UNC Path and Server name are not working as it seems to be configured somewhere else in the MSI and does not take my Values when i add them in the Property.

As you are trying to run two work station setups on the same work station. You actually don't have to run the second instance. You just have to edit the sage.ini and add the second instance and distribute. All the prerequisites and runtimes and DLLs will be installed on the first instance.

We don't use Orca (We use PDQ), but I imagine they are somewhat similar.  In PDQ we pass the following, just update %SERVER% with your servername & %PORT% with your port #.

msiexec /i "\\%SERVER%\sage\sage 100 premium\MAS90\wksetup\Sage 100 2018 Workstation.msi" /q /l*v C:\Windows\Temp\Sage100Install.txt SAGEPORTID=%PORT% SAGESERVERNAME=%SERVER%SRCSERVERPATH="\\%SERVER%\Sage\Sage 100 Premium\MAS90\" INSTALLDIR="C:\Sage\Sage 100 2018 Workstation\MAS90\"

I actually went the same route of scripting after i was unable to get the custom MSI to work.  Was able to successfully deploy over PDQ and get both instances of the server running by using the suggestion from BigLouie with the sota.ini file.  I also got the deployment process to update the port for the Sage 100 PDF Converter.  Thank you for the reply though!

Hi CtheissIBP,

Which line or command did you use to update the port for the Sage 100 PDF converter?

I am in the process of migration Sage 100 2016 to 2019. I was able to create a batch file that uninstall the old version (2016) and install the new one (2019).

I used the line from RedemptionMatt and I modified a little nit. My batch file look slike this:

msiexec /x {744EF34E-713C-4863-B102-68C0DEAA5DAE} /quiet
msiexec /i "\\SERVERNAME\SageSoftware\v610\MAS90\wksetup\Sage 100 2019 Workstation.msi" /q /l SAGEPORTID=PORTNUMBER SAGESERVERNAME=SERVERNAME SRCSERVERPATH="\\SERVERNAME\SageSoftware\v610\MAS90" INSTALLDIR="C:\Sage\Sage 100 Workstation"

How did yo update the port for the Sage 100 PDF Converter in the installer?

Do you mean the port # for Advanced CS/ODBC?  That is added runtime to SOTAMAS90, not during the install.

At the end of the installation under printer and devices in windows, we want to create a local custom port for the Sage 100 PDF converter called "Sage100" and we want to Allow Everyone  to Manage the printer and documents under the Properties. 

That should not be necessary for v2019 (...only the registry permission...HKCC\Software\...). 

I have not had to mess with the PDF Converter's print object port / permissions on new workstations since Sage upgraded Amyuni drivers a few years ago.