Updates, support and license validation make use of Candy servers.
Updating Candy requires the download of a 20MB setup.exe file.
Access to these servers is not mandatory, however it is recommended to keep Candy up to date, avoid telephone calls for license validation and managing errors/support efficiently.
All Candy services use the HTTP protocol. If the appropriate websites are placed in a whitelist, Candy’s services will work using port 80.
Note: Under no circumstances is user DATA sent to CCS servers. Candy jobs can be backed up and sent to support via email on user instruction.
Validation of licences and system extensions are done via a connection to the following URL:
Candy needs access to http://www.ccssa.com to read the current available version.
The actual setup.exe file is downloaded from one of the following (depending on the user’s server choice):
http://ccshosts.com (South Africa server)
http://ccs.fileburst.com (International file sharing server)
http://www.candytech.co.uk (United Kingdom server)
Candy can be downloaded from South Africa, UK and US – please see the following web site to try the different options.
The UPDATE CANDY tool offers this web site (“Download using default browser”) or a direct download (“Download latest software”).
QTO 2 Connects to http://www.candyws.com/CandyQTOReg/TheUpdateService.asmx which is a web-service.
QTO 2 downloads updates from http://register.ccsqto.com
QTO 3 downloads updates from https://candyproject.co.za/
Error information and other licence information is set via web service to the following server. This is not a pre-requisite to running Candy, however blocked access to this will increase support and licensing turnaround times.
This makes use of web services that reside at:
The candy webs site is at the following URL: