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

Gnarly install issue

I'm running into an install issue when using "Protect Computers" to install Sophos on new clients. The management console and server are on Windows 2003. The new clients are XP. We were able to use Protect Computers in the past on these clients, but something's changed...

We are now getting the dreaded error 00000034 back from the client whenever we try to "Protect Computers". If I log in to the client using the credentials given in the Protect Computers wizard, I can browse to the install location fine, and I can even install Sophos on the client manually from that location. Share permissions and NTFS permissions all look fine.

The potential issue here is that this is all going on on a DoD classified network, so it's possible that one of the security settings set by the GPO is blocking things somehow. But I'm stymied by not knowing just how Sophos is attempting the install, and also by the fact that there are no other warnings or errors popping up (nothing in the Sophos logs, and nothing in the Security events log).

Any ideas on this would be quite welcome. Sophos is running fine on our unclassified network, it's just on the secure one that we are having issues.

:16013


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

    The management service just creates a scheduled task on the client to run setup.exe with a number of switches.  You could check the properties of the task as it's created are as they should be.  Maybe copy the command line out of the task properties and manually run that, does it work when run as the deployment account on the client?

    Regards,

    Jak 

    :16015
Reply
  • Hi,

    The management service just creates a scheduled task on the client to run setup.exe with a number of switches.  You could check the properties of the task as it's created are as they should be.  Maybe copy the command line out of the task properties and manually run that, does it work when run as the deployment account on the client?

    Regards,

    Jak 

    :16015
Children
No Data