Moin Michael,

Thanks for the clarification. 

Grüße

Jörg

Hi,

Every year arround x-mas I carry out some maintenance tasks on our server as well as client computers. This year I would like to update our Mercury/Pmail multi-user system to the latest releases. Presently Mercury 4.52 is running on the server. Also Pmail 4.41 (fully german version) is installed on this server in another directory. All user mail folders are located under Mercury\mail\... on the server. On each client PC there is only a link to the winpm-32.exe at the server.

Now I would like to update to Mercury 4.72 and Pmail 4.51 (german). Are there any update instructions available for such multi-user systems? I'm not interested to loose any configurations because the system runs very stable.

I think I could start the installation process of Mercury and it detects whether a system is already installed or not. Depending on it it carries out a complete new installtion or an update only, isn't it?

For Pmail, may be I could install the new release to any local folder and than copy it to the Pmail directory at the server without overwriting any configuration files like pmgate.sys or synonym.mer.

Have already searched the FAQs but unfortunately found no postings which match my concern.

Could anybody advise?

Greetings from cold Germany

Joerg

> Now I would like to update to Mercury 4.72 and Pmail 4.51 (german). Are there any update instructions available for such multi-user
> systems? I'm not interested to loose any configurations because the system runs very stable.
>
> I think I could start the installation process of Mercury and it detects whether a system is already installed or not. Depending on it
> it carries out a complete new installation or an update only, isn't it?

Correct, both PMail and Mercury will update an existing system without modifying any user data.  With a multiuser setup all Pegasus Mail users must close Pegasus Mail and Mercury needs to be closed in order to do an update.  The whole process should take only minutes to accomplish.

Hi Thomas and thanks for your quick reply.

But what about any new functions of the latest releases? They are may be not configured by the old config files. Is it always ensured that the new releases work stable with the old configuration files and user settings?

> Hi Thomas and thanks for your quick reply.
>
> But what about any new functions of the latest releases? They are may be not configured by the old config files. Is it always ensured that
> the new releases work stable with the old configuration files and user settings?


The new functions may have to be configured but the new release will provide a default configuration for anything critical to the new release.

Hi Thomas,

As I told both installations (Mercury and Pmail) are installed on a server. Could I nevertheless start the installation processes from my client pc and give them the UNC installation path for the current Mercury/Pmail installations at the server? Or are they exchanging/adding any files or keys at the windows system or windows registration database, and that's why it's necessarily to carry out them from the own system (server) only?

I believe to remember that Mercury and Pmail are installing files in their own installation folder only without changing anything on the Windows system, isn't it?

Brgds

Joerg

> As I told both installations (Mercury and Pmail) are installed on a server. Could I nevertheless start the installation processes from my
> client pc and give them the UNC installation path for the current Mercury/Pmail installations at the server? Or are they
> exchanging/adding any files or keys at the windows system or windows registration database, and that's why it's necessarily to carry out
> them from the own system (server) only?

There are things that go into system registry nowadays so I would only do the install on the server just as a safety measure.  It can be done remotely, and I have done this with topless servers from my workstation.

> I believe to remember that Mercury and Pmail are installing files in their own installation folder only without changing anything on the
> Windows system, isn't it?

Yes, this is correct except when you are using third-party daemons and file extensions that talk to the system registry.  Again, this generally is not a problem but if you can do this from the server I would do so.

OK Thomas, I try this next week, when I'm alone at the office.

Thanks for your always good help and merry X-mas

Hi Thomas,

I have installed both new releases without bigger problems. Pmail I have updated from my Client PC to the server directory. The Mercury update I have launched from the server directly. After finishing the Mercury update I was a little bit confused because the X scheduler did not start up. It only said "waiting for processes to be ended" (or something like that). But after waiting a few minutes Mercury starts the retrieving and sending procedures as usual.

One missing thing in Pmail:  In 4.51 German Version I miss the entry "Change User" under FILE at the menu bar. Now I'm not able to jump between our different user mail boxes quickly. Now I have to close pmail first and restart it with the option "-i" + "user name". This was much faster in the old version with "Change User".

Brgds

Joerg

[quote user="Joerg"]One missing thing in Pmail:  In 4.51 German Version I miss the entry "Change User" under FILE at the menu bar. [/quote]

People complain a lot about this issue, here's one of Thomas' frequent replies.