Overview of Enterprise Migration:
from One Windows Server to Another

Important Note: You may require further consultation on the content of this document. You may not have the in-house expertise or the time to apply the instructions included with this document. Either way, Tecsys can help: just contact our support team at SMBSupport@Tecsys.com with a brief description of your issue(s) and one of our technical specialists will contact you directly.


  • If our EDI products (Cleo and PROEDI) are being used, then our EDI Group must be advised before the move. Proper shutdown and restart of EDI as well as software installation will be required.

  • Gather information on both servers, old and new. Server names and IP addresses will be required. Make note of file shares and their permissions.

  • Identify all applications that access Enterprise data via file shares.

  • Check Printer configurations for any server based printers, especially dot matrix printers.


  1. Install and activate ProvideX on the new server.

  2. Copy the Enterprise install to the new server and setup the required file shares.

  3. Make adjustments to the Enterprise configuration.

  4. Update Enterprise icons on the workstations.

  5. Correct printer configurations as necessary.

The installation and activation of ProvideX must be done by Tecsys staff. This can be done before or after the Enterprise migration.

The customer or technician may perform the copy as it can be very time consuming.

Adjustments to the Enterprise configuration are usually performed by Tecsys staff.

Tecsys staff will usually assist with the first one or two workstation changes and the customer or technician completes the rest.

Copy of Enterprise:

  • Ensure that nobody accesses the Enterprise files during the copy process. (Stop Replication, Cleo, E-Sales, Radio Beacon or any other task that updates Enterprise files.)

  • Have everyone exit Enterprise.

  • Reboot the old Enterprise server and stop the NTHOST program. (Remove the NTHOST from the Start Up Group on the old server to ensure that it does not restart.)

  • If a copy of Enterprise already exists on the new server, rename or erase it.

  • Copy the "\0" (usually "C:\0") directory from the old server to the new one. (The destination drive does not have to have the same drive letter.)

  • Once the copy is completed, check the file and byte counts on both servers to ensure that EVERYTHING got copied. This is most important. (Use the actual file size and NOT the "size on disk".)

  • Set up Enterprise file shares on the new server.

When the copy is complete there will be two identical copies of Enterprise. It is very important to prevent users from accessing information on the old Enterprise server. Any information processed by the old server after this point will be lost. Remove the NTHOST from the Startup group on the old server and ensure that is does not get started from this point on. Also, disable the "odbcdata" file share to ensure nobody runs Crystal Reports against the old server. It would be best to disable all Enterprise related file shares on the old server.

Adjust Enterprise settings:

The following changes must be made if the server name has changed:

  • Run 00LU02 and update each field containing the old server name. If the install drive changes also update fields containing the drive letter.

  • From the live company run CC84 and rebuild the WinSol_ODBC.ini files.

On the Workstations the following steps must be performed:

  • Update the Target Field on the Enterprise icon to reflect changes in IP address and file location. (There are at least two icons, one the desktop and one in the Enterprise Group.)

  • Update the ODBC/DSN information. (The Enterprise_ODBC.ini files on the server must be updated first.)

Printer considerations:

  • Printers may be an issue if the Enterprise server is also a print server. Printers hosted on the old server and moved to the new one may require each to be removed and re-installed on each of the workstations. Using CC97, Enterprise printer links may have to be updated. Special printers, such as large dot matrix printers that are configured on the Enterprise server only will have to be installed on the new Enterprise server and their links updated from the server's console.

  • The Enterprise printer links, or ProvideX Device Link Files, are stored under the client directory. (For example: c:\0\client_id\ )