This document lists the steps needed to update the site URL for both Genus G1 and G2 clocks.
Rule of Thumb:
In order to update the information on both clocks, a physical and/or remote connection is required. For Clocks on a private network, Support associates will need to start a remote screen share connection with you to connect to a computer that is confirmed to be on the same network as the clock. (This allows for the ability to run tftp and general shell commands to reach the clock. Without the computer being connected to the same network as the clock, the commands will not be able to run)Once the remote session is established, a connection to the clock(s) can be made.
The primary commands to be used to connect to the clock(s) are the tftp commands which use the tftp protocol to transfer files to and from the Genus clocks with the corresponding computer. Best practice is to either create, or transfer a folder containing the tftp.exe file, which will allow for the windows command terminal to recognize the commands themselves (I recommend transferring this folder on to the computer's desktop for ease of use).
Once confirmed, open a command terminal and navigate to the path of the tftp.exe file using the CD command displayed below:
cd pathoffolder/foldername
Once in, the next step is to run the ping command to ensure you are able to reach the clock from the network of the computer you are remoted into. The results should look like the following:
From there, you should be ready to pull the eems.properties file that houses the URL used to access the site. In order to pull the file, run the following command:
tftp -i 0.0.0.0 GET \ramdisk\etc\eems.properties eems.properties
This command should transfer the eems.properties file to the folder or file path you are shell'd into and should look like the following:
From there, you will need to right-click on the file, navigate to the properties of the file, uncheck the "read-only" box and "Apply" to allow for editing.
Next, open the file and scroll or ctrl +F for "EEMS_SERVER_URL" (You should see the following script:
Simply change the "ghg.com" to "teamkeeper.com" in the URL and save the file.
Next, you will need to send the file back to the clock by running the following:
"tftp -i 0.0.0.0 PUT eems.properties \ramdisk\etc\eems.properties"
Next, you will next need to reboot the clock unplugging an plugging the power cord or POE cable back in. You can also reboot the clocks by using the following telnet commands:
Telnet 0.0.0.0 9999
This command will prompt you to enter "Setup Mode"
From there, you will need to type "9" and then enter to reboot the clock remotely
Done!
COMMON ISSUES:
There are times when running the tftp commands, the commands will time out instead of giving you a transfer confirmation. If this happens, check the spelling and order of your command to ensure it was run correctly.
Additionally, there may be a restriction on the local firewall that may block UDP connections on port 69. Ensure that this is either allowed or temporarily turn off the firewall, run the commands, then turn the firewall back on in order to proceed.
Another potentially avenue for issues can stem from the other web related settings in the offline mode of the clocks. If the issue persists past the above changes, please check the physical clock's settings to ensure, "web host services" and "tadmin" settings are turned off. These can both interfere with transferring files to and from the clocks at times.
Support:
For any issues with the commands timing out or need of assistance with this process, please reach out to Support Services at 866-380-4146 ext. 2 or support@teamkeeper.com