The Server Setups items on the Utilities Menu allow you to create or reset the INI files for CMD's optional servers, which enhance the feature set and usefulness of CMD. These two optional servers are software based, and run in the background on the computer that hosts CMD's data. A dedicated hardware server with a server OS is NOT required for either:

•Remote Database Server Software. This server software allows for more stable LAN connection to CMD's data, and also enables remote access where users can connect to live CMD data from an off-site computer.

•Web Server Software. This server software provides the connections necessary for CMD's phone and web apps to connect to your CMD data.

Both servers use an INI file which stores the necessary information to make the connection, and the setup dialogs provide an easy way for these INI files to be properly created and stored.

Remote Access for CMD and for CMD Web App

In order to make remote access of your CMD data work, either by CMD 2020 being setup on an off-site computer or through one of the CMD web apps, there are several things that you must do in your computer setup. They are not hard, but they are very specific. Here's what you will need to do:

1.You must have purchased either the Remote Database Server software (for remote connection of the CMD software) or the proprietary Web Server software (for accessing the CMD Web apps) from Software for Ministry.

2.The Remote Database Server software and/or the Web Server software is downloaded to and then installed on the computer that is hosting CMD's data.

3.The server software is then setup to run in the background on the host computer. Both servers have a small footprint, and the user of the host computer will not notice any performance hit for their activity in the background.

4.You must have either a static IP address that resolves to your router, or you must purchase a third-party DNS server that provides a domain name that resolves to your router (you cannot use your church's domain name for this. It must be a separate service). We suggest Dyn.com's basic-level service, which costs $25/year.

5.You must set the host computer to have a static IP address within your local network at the church.

6.You must set two port forwards in your router setup: Ports 12010 and 80 must be forwarded to the IP address of the host computer.

Once you have done these things, the remote access and/or web apps will be accessible. Hooking up clients and accessing the web apps is simple from that point on.

You will likely need our help in setting this up. We reserve the right to charge a modest fee for this service. If you need our help, you will need to have the following ready:

1.Create your own LogMeIn.com account and add all computers to it that we'll be working on. Generally, we need the host and at least one client. Hooking up clients is so simple, once you see it you will know how to set up the others.

2.We will need all the LogMeIn account information so that we can log in to your computers and do the setup.

3.We will need the information on how to access your router's setup program, which includes method of getting to it and the user name and password for it.

4.If your church does not have a static IP address, then you will need to have set up an account with Dyn.Com for their most basic service.

Once you have those things done, contact us for an appointment to help you get it set up.

If you cannot get your remote connection or web server to give you access to the CMD Phone App, click here.