This is a brief overview of the system setup and path setup of the Candy system.
Candy is designed to install and run on workstations that are running Microsoft operating systems such as Windows XP or Windows Server.
Newer operating systems are preferable. Latest service packs should be installed (within reason).
Additionally, workstations require a reasonable amount of available ram over and above what is required to run the operating system, virus checker and email package.
Candy expects each user to be setup with a profile as specified by Microsoft.
Candy does not run ‘server side’ software. However, the Candy application can be installed on an application server and accessed using a shortcut via a LAN. Requirements here are the same as for any other application that needs to be run from a server.
Candy data can be accessed on a file server. The server load, hard drive speed and network speed are all factors that will affect performance. Candy accesses its data files continuously – any interruption in this process will cause major problems.
Cache settings or third party cache software and other performance enhancing software running on the server can cause problems. Virus checkers that delay the open and closing of a file can also cause Candy to fail.
“LAN” speeds are expected where Candy is running on a network except in virtual desktop environments (ie Microsoft Terminal Services or Citrix).
The SETUP.EXE program helps with the installation, but it is not required. For example, the system could be installed on a test machine and then the entire Candy application folder can be copied onto another machine.
To unpack the system files without the setup interface make use of the following from a command line or batch program:
…\setup.exe SILENT=[install path]
Note that there are no spaces around the “=” sign and SILENT is in upper case. [install path] may be in UNC form, can have spaces and is not enclosed in quotes.
It is not necessary to uninstall Candy files before re-installing the application.
The system can be installed in any folder. The preferred folder is C:\PROGRAM FILES\CCSWIN. Many different versions of Candy can be installed on the same machine if required. The system can be run over a network from a mapped or UNC share.
No files are installed outside of the specified system folder. No Windows DLLs are replaced. No critical registry settings are changed.
A shortcut to the file …\ccswin\system\ccsvfx.exe is required to start Candy. No “start in” path is required as Candy relies on the user’s profile (…\my documents) to determine user preferences and to determine where data is located.
Each user must have access to a “MY DOCUMENTS” folder. When Candy loads it will ask Windows for the user’s profile path – here it will expect to find a ...\My documents\MY CCS folder (or similar). If it does not find a folder then one will be created.
Most importantly user data paths are stored in the MY CCS folder. Additionally, colours, fonts, document positions and sizes are stored here. User’s reports and document column settings are also stored here.
No actual user data is stored at MY CCS, however, users do invest quite a bit of time setting up their documents and reports – because of this the MY CCS folder must be migrated with the users profile when moving to a new machine.
Note: The current trend is to place user profiles onto a network drive. The Candy application has no problem with this. However, Candy requires continuous access to the MY CCS folder – failure to provide this will result in a situation in which the user will not be able to work.
A user can have many preferred data paths. An obvious default path would be [user profile path]\my documents\ccsdata.
These paths can also be mapped or UNC paths to network shared folders.
The list of available data paths is stored in a file that is located in the MY CCS folder.
The user must have full read/write/modify rights to any data path. Additionally, connectivity must be guaranteed – Candy accesses its data files continually – if the connection to a data path is lost once the user has entered a Candy “job” then serious data corruption could occur.
Note: Candy is designed to recover from sudden shut downs (either power failures or network connectivity loss). However, Candy cannot recover from intermittent connectivity problems.
The licence can be installed centrally or locally.
Local installations – the licence file will be corrupted when a profile is migrated. The correct procedure is to phone CCS before migrating the profile.
Network installations – This type of licence is expected to be installed on a local file server. Except in the case of a virtual desktop environment, the licence is not allowed to be installed on a server that is to be accessed via a WAN. The licence is checked periodically while a user is working – failure to provide a fast and guaranteed connection to the licence will make Candy unusable.
Candy data files are proprietary. Because of this it is not possible to transmit viruses via these files. Naturally any attempts to store viruses inside a Candy data file will render them corrupted.
Due to problems with virus checkers it is suggested that the Candy data area be specifically excluded from virus checks.
The Candy setup.exe and installed .exe and .dll files are certified by Thawte Certification Authority (https://www.thawte.com).
Candy data should not be placed in a folder that makes use of any type of synchronization. This includes the MS Windows Offline Folder facility.
Candy will work with Citrix and MS Remote Desktop/Terminal Services.