Migrating Enterprise Commander to a Windows server host

Owned by Pramuk Shyam Pathy (Unlicensed)
Last updated: May 18, 2015

Migrating the Enterprise Commander server to a Windows host is easy if you are using an SQL server to store your data.

Note

Currently there is no migration path to migrate the Enterprise Commander server to a Windows host if you are using the internal database to store your data.

Guide to Migrating Enterprise Commander to a Windows Server host.

STEP 1: Hardware and Operating Systems Requirements

Enterprise Commander requires the following virtual servers set up in Hyper-V or VMWare:

  • A 64-bit Windows Server (2008 or 2012 R2) at your current patching level with t he following:

    CPU: 4 
    RAM: 6 GB
    HARD DISK: 40 GB

  • A 64-bit SQL Server (2008 and above) to host the Enterprise Commander's data with the following specification:

    CPU: 4
    RAM: 16 GB
    Database space autogrow should be set to 15% or more

STEP 2: Software Pre-Requisites

The Windows server will first need Java, .NET Framework and Application Request Routing 3.0 to be installed as per the Pre-requisite Software Installation page.

STEP 3: SQL Server Details

At this stage make sure you have the SQL server connection details for the existing Enterprise Commander database on our SQL server. The windows Enterprise Commander Manager application will need the following details:

  • Hostname
  • Port
  • Database Name
  • Username
  • Password

STEP 4: Enterprise Commander Installation

Once all the above pre-requisites have been set up you are ready to install Enterprise Commander on the Windows server. 

All your access configuration will be migrated, you should be able to log in with the account you previously used to log into Enterprise Commander.

STEP 5: DNS Name Migration

To preserve previous connectivity please re-allocate the DNS name used by the old Linux host Enterprise Commander server to the new Windows host. This will ensure that the Connectors connections and all requests go to the new Windows hosted server.

STEP 6: Testing for Successful Migration

Turn off the old Linux hosted Enterprise Commander Server and check the following.

  • Make sure the Connectors are syncing: You can do this by checking the last connected time stamp of the connector in Admin -> connectors page, they should not be more then a minute or two. 
  • Make sure you can navigate to the Enterprise Commander server DNS name from another computer. 

STEP 7: Decommissioning the old Linux hosted Enterprise Commander server

Once the above tests are successful, you should be good to delete/decommission the old Enterprise Commander server. 

Unable to render {include} The included page could not be found.