CommuniGate Pro Installation
Note:your should use the Services control panel to verify or change the Log On as name for the CommuniGate Pro service. That name should have the Act as part of the operating system Windows NT privilege. If the CommuniGate Pro Server does not have this privilege, not only it will fail to authenticate users using the Windows NT password system, but an attempt to use an incorrect password may cause the server to crash. This problem is fixed in the Windows NT Service Pack 4.
Note:if your server should serve 100 accounts or more, check the description of the TIME_WAIT problem and follow the instructions to decrease the NT TIME_WAIT time interval.
Note:Unlike Windows 98, the Windows 95 system does not have the "WinSock2" libarary installed. Download this library (.dll) from the http://www.microsoft.com and install it before you try to launch the CommuniGate Pro Server.
You can also start the CommuniGate Pro server manually, as a "console application", by launching the CGServer.exe file. If started without parameters, the Server creates the C:\CommuniGatePro folder and uses it as its "base" folder". If you want to use any other location, use the --Base command line parameter:
CGServer.exe --Base D:\OtherDirectory
The base directory and all its files are not modified when you update the CommuniGate Pro Server software, so all accounts, mailboxes, messages, settings, Personal Web Sites, customized WebUser and WebAdmin files stay and continue to work with the new version of the Server.
Note: if you chose to manually modify WebUser and/or WebAdmin files right in the application directory, then you should save them before updating. If you properly placed your customized versions of WebUser and/or WebAdmin files into the Domain Webuser/WebAdmin directories, these customized files are not removed when you upgrade the Server software.
CommuniGate Pro keeps all its data in the base directory. This is the only directory you need to copy to your new server computer.
CommuniGate Pro uses the same file formats on all hardware and software (OS) platforms, so usually you can just pack the entire CommuniGate Pro base directory into an archive file (using tar and gzip on Unix systems, zip on MS Windows systems), and unpack the archive on the new server computer.
Additional processing is needed when you move the CommuniGate Pro Server from a computer
running any MS Windows operating system to a computer running any flavor of Unix, or vice versa.
CommuniGate Pro files are text files, and text files on MS Windows and Unix have
different EOL (end of line) symbols: CR-LF (return - linefeed) on MS Windows and bare LF (linefeed)
symbol on Unix systems. To copy files properly, you may want to use any FTP software to copy
files between those systems: when an FTP client is instructed to transfer files in the ASCII
mode, it properly converts EOL symbols.
Note: CommuniGate Pro base directory can contain non-text (binary) files in the WebUser and WebAdmin directories inside the Account and Domains subdirectories - graphic files used in the customized WebUser and WebAdmin Interfaces. Binary files can also be stored in Personal Web Sites - account.web directories inside the account directories. When you move a CommuniGate Pro base directory between systems using different EOL conventions, check that those binary files are copied in the BINARY mode (i.e. without EOL recoding).
If the new server computer is running a Unix system, check that the copied directory and all its files and subdirectories have the same access rights as they had on the old system.
After the CommuniGate Pro base directory is copied, download and install the proper version of the CommuniGate Pro Server on the new server computer. There is no need to copy the content of application directory from the old server computer, even if both new and old computers are running the same operating system.
Check that the newly installed copy of the CommuniGate Pro Server (its startup script, if any) is configured to use the copied base directory, and then start the CommuniGate Pro Server on the new computer. Use the WebAdmin Interface to modify the computer-related settings on the new server. For example, you may need to update the Client IP Addresses table or re-assign IP addresses to CommuniGate Pro Domains.