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

installed enterprise console 5.2.2 fresh install in a server, workgroup PCs are not getting update

sanjit

PCs are that within the domain are getting the updates but not the ones that are in the workgroup. Console does find the PCs though. The PC can ping the server where the console is  and user name and password is correct to for sophos update manager user but still can not connect.

Sophos support has been looking into for last two weeks. Any help from forum would be great.

:53801


This thread was automatically locked due to age.
  • 0

    Hello sanjit,

    how did you install on the workgroup PCs? With a package or running setup.exe from the CID?

    PC can ping the server

    Is the updating policy correct on the workgropup PCs? Ping is IMO overvalued, all it shows is there is a path to the server and, if you're using a name, that name resolution works. Instead you should browse to the share or map it to a drive (using the updating credentials and the path from the policy) - does this work?

    user name and password is correct

    Where did you enter them? Did you test them by accessing the server share from a workgroup PC (see above)?

    Console does find the PCs

    What is find in this context? Any of the Discover methods or did the PCs "appear" in the console after install?

    not getting update [...] can not connect

    What does the updating log say, what exactly is the error (can not connect is rather vague)? Sometimes the error report is rather general and it's necessary to inspect the more detailed ALUpdate logs.

    Christian

    :53805