silent installation

[rafnews]

Hi,

at work we have several hundreds of computers having a licensed version of total commander.
however, as there are various versions, we would like to:
- uninstall previous version
- install latest version according to licenses we bought

my questions are the following ones:
- how to detect which version is installed and in which directory ?
- how to backup settings before removing it ?
- how to install the new version

everything should be in silent mode and will be run once when users log onto acive directory (via NETLOGON script).

Can we perform those steps ?
where can i find some help, tutorials or documentation ?
thanks a lot,

Alain

[sqa_wizard]

2rafnews: Welcome to the forum !

First of all: You do not need to uninstall any old version, just install the new version on top.
Installed version is detected automatically.

- install latest version according to licenses we bought

The license is valid for every version (From 1.0 to the current one 7.04a)

where can i find some help, tutorials or documentation ?

Just search the forum for "unattend" and you get the answer

[rafnews]

thanks for info.

i just have additional question:
- what if total commander is installed several time on different folders on the same computer ? I know it's stupid but some people are crazy.

thx.

[ts4242]

- what if total commander is installed several time on different folders on the same computer ? I know it's stupid but some people are crazy.

No harm! I have now 13 beta versions of TC 7.50 installed on the same computer on different folders, this is because for testing purpose sometimes I want to back to an old beta version! So I'm the biggest crazy!

[HBB]

To rafnnews,

I am agreed with you about that it is difficult to install TC on every machine in a company. Why don't you try to use TC over server on which TC is installed portably.

In our company, unfortunately, I only use the TC. A short time ago, I have decided to install TC on server. My aim was to introduce the TC to my friends. For two or three weeks, my friends have started to try and to use TC over server. I am able to add all plugins, buttons, ...etc. on one copy on the server. Now, we are on a trial period. At the end of the period, if my friends like TC and decide to use it continuously, we will increase our licences as required.

This installation method may be helpfull for you. "ini" files may specialized for each users if you want.

[rafnews]

basically we have 1200 computers on which we would like to install/upgrade to latest version.

unfortunatelly the policy here is to not install it on server. we have thin client but only 300 pieces. so TC on server is not a solution for us.

Moreover we have cca 300 notebooks on which TC must be installed and as those notebooks are quite used a lot outside company via different networks and network configuration, it make no sense to setup a TC on server.

A.

[ghisler(Author)]

You should try to install the program via group policy if you have so many computers. This is done with a custom MSI (micrsoft installer) file.

There isn't an MSI file available because it wouldn't install the registration key and settings. However, there is a way to create such an MSI yourself quite easily, and at no cost:

The basic idea is to create a custom msi file (microsoft installer) with all your desired settings and files (e.g. key file), and then deploy this.

See: www.windowsnetworking.com

Brief description of the above link:
1. Get WinInstall LE 2003 (link see the above page)
2. Take a snapshot of the test system with WinInstall LE 2003
3. Install Total Commander with the options you need. I recommend that you configure the ini file location to use individual per user settings
4. Take again a snapshot of the test system with WinInstall LE 2003 to create the MSI
5. Deploy the MSI

[Lefteous]

MSI is a crime against humanity and should be outlawed.

[ghisler(Author)]

Why? Do you have a better solution for an automatic installation on 1000s of computers?

[Lefteous]

Why?

It's deadly slow and has a large footprint on target system.

Do you have a better solution for an automatic installation on 1000s of computers?

TC's great new copy to multiple targets function

[petermad]

TC's great new copy to multiple targets function

Should be:

The upcoming TC 7.50's great new copy to multiple targets function

[djgtram]

There isn't an MSI file available because it wouldn't install the registration key and settings.

I always wondered why you don't finally provide a proper MSI installer file. This is probably some misinformation, MSI can store registry settings all right and even if it happens to not provide some functionality you need, you can always add your custom action code. Not having a correct installer in 2009 is a serious drawback and, frankly, doesn't go well with the professional quality of your program.

[Balderstrom]

I wouldn't call MSI proper... proprietary maybe...
A lot of the software I install uses Nullsoft or InnoSetup, of which I prefer those to msi or InstallShield -- both of which tend to dump a slew of junk into the registry and redundantly copy most of the whole unpacked install data into %ProgramFiles%\InstallShield Installation Information or elsewhere.

[djgtram]

I wouldn't call MSI proper... proprietary maybe...
A lot of the software I install uses Nullsoft or InnoSetup, of which I prefer those to msi or InstallShield -- both of which tend to dump a slew of junk into the registry and redundantly copy most of the whole unpacked install data into %ProgramFiles%\InstallShield Installation Information or elsewhere.

Proprietary*, yes, of course, still, this is "the" (in Linux parlance) package manager in Windows, responsible for maintaining consistency of dependencies, offering numerous features like administrative or silent installs, repair, removal, everything.

You seem to mix the format (MSI) with the tool creating it. InstallShield is a very bad solution, I agree, but a mediocre tool doesn't make MSI as a format something to be avoided. A properly authored MSI installation package doesn't put anything into the registry you don't ask it to put there (well, OK, one single entry for Add/Remove Programs, but any other installer does the same to allow the user to uninstall) and it only leaves a very small datafile (dependent on the size of the application to be deployed, which is rather small in the case of TC) in the Windows Installer database.

If you use a correct MSI authoring tool, you can get all the benefits of the system's built-in installer functionality without any adverse effects. I speak from experience, I do it regularly as a programmer...

* Addendum: proprietary in a way, but in no sense closed. The format is completely documented and MS even provides tools to edit it directly and manually (not that manual editing would be a comfortable way of authoring setup but it opens up the format completely and transparently).