Candy can be accessed from a server using Citrix XenApp. To use this this feature you must first Install Candy as you would on a normal workstation.
1. Download a standard version of Candy from www.ccssa.com\version2
2. You can run this as is – it will ask for an install path. To install without the interface and to avoid a shortcut being created on your admin desktop you can run it from a command prompt:
…\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.
For example: C:\download\setup.exe SILENT=C:\CCSWIN
3. That CCSWIN folder can now be copied to your application server’s program files folder.
On a normal PC a shortcut would be created and would point to c:\program files\ccswin\system\ccsvfx.exe.
When executed the Candy splash box will appear while the main application loads.
Once loaded it will detect that this user profile has not accessed Candy before and ask for the user’s name.
The user profile MY DOCUMENTS is used to store user settings in a folder called MY CCS. A default data path is created in the user profile MY DOCUMENTS and is named CCSDATA.
In a virtual desktop environment this should work in exactly the same way.
Start the Publish Application wizard in XenApp.
For the purposes of this example don’t set the streaming options on. As a side note Candy will work as a streamed application, the complexity is in making the candy licence work – this is separate to the application.
Browse or type in the Candy program path – quotes are required is the path contains spaces:
The working directory must remain blank.
Add the Candy application to as many servers as required. NOTE that Candy does not install or replace any files outside of its own program folder. It does make use of many Windows DLLs and will expect them to be available on each server. In other words, Candy will not interfere with other applications, but could suffer if other applications have made odd changes to standard Windows DLLS.
Make sure that the correct users are allowed to access the Candy application.
Suggest that a shortcut be placed on the users virtual desktop.
The limits screen can be used to limit the number of users that will simultaneously be using Candy. NOTE that Candy cannot run without a Candy licence. This mechanism will restrict the number of users running at the same time. We suggest that the Citrix limit option below is left unchecked. However, the users “usage” of a one licence is released at critical points in Candy ie flipping from one estimate to another – it is possible to effectively “loose” access due to the fact that another user has managed to slip in and take up the last simultaneous licence. By setting a limit on the application this can be avoided as the original user will be blocking any other users. In this case the Candy licence count and the instance limit must be kept in sync.
Candy will prevent multiple instances from loading, but for the sake of efficiency it is suggested that a user only be able to open one instance of Candy.
Candy is designed to give users a fast and detailed experience – aimed at speeding the tender process. Under no circumstances should Candy be given a below average priority level.
Candy does not make use of sound as part of its primary interface – we suggest unticking the “enable legacy audio” option.
We suggest that encryption be left as Basic.
Leave the printing option checked – Candy does not query printer drivers at startup.
Candy is designed to work within in a MINIMUM of 1024x768. For the type of spreadsheet and planning work a bigger environment size is essential. However, obviously there are limits in a virtual desktop environment – this needs to be discussed with end users.
Colour- Candy will attempt to downgrade features in a low colour (256) environment – this does not make for a very good working experience. 16 bit colour is acceptable, True colour is better.