Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 2 replies
  • Subscribers 1 subscriber
  • Views 1176 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Detecting if an error is a problem or just a software deployment issue.

kej

Hi,

 Is it possible to set up a data column for clients in Enterprise Console v4 that just lists software deployment statuses like "Reboot Needed", "Installation Failed" etc?

 I just did a bunch of upgrades and, not being quite used to the Enterprise Console v4.0 yet, it was a bit annoying to have to examine the reports machine by machine to try and work out if "Error" was a real issue or just a machine needing a reboot.

 Have fun,

 Keith

:1558


This thread was automatically locked due to age.
  • 0

    Hi, In the console looking at the tab: "Alert and Error Details" and then the columns: "Install Errors", "Update errors" should give an idea of deployment issues.

    The deployment process consists of the following steps:

    From SEC:

    1. "Protect Computers" action instructs the Sophos Management Service to connect to the machine and attempt to create a shceduled task on the machine to run setup.exe from the distribution share.  The management service needs to impersonate the account entered in the deployment wizard so the account you enter needs to be able to log on to the management service machine.

    If you have a problem with the management service creating the scheduled task, you can always run setup.exe on the client manually, please see: http://www.sophos.com/support/knowledgebase/article/12570.html for details on setup.exe.  One common approach is to create a startup script in AD such that as machines startup they will receive protection, something similar to: http://www.sophos.com/support/knowledgebase/article/13090.html

    2. Once setup.exe is running on the client it will install Sophos AutoUpdate.

    3. Based on the options selected, it will then pull down the packages, i.e. RMS, SAV, SCF, etc..

    4. Once the download sequence has completed, Sophos AutoUpdate (SAU) will start the install phase of each of the packages, starting with RMS so the machine soon appears as managed in Enterprise Console.

    As SAU is installing the packages as "System" the MSI install logs will be in the Windows Temp directory, so any problems with a package installing check the MSI logs in that directory.  The log names are obvious to the product.

    Hope this helps,

    Thanks

    :1559
  • 0

    The Alert an Error Details tab in the Endpoints view will show Restart needed ... in the Update errors column. Is this what you are looking for?

    Christian

    :1565