Create custom automated install

[KePaHa]

We do server installs, but I assume same can be done onto a CD. We first built an admin install point by running setup.exe /a. Then ran through the CIW to point to the install .msi file and create an .mst file containing our preferred custom install choices. THis also allows you to pre-supply the License Key and all install options.

Then this whole install folder can be burned to cd. We wrote a batch file that calls the setup.exe for office and included the TRANSFORMS switch to identify the MST file to apply. It looked roughl like:

\\server\share\setup.exe" /lv* c:\officelog.txt TRANSFORMS="\\server\share\FileName.mst" /qb-!

So installers simply dbl-click on the batach file.

 

[KePaHa]

We do server installs, but I assume same can be done onto a CD. We first built an admin install point by running setup.exe /a. Then ran through the CIW to point to the install .msi file and create an .mst file containing our preferred custom install choices. THis also allows you to pre-supply the License Key and all install options.

Then this whole install folder can be burned to cd. We wrote a batch file that calls the setup.exe for office and included the TRANSFORMS switch to identify the MST file to apply. It looked roughl like:

\\server\share\setup.exe" /lv* c:\officelog.txt TRANSFORMS="\\server\share\FileName.mst" /qb-!

So installers simply dbl-click on the batach file.

 

[KePaHa]

We do server installs, but I assume same can be done onto a CD. We first built an admin install point by running setup.exe /a. Then ran through the CIW to point to the install .msi file and create an .mst file containing our preferred custom install choices. THis also allows you to pre-supply the License Key and all install options.

Then this whole install folder can be burned to cd. We wrote a batch file that calls the setup.exe for office and included the TRANSFORMS switch to identify the MST file to apply. It looked roughl like:

\\server\share\setup.exe" /lv* c:\officelog.txt TRANSFORMS="\\server\share\FileName.mst" /qb-!

So installers simply dbl-click on the batach file.

 

[KePaHa]

We do server installs, but I assume same can be done onto a CD. We first built an admin install point by running setup.exe /a. Then ran through the CIW to point to the install .msi file and create an .mst file containing our preferred custom install choices. THis also allows you to pre-supply the License Key and all install options.

Then this whole install folder can be burned to cd. We wrote a batch file that calls the setup.exe for office and included the TRANSFORMS switch to identify the MST file to apply. It looked roughl like:

\\server\share\setup.exe" /lv* c:\officelog.txt TRANSFORMS="\\server\share\FileName.mst" /qb-!

So installers simply dbl-click on the batach file.

 

[KePaHa]

We do server installs, but I assume same can be done onto a CD. We first built an admin install point by running setup.exe /a. Then ran through the CIW to point to the install .msi file and create an .mst file containing our preferred custom install choices. THis also allows you to pre-supply the License Key and all install options.

Then this whole install folder can be burned to cd. We wrote a batch file that calls the setup.exe for office and included the TRANSFORMS switch to identify the MST file to apply. It looked roughl like:

\\server\share\setup.exe" /lv* c:\officelog.txt TRANSFORMS="\\server\share\FileName.mst" /qb-!

So installers simply dbl-click on the batach file.

 

[KePaHa]

We do server installs, but I assume same can be done onto a CD. We first built an admin install point by running setup.exe /a. Then ran through the CIW to point to the install .msi file and create an .mst file containing our preferred custom install choices. THis also allows you to pre-supply the License Key and all install options.

Then this whole install folder can be burned to cd. We wrote a batch file that calls the setup.exe for office and included the TRANSFORMS switch to identify the MST file to apply. It looked roughl like:

\\server\share\setup.exe" /lv* c:\officelog.txt TRANSFORMS="\\server\share\FileName.mst" /qb-!

So installers simply dbl-click on the batach file.

 

[KePaHa]

We do server installs, but I assume same can be done onto a CD. We first built an admin install point by running setup.exe /a. Then ran through the CIW to point to the install .msi file and create an .mst file containing our preferred custom install choices. THis also allows you to pre-supply the License Key and all install options.

Then this whole install folder can be burned to cd. We wrote a batch file that calls the setup.exe for office and included the TRANSFORMS switch to identify the MST file to apply. It looked roughl like:

\\server\share\setup.exe" /lv* c:\officelog.txt TRANSFORMS="\\server\share\FileName.mst" /qb-!

So installers simply dbl-click on the batach file.

 

[KePaHa]

We do server installs, but I assume same can be done onto a CD. We first built an admin install point by running setup.exe /a. Then ran through the CIW to point to the install .msi file and create an .mst file containing our preferred custom install choices. THis also allows you to pre-supply the License Key and all install options.

Then this whole install folder can be burned to cd. We wrote a batch file that calls the setup.exe for office and included the TRANSFORMS switch to identify the MST file to apply. It looked roughl like:

\\server\share\setup.exe" /lv* c:\officelog.txt TRANSFORMS="\\server\share\FileName.mst" /qb-!

So installers simply dbl-click on the batach file.