Thread Info
  • State Verified Answer
  • Locked Locked
  • Replies 8 replies
  • Subscribers 2 subscribers
  • Views 6587 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

unable to push sophos to server 2012

vospersIT

Good morning all

iv not been on in ages now but now have a problem im hoping you all can help me with.

we are deploying new 2012 r2 servers in our domain for some reason i cant protect them. i can do a manual install but there are so many going out i want to be able to push to them. i get error code 80070002 but i cant find this on the KB's. 

thanks guys

Kurt



This thread was automatically locked due to age.
Parents Reply Children
  • 0 in reply to vospersIT

    Hello Kurt,

    in case of 8-hex-digit error codes search for both hhhhhhhh and 0xhhhhhhhh [;)] But anyway, you should get two results searching for 80070002.

    You said manual install - did you access the share using the same credentials as for Protect Computers?

    Christian

  • 0 in reply to QC

    Hi Christian

    yes im using the same credentials to protect computers as i used to A) log in to the server B) run the setup.exe.

    iv done some poking around and found an error log of event ID 101 pointing me to look at the log on as batch on the server where SEC is installed. so eddied that and still noting.

    SEC is creating the task for the server to run but the server just never runs the task.

    kurt

  • 0 in reply to vospersIT

    Hello Kurt,

    IIRC SEC first creates the task and with a second command to the remote Task Scheduler starts it. I vaguely remember I have somehow monitored or traced the whole procedure.
    As usual with Windows errors one piece of information is missing, in this case the file name. Is the task still there in the endpoints (hard to find)? And whether or not, the Event Log -> Application Logs -> Task Scheduler has perhaps some useful information. It's very likely some setting or permission on the 2012 ....

    Christian

  • 0 in reply to QC

    Good morning Christian

    hope you had a good Christmas.

    so after a week off iv come back and started looking at this again and found the task is still sat in the task scheduler ?? 

    iv re pushed the task to the server and then checked event viewer to find an a logging error ?? its giving a 104 login failed and a 101 task failed to start.

     

    kurt.

  • 0 in reply to vospersIT

    Hello Kurt and thanks,

    as the task is still "sitting there", if you view its properties is the account it should run under correct - should be the one used with Protect Computers? There's a security setting which prevents storing credentials, but I've thought that task creation would fail when it's enabled. Please try to "change" the task and (re-)store the credentials - if this setting is enabled you should get an error.

    Christian

  • +1 in reply to QC

    Hi Christian

    Turns out iv just found out the problem. its to do with a default domain policy. the domain admins accounts dosnt have access to login as a batch on domain controllers hence the problem with logging on. so for now until we set up ether a new account for sophos install's or we add one of the sophos accounts already there i will have to do manual installs. pop goes my week.

Unfiltered HTML