Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 8 replies
  • Subscribers 1 subscriber
  • Views 2509 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

Enterprise Console 4.0 - Several Questions

lump

Hi all,

this is my first post here. Please dont judge my english, im from germany.
Hope i get some help from you guys here.  :smileywink:

I have to take over the Sophos administration in our company. Im not completly new to the Console 4.0 Frontend, but ive got a few questions.

1.There is an install path called  \InterChk\ESXP and \InterChk\ESOSX. The installation files for Windows AV client and OSX Client are placed here. The OSX folder is not important, iam working in a Windows environment.

When i start a setup from the folder ESXP it will install version 7.6, but the latest version is 9 at least what i know. Question is, can i simply replace the Files in the ESXP Folder with install Files from savw_90_sa_sfx.exe which i can download from the sophos site?

2.When i open EM-Libraray i can see that two Packages are subscribed. The first one is called
Sophos Anti-Virus for Windows v7.6.19 VDL4.53E
and the second one
Sophos Anti-Virus for Mac OS X v4.9.34.

Are these packages the update files(SAV+IDEs) or the Client Full Installation files? And if so, why do they still thave the version number 7.6?

So far these are the first two questions, but im sure those wont be be the last.

Thanks for any help

lump

:2622


This thread was automatically locked due to age.
Parents
  • 0

    Hi,

    The best test you can perform that most closely emulates what Enterprise Console is doing to protect a machine is:

    1. Log on to the Sophos Management Server machine as the account you are specifying in the deployment wizard.  This needs to be able to log on to the management server machine and be an admin account on the remote client you are protecting.

    2. type \\<remoteclientNETBIOSname>\

    where:

    <remoteclientNETBIOSname> is the name of one of the machines you are trying to protect.

    3. Go into the "scheduled tasks" folder, right click and attempt to create a scheduled task.

    From the error you received, it sounds like:

    \\remotemachinename\

    would also fail?

    Don't forget you can always just run setup.exe from the distribution share to install Sophos on the client as per:

    http://www.sophos.com/support/knowledgebase/article/12570.html

    So psexec, AD start-up scripts and such can all be used to trigger the install if you need to.

    The easiest way I find to get a deployment string with the obfuscated user name and password is to protect a machine and monitor the scheduled tasks folder on that client (%windir%\tasks"), Once Enterprise Console creates the task you can copy the deployment string from it.

    Good luck

    Jak

    :3170
Reply
  • 0

    Hi,

    The best test you can perform that most closely emulates what Enterprise Console is doing to protect a machine is:

    1. Log on to the Sophos Management Server machine as the account you are specifying in the deployment wizard.  This needs to be able to log on to the management server machine and be an admin account on the remote client you are protecting.

    2. type \\<remoteclientNETBIOSname>\

    where:

    <remoteclientNETBIOSname> is the name of one of the machines you are trying to protect.

    3. Go into the "scheduled tasks" folder, right click and attempt to create a scheduled task.

    From the error you received, it sounds like:

    \\remotemachinename\

    would also fail?

    Don't forget you can always just run setup.exe from the distribution share to install Sophos on the client as per:

    http://www.sophos.com/support/knowledgebase/article/12570.html

    So psexec, AD start-up scripts and such can all be used to trigger the install if you need to.

    The easiest way I find to get a deployment string with the obfuscated user name and password is to protect a machine and monitor the scheduled tasks folder on that client (%windir%\tasks"), Once Enterprise Console creates the task you can copy the deployment string from it.

    Good luck

    Jak

    :3170
Children
No Data