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

Trouble doing manual installs (Endpoint Security) (Bootstrap Location Empty)

I'm having a hard time installing Endpoint Security manually and getting it to update (and import into a group).  I also notice that the Bootstrap Location is empty.  I'm getting too many mixed results on Windows XP (Sp2 and Sp3) workstations.  Some work, some don't.  What should I look for, and how can I get the bootstrap location populated?

:453


This thread was automatically locked due to age.
  • Hi,

    When you say you are doing manual installs I assume you are running setup.exe from the distribution share and you wish for the machine to become managed in Enterprise Console 4?

    The following article lists the switches to setup.exe and should be useful:   
    http://www.sophos.com/support/knowledgebase/article/12570.html

    As a quick way of capturing the install string.  If you protect a machine on your network from Enterprise Console, whilst monitoring the scheduled tasks directory on the client, as soon as the scheduled task appears you can rights click and look at the properties.  This is a quick way of getting a deployment string which already has an obfuscated username and password.  You can then add the -G switch on if you want the machine to appear automatically in the right group and the client to receive the policies of the group.  Remember that the path is case sensitive and must include the server name,

    I hope this helps

    Thanks.

    :454
  • That DEFINATELY helps.  This is the information I was looking for.

    :455
  • I used your trick to snag the Scheduled Task install string, and noticed that it used an undocumented command line parameter "-xp".  What does "-xp" do?

    Also, I tried removing "-s" to make it not silent, but it didn't seem to have an effect?

    Also, I'm not clear on the -ouser and -opass parameters.  Are they just credentials for a user account with read access to the \\<SOPHOS-SERVER>\SophosUpdate\ share? 

    Thanks!

    :1939

  • Scissor wrote:

    Also, I'm not clear on the -ouser and -opass parameters.  Are they just credentials for a user account with read access to the \\<SOPHOS-SERVER>\SophosUpdate\ share? 


    I can answer this one myself.  Those parameters are used for the AV Client's Update configuration under the Updating -> Configure Updating -> Primary Location tab -> User name and Password

    :1941