New setup - cant deploy to users - installation could not be started

view updating status is greyed out

i just browsed to the setup file from the end user pc to the sophos server and ran setup, entering my sophos username and password to get the updates (not sophosm active directory account)

i can view log file and it says

could not connect to the server - check that the computer is connected to the network and that sophos autoupdate is configured to update from the correct location with the correct credentials.... 

:(

Hello dalboy,

could not connect to the server

there might be a little bit more information in the preceding lines, so could you please post a few of them?

entering my sophos username and password 

I don't quite get which account my sophos username refers to - it should be the one used in the updating policies (which is by default pre-set to the SUM account - see User accounts required by Sophos Enterprise Console).

Christian

hi again QC

i am having trouble rolling out via the console so i am trying to do it the manual way:

end user pc browse to the setup file on the console server.  this i can do

the setup pops up with the option to uninstall 3rd party software and half way down asks for username and password to be used to get updates from the server if needed.  what details do i put in here?  i have an active directory sophos account called sophosm with password.  or do i use the username and password given my sophos for the software itself?

i tried using the sophosupdatemgr account in the console via protect computers but it says those credentials are invalid!?

again any help appreciated!

EDIT:  Right I think i am getting somewhere!

i entered the sophosm account in the setup box as above.  log says autoupdate finished and when i right click to update it says none are needed (done a reboot as well which the log stated to do)

So is that it?  will the end user pc now update itself automatically from my server?

the username and password which I used to type in to manually add sophos antivirus to standalone pcs (i.e. what they give you when you purchase the product) do i not need to enter this anywhere?

again thanks!

Hello dalboy,

good to hear it works.

To clarify - the credentials from your license schedule are only needed for downloading from Sophos. Normally you'd use these only on the Sources tab in Configure update manager. The only other instance where you'd need them is when you have clients which occasionally can't access your updating infrastructure and thus have to update from Sophos directly (note that per the license agreement this is permitted only for exceptional cases - if you have a significant number of clients which are routinely outside your network you should provide the means for them to update from your infrastructure; this could be e.g. a WebCID, or VPN to your site).

The CID (update location) on your server is "just" a (Windows/SMB) share, there is no magic involved. The account used must have the right to read from the share (and depending on your file server additionally the right to read from the file system). Thus it is (usually) a server-local or domain account - it has nothing to do with the credentials from your license.

In order for Protect computers to work you'd have to use an account with administrative rights on the target computer which can also access the share on the server for the initial install step (the equivalent of end user pc browse to the setup file on the console server). As the install runs in the background the console must set the parameters you'd enter in the pop up - the credentials are taken from the updating policy (this has recently been discussed in Initial install source help). With these it completes the installation.

As to standalone installations: The package provided is more a convenience - you can build your own - but it doesn't contain the management component and consequently these clients can't be managed from the console (you can include RMS if you build your own package). It is not required (and indeed, as said above, not encouraged) that these clients update from Sophos.   

HTH

Christian