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

Deploy Sophos to PC which is logon by non administrative users...

Uncle_Ben

Hi ALL,

Currently we are trying to deploy the sophos endpoint to the remote clients which in a separated workgroup and all login with a non administrative accounts. Even I used a local administrator account during the IP range scanning & Protect Computer wizard, it still show the "0000002e" error code. Most likely the installation schedule cannot be added to the PC task... does anyone facing the similar case? And any suggestion / advise? Thanks for your help !!

:4349


This thread was automatically locked due to age.
  • 0

    Hello Uncle_Ben,

    the easiest way would be to do a manual install from the CID or from a copy of the CID on a stick.

    Is the number of PCs suitable for this approach? Of course, the setup needs to be executed from the local administrator or via a runas-command which gives the setup-process the administrative right.

    Best regards,

    Detlev

    :4351
  • 0

    Detlev, thanks for your kindly advise! This approach is my last work out... as we have over 200 remote clients and some of the outlets take a long distance from the HQ. Thus, I would prefer a pushing approach from the Console via the VPN connection if possible. Does there any other workaround besides the local manual installation?

    Besides, I tried to copy the whole SophosUpdate folder to a remote server and shared the folder to everyone just like the one in Enterprise Console. And then I modified the 'Updaing Policy' for a group in which the Initial Install Source is pointing to that new shared folder. However, the clients that moved into this group doesn't install the sophos client as expected..... it seems that this approach is not working....  I found 2 common case: (1) The installation just started and keep showing the status is in progress but never end. (2) Even the installation is completed, the update status is failed and I found that the Primary Update Source is pointing to the initial install source (not the one I set as desired primary updatge source).    Anyone know what's the magic inside? Any hints about how to use a different intial install source for the remote client installation but keep the primary update source from the central one in local (HQ)?

    Many thanks for any help!!  :smileytongue:

    :4358
  • 0

    Hi Uncle_Ben,

    you can configure the primary installation source in the update policy which is assigned to the group in which the computer resides. This location is independent from the primary and secondary source.

    Best regards,

    Detlev

    :4384
  • 0

    As I said, I configured the different location for the Initial Install Source but it just failed and keep waiting for a long time... Anyway, I used a cmd line for the automatic installation with some parameter that force the client to install the program from the desired local server and then update from the remote primary update server. It works fine~  :smileyhappy:

    :4457
Unfiltered HTML