More on 3.0 Config Terminal

We have really spent a lot of time (way longer than expected) perfecting the terminal loading routines for 3.0. We had 2 main goals when we started this:

1. Make it super easy for someone to load and run it on their laptop or stand alone computer, anywhere on that machine.
2. Make it super easy (with nothing more to download and no jump drives) to stage all additional machines at the site.

By downloading the setup.msi from our website, you can easily load the software onto a laptop or server machine. The setup file has grown to about 80MB, but now essentially includes "setterm". Setterm, as you previously knew it, is gone. You can install onePOS anywhere on the machine, and a reference in the registry (HKEY_LOCAL_MACHINE\Software\onePOS\DefaultPath) to that installation directory lets the onePOS Applications without a onepos.cfg file know where to run.

To turn this machine into a "production" machine, navigate to where you installed onePOS (usually c:\onePOS) and then the Install folder. Run the ConfigTerminal application, indicating that this is terminal 1 (you have to have terminal 1 running before you load any other terminals) IP addresses, etc, and click OK. Ken is working on a document on the full ConfigTerminal application and routines, but basically this will load a "raw" XP or Win7 machine with onePOS, lock it down, and set it up to be a POS station.

The coolest part is loading terminals 2+ and the Manager Workstations. Windows File Sharing is not allowed, and jump drives are so 2006... so we created a simple webserver that will load the remote machines! You navigate on your terminal you are loading to http://:10001 and click the Click Here to Run the Installers link. The entire Install folder is zipped up on terminal 1, sent via http to the terminal, unzipped, and ConfigTerminal is run. You make the appropriate setting choices, click OK, and the terminal is reconfigured into a locked down onePOS terminal that is as PCI compliant as we can automatedly make it.