Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 4 replies
  • Subscribers 0 subscribers
  • Views 13076 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

Can pull but not push Sophos software

mysticole928

Running Sophos Enterprise Console: 5.2.0.644 in a Windows Domain environment.

When install manually by going to the share and running setup.exe, the install runs, connects, and updates correctly.

When I push an install (either as an upgrade or a fresh install), I get an error message saying that it can't connect to the console.  It tries, but it is using the clients local credentials.

It doesn't look as if it is getting the update policy correctly.  My primary server is a web based and, instead, it is grabbing the server's share and using the wrong credentials.

I can't find a default cedential schema anywhere.  It looks as if it might be trying to use the default software subscription's setup but I can't see how to change it.

I'm very frustrated.  Can someone help?

Stephen

:50900


This thread was automatically locked due to age.
  • 0

    Hello Stephen,

    please see the Initial Install Source tab in the updating policy - conveniently it comes with a detailed description (to add a brief explanation - setup.exe can only run from a UNC location).

    Christian

    :50916
  • 0

    I've seen that and I have the UNC path to the share.  Does it need to be more explicit than just the path?  Does it need to include the executable?

    Thanks!

    :50950
  • 0
    Hello Stephen,

    definitely not the executable, it is fixed. According to article 64639 it has to be the complete path though (down to SAVSCFXP).

    Christian
    :50960
  • 0

    So far, nothing's worked regarding pushing out the updates.

    I can pull them.  I can run the installer from the share without issue.  I've used the deployment tool to create both a large and small installer and that's worked as well.

    Looking at the error logs, the messages say that it needs a service to run (like remote registry, task manager, or windows installer) and I made sure they were all functional.

    I disabled the windows firewall on the client.

    I put the full path in that Updating Policy.  It worked once.  (when I added setup.exe)  However, it only worked once.

    Going to try again tomorrow.  Would love some advice.

    Stephen

    :50962
Unfiltered HTML