EM Library: how to evaluate on a test network before full deployment
Many companies evaluate a new version of Sophos
- The test version runs the 'Latest' EM package. This package is not published, thus only a local Central Installation Directory (CID) is present. The test computers run from that local CID.
- End users run a 'Fixed' version kept up to date with the latest IDE files. The 'Fixed' version is published over the network.
What to do
To set up a 'Fixed' version for publishing to production CIDs:
- Create and publish a customised package based upon a 'Fixed' version of Sophos
Anti-Virus , on the top parent library. - Describe it as "Master package".
- Create CIDs for end users to install and update from.
- Do not publish any other packages.
To set up an evaluation version for the test network:
- Subscribe to the 'Latest' Sophos
Anti-Virus package as well, but do not publish it. - Use it to populate a local CID for the test network so that the company can evaluate new versions before rolling them out across the organisation.
By doing this, the customer can ensure everyone uses just one version of software.
Updating:
- By changing the base package associated with the customised package, the administrator can decide when to switch from one fixed version to another.
- By basing the package upon 'Fixed' versions rather than the 'Latest' version, the end users will be kept up to date with all the IDEs for that version for up to three months without the executables changing.
Thus, manual changes to the packages need only be made every three months.
If you need more information or guidance, then please contact technical support.
- Article ID: 10258
- Created: 5 Jan 2004
- Last updated: 2 Oct 2008
