Hello All,

That's interesting... I could have sworn that only what I call the "master install" (to the server) would result in removal from the server if an uninstall was done from that same workstation. Whereas an uninstall from a PC that had been installed via a "workstation install" (and I thought "allwkst.exe" qualified as such) would result in the module(s) being removed from that particular PC leaving the server installation in tact.

Maybe "allwkst.exe" works differently from the "wksetup.exe" that can be used to do workstation installs for individual modules... or as is often the case I'm just loony :-) However just recently I uninstalled 2 modules from a PC and then went right back and reinstalled them via a workstation install and all was well - I did not have to re-inistall to the server.

Because I had believed the above to be true, I have tried whenever possible (and it's not always possible due to crashes etc.) to do server installs / upgrades from the same PC (or at most 2 different ones).

On another note, something I've been asking for is somewhat related to this topic so I'll give it a plug here again.

I believe that if the Adagio "powers that be" at a company chose not to do a workstation install of a specific module at a specific PC - then users should not be able to "accidentally" start the installation by "accidentally" picking it from the Adagio menu of another module that does belong on that PC.

While I know that "Network Security" could be configured to prevent the install from completing... Wouldn't it be easier to have the Adagio menu only display modules for which data exists (as it does now) AND the module has already been installed at the workstation ?

Regards, Pete