Silent Installation Frontpage2003

[Gerry Hickman]

2. Find the Setup.ini file (in Files\Setup) and customise the display
settings to make it a quiet setup.

I believe you can also simply supply /qn on the MSIEXEC CMD line. The
setup.ini route is valid, but sometimes it's nice to keep setup.ini
clean so you get flexibility at setup time. e.g. you might want to run
one minute with full UI and the next you are blasting to a remote PC
with WMI or WSHRemote or PSExec, and want to include a transform. It's
also worth checking the %ErrorLevel% after any such install. Setup.ini
is a good place to set up centralized logging for the whole network, but
make sure the share is accessible, especially if your process is running
as local admin of the remote machine.

 

[Gerry Hickman]

2. Find the Setup.ini file (in Files\Setup) and customise the display
settings to make it a quiet setup.

I believe you can also simply supply /qn on the MSIEXEC CMD line. The
setup.ini route is valid, but sometimes it's nice to keep setup.ini
clean so you get flexibility at setup time. e.g. you might want to run
one minute with full UI and the next you are blasting to a remote PC
with WMI or WSHRemote or PSExec, and want to include a transform. It's
also worth checking the %ErrorLevel% after any such install. Setup.ini
is a good place to set up centralized logging for the whole network, but
make sure the share is accessible, especially if your process is running
as local admin of the remote machine.

 

[Gerry Hickman]

2. Find the Setup.ini file (in Files\Setup) and customise the display
settings to make it a quiet setup.

I believe you can also simply supply /qn on the MSIEXEC CMD line. The
setup.ini route is valid, but sometimes it's nice to keep setup.ini
clean so you get flexibility at setup time. e.g. you might want to run
one minute with full UI and the next you are blasting to a remote PC
with WMI or WSHRemote or PSExec, and want to include a transform. It's
also worth checking the %ErrorLevel% after any such install. Setup.ini
is a good place to set up centralized logging for the whole network, but
make sure the share is accessible, especially if your process is running
as local admin of the remote machine.

 

[Gerry Hickman]

2. Find the Setup.ini file (in Files\Setup) and customise the display
settings to make it a quiet setup.

I believe you can also simply supply /qn on the MSIEXEC CMD line. The
setup.ini route is valid, but sometimes it's nice to keep setup.ini
clean so you get flexibility at setup time. e.g. you might want to run
one minute with full UI and the next you are blasting to a remote PC
with WMI or WSHRemote or PSExec, and want to include a transform. It's
also worth checking the %ErrorLevel% after any such install. Setup.ini
is a good place to set up centralized logging for the whole network, but
make sure the share is accessible, especially if your process is running
as local admin of the remote machine.

 

[Gerry Hickman]

2. Find the Setup.ini file (in Files\Setup) and customise the display
settings to make it a quiet setup.

I believe you can also simply supply /qn on the MSIEXEC CMD line. The
setup.ini route is valid, but sometimes it's nice to keep setup.ini
clean so you get flexibility at setup time. e.g. you might want to run
one minute with full UI and the next you are blasting to a remote PC
with WMI or WSHRemote or PSExec, and want to include a transform. It's
also worth checking the %ErrorLevel% after any such install. Setup.ini
is a good place to set up centralized logging for the whole network, but
make sure the share is accessible, especially if your process is running
as local admin of the remote machine.

 

[Gerry Hickman]

2. Find the Setup.ini file (in Files\Setup) and customise the display
settings to make it a quiet setup.

I believe you can also simply supply /qn on the MSIEXEC CMD line. The
setup.ini route is valid, but sometimes it's nice to keep setup.ini
clean so you get flexibility at setup time. e.g. you might want to run
one minute with full UI and the next you are blasting to a remote PC
with WMI or WSHRemote or PSExec, and want to include a transform. It's
also worth checking the %ErrorLevel% after any such install. Setup.ini
is a good place to set up centralized logging for the whole network, but
make sure the share is accessible, especially if your process is running
as local admin of the remote machine.