Rehosting ConsoleWorks - Windows Server 2003

From TDiWiki

Jump to: navigation, search

The qustion was asked of TDi:

"We intend to upgrade the ConsoleWorks server to Windows 2003 as well as upgrade to Console Works 3.5. Before we commence, could you please advise the best approach to this task to save pre-existing configuration & logs. The upgrade to Windows will be a clean install, effectively wiping everything on the box. Could you please advise?"


The most prudent approach would be this:


- Read the Install guide for version 3.5-0u0

- Login to the existing server and disable all consoles

- On the v2 server, verify and/or change Server Host Address to: 0.0.0.0 (It can be found on the >Admin Configure Server page.)

- Log out and stop the ConsoleWorks service(s)

- Backup the entire ConsoleWorks tree: <drive>:\program files\Tdi

- Uninstall ConsoleWorks from the "old" server (This will leave only the data related to your invocation behind )

- Backup the Uninstalled ConsoleWorks tree which now contains only your invocation data

- Do the clean install of Windows Server 2003 and get it stablized

- Restore the Uninstalled ConsoleWorks tree of your data

- Install the new ConsoleWorks package over the restored tree

- Start the ConsoleWorks service(s), log on and begin testing.

- Register ConsoleWorks on the new server

When your users login, they will each need to change their passwords. This is a new feature in the 3.x line of ConsoleWorks.


-- SSL Considerations --

Before the change, login via your browser and go to the menu item for Admin > Server > Configure. If the Require SSL Connections is set to Yes, you should set it to No for the move and any subsequent testing, until you are comfortable that all is well.

If you are using SSL, and the server certificate was created using the IP address as opposed to the host name, and you're not going to re-use the same IP address, then a new cert needs to be created. (Creating the SSL cert is detailed in the installation guide.) You should create a new cert using the host name.

Also on the SSL front, if you do need to create a new server cert, then your users will need to click Download > Local > SSL Certificate from within their browsers after the new server is up and running.

Personal tools