CROSS-Client Software Depot_Allg_en_29062010
1 Overview 3 2 System Requirements 4 3 Installation 5 4 Updater Service Configuration 7 5 Updater Logging Service 8 6 Copying Client software into the depot 9 7 Administration 10 7.1 Proxy configuration 10 2
Overview 1 1 Overview A Client Software Depot provides centralised storage for C2Client versions. CROSS2 Client software allows you to specify up to 2 so-called Software depots (for more information see Entries in c2client.ini), which are sequentially searched for the required software version, if the necessary version is not installed on the workplace. If the version is found in a defined software depot, it is automatically downloaded to the Client and installed. This mechanism means that new Client versions can be centrally made available on a server and do not need to be individually installed on workplaces. Software depots can make the Client versions available via a file share or a virtual directory of a webserver. CROSS2 Client versions can either be manually installed in a software depot or a Windows service can be installed, which synchronises a software depot with a centralised software depot. 3
System Requirements 2 2 System Requirements Windows Server 2003 IIS 6.0 Is necessary if the client versions of the depot are to be made available via a webserver. If they are to be made available via filesharing, this component is unnecessary..net Runtime 2.0 (free download from Microsoft Downloadcenter) Windows Service user account A Windows Service user account is needed for the synchronisation service for automatic synchronisation of a software depot with a central software depot. This user account requires the rights needed for read access for the file share / the webserver of the central software depot. If a Software Depot is used, CROSS Client software users must have read rights for the file shares / webserver of the software depots configured on the client. 4
Installation 3 3 Installation A software depot requires.net-runtime 2.0, which must be installed separately. Use the c2clientswdepot.exe program for the installation of software depots. 5
Installation 3 The target directory specifies where the concerned CROSS2 Client versions are stored. This directory must be made available as either a file share or a virtual directory on a webserver after installation of the software depot. Optionally a Windows service can be installed, which automatically synchronises the software depot with a centralised software depot (in this example http://c2updateserver/client). 6
Updater Service Configuration 4 4 Updater Service Configuration In the C2ClientSoftwareUpdater.ini file (<installation directory>\bin) the follwoing settings are available under [Settings]. UpdateServer Specifies the path to a centralised software depot with which the local software depot is to be synchronised. e.g.: UpdateServer=http://centralswdepot/client or UpdateServer=\\centralswdepot\client PollingInterval Specifies the intervals in which the service is to check the centralised software depot for changes (in minutes). KeepLogFiles Specifies how long archived log files are to be kept (in days). The log file of the Updater service (<installation directory>\logs) is automatically archived when it reaches a seize of 1MB. 7
Updater Logging Service 5 5 Updater Logging Service The Updater Logging Service allows central logging of all download activities of local updater services. System Requirements Windows Server 2003 Internet Information Server (IIS) Installation The Updater Logging Service can be installed using the swupdaterlogger.exe installer. Configuration In the swupdaterlogger.ini configuration file (in the Updater Logging Service installation directory) the following settings are available. rollsizekb= Specifies the maximum size of the log file (in kilobytes). When this size is reached, the log file is saved to a new file and then emptied. loglevel= Available values are "normal" and "verbose". "normal" loges the start and end as well as any download errors that occurred. "verbose" means that the local local Updater Services additionally log their configuration data and local Client versions. 8
Copying Client software into the depot 6 6 Copying Client software into the depot The C2CLIENTSOFTWAREDEPOT=TRUE parameter tells the CROSS2 Client installation program that it should not install the Client software, but copy the program files in it into the software depot. e.g.: c2client-x.xx.xxxx.xxxx.exe C2CLIENTSOFTWAREDEPOT=TRUE 9
Administration 7 7 Administration If the Software Updater service is not installed during the installation of the software depot, then the depot must be manually administered. Client versions are installed as described in Copying Client software into the depot [ 9]. Versions that are no longer needed can be deleted using the C2SWDepotAdmin.exe (<installation directory> \bin) tool. C2SWDepotAdmin.exe can also be accessed via the /keep=<noofversions> command line parameter. Thereby all old versions are deleted and only the amount of recent versions specified in the <noofversions> are kept. e.g.: C2SWDepotAdmin.exe /keep=3 Deletes every version except the most recent 3 versions. The above access could be regularly accessed as a "Scheduled Task", to prevent the software depot from filling up with old versions. 7.1 Proxy configuration If a proxy server is used, you can configure it as follows: 1. Run C2SWDepotAdmin.exe (<installdir>\bin). 2. Click on Settings. 10
Administration Proxy configuration 7 3. Input the necessary data in the Proxy area. If authentication is required, log in. 4. Click on OK, to save your input. 5. Start the C2Client-SoftwareUpdater service via the Windows control panel (Settings -Control panel - Administrative tools Services). 11