<?xml version="1.0" encoding="ISO-8859-1"?>
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" />
<title></title>
<style type="text/css">
<!--
body{margin-left:10px;margin-right:10px;margin-top:10px;margin-bottom:10px;}
-->
</style>
</head>
<body marginleft="10" marginright="10" margintop="10" marginbottom="10">
<font face="Geneva" size="+0" color="#000000" style="font-family:Geneva;font-size:11pt;color:#000000;">Hello,<br />
<br />
We are using Sophos, however it is their Endpoint Security and Control Suite. In this configuration all the clients report to a central server, which means that every client installation has to be unique (the installer creates a unique ID on first install). If you do a simple snapshot to create the package the ID will not be unique on all of the Macs you distribute the package to which can cause issues with reporting and updating within Sophos. There are 2 ways to solve this: Remove the unique ID file before completing the snapshot package creation, or just use your custom .pkg installer. According to Sophos, they preferred us to use the .pkg. If you want to apply the custom .pkg installer while re-imaging you will have to create a new trigger that will specifically run the .pkg the next time the machine reboots after imaging. It doesn't work correctly unless you're booted off of the target hard drive. That is the methodology we are
using and it seems to work pretty well.<br />
<br />
<br />
<br />
<br />
</font><span style="background-color:#d0d0d0;"><font face="Geneva" size="-1" color="#000000" style="font-family:Geneva;font-size:9pt;color:#000000;">------------------------------<br />
<br />
Message: 8<br />
Date: Thu, 22 May 2008 10:44:42 -0700<br />
From: "mcorippo" <<a href="mailto:mcorippo@lblp.com">mcorippo@lblp.com</a>><br />
Subject: Re: [Casper] Sophos Intsall via Casper<br />
To: <a href="mailto:casper@list.jamfsoftware.com">casper@list.jamfsoftware.com</a><br />
Message-ID: <<a href="fcp://fc.006ad22901a3562c3b9aca004c6816cc.1a35ac8@lblp.com" target="_blank">fc.006ad22901a3562c3b9aca004c6816cc.1a35ac8@lblp.com</a>><br />
Content-Type: text/plain; charset=ISO-8859-1<br />
<br />
"Gene Anderson" <<a href="mailto:ganderson@phrd.ab.ca">ganderson@phrd.ab.ca</a>> writes:<br />
>"Dorey, Dustin" <<a href="mailto:Dustin.Dorey@district196.org">Dustin.Dorey@district196.org</a>> writes:<br />
>>I was curious how people are handling installing Sophos Anti Virus. <br />
>>What we are running into here is that it needs to run the installer to<br />
>>create a unique install on each machine. Any ideas, suggestions, or<br />
>>just let me know if I?m missing something glaring an I need to hang my<br />
>>head in shame. <br />
><br />
>We had just done a Composer snapshot of the install and the package seems<br />
>to work just fine. We're using version 4.9 of the Sophos client for Mac.<br />
><br />
><br />
Same for us (Composer snapshot), and it seems to be fine. On a previous image, we installed Sophos on the base OS image. Not as flexible, but worked OK as we would put Sophos on every box, and the config was<br />
always the same, so all we really lost was the option to easily uninstall.<br />
<br />
Thanks,<br />
Matt Corippo<br />
Lindamood-Bell Learning Processes<br />
<br />
<br />
<br />
------------------------------<br />
</font></span><font face="Geneva" size="+0" color="#000000" style="font-family:Geneva;font-size:11pt;color:#000000;"><br />
<br />
<br />
-------------------------------------------------------<br />
Quade Boman | Beaverton School District <br />
-------------------------------------------------------<br />
<br />
</font>
</body>
</html>