Hello:
In this instance I'm using "primary" to refer to the computer from which Adagio module(s) were installed to the server. If the Windows Uninstall process is used, Adagio will be uninstalled from the server.

In cases where the primary computer is to be used for another purpose, it would be prudent to remove all references to Adagio. What is the recommended way to accomplish that?

NB: This discussion does not apply to computers where Adagio is installed through the Workstation setup process. In those cases, the Windows Uninstall process removes Adagio only from that particular computer.

Hi Bruce,

If Adagio was installed to a network from a particular workstation, it definitely would not be prudent to run the Windows Uninstall of Adagio, for the reason you outlined.

If you want to use this workstation for a different purpose (ie never use Adagio again), and want to clean up other files, you could delete all Adagio-related Windows shortcuts and Windows start menu items. Also remove the C:\softrak folder and all sub-directories (for workstation setup info and help files). All that would be left are some Crystal files and Windows registry settings and a couple of files in the System folder - not much when workstations these days have hundreds of gigs of hard-drive space.

For a complete list of files installed by workstation setup, you could look in the INSTALL.LOG found in the C:\softrak\xxWin\wksetup directory, if you wanted to perform a more thorough clean-up.

Hello Support:
Thank you. That works to prevent anyone from running Adagio (which is admittedly the most important issue).

However it still leaves the Adagio modules available to be removed throught Windows Add/Remove Programs. And that leaves open the possibility of Adagio modules later being inadvertently uninstalled by a zealous IT professional.

I found the following Knowledgebase article from Microsoft that explains how to remove the Adagio modules from the Add/Remove list. It requires editing the Registry. The Registry is a key component of anyone's computer so caution must be exercised.

Microsoft KB article 314481