Thread Info
  • State Verified Answer
  • Locked Locked
  • Replies 12 replies
  • Subscribers 1 subscriber
  • Views 30029 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

0000003a - Installation involves creating a scheduled task on the computer. Windows 7

CarnabyERP

Hi I have just sucessfully deployed 5 Win 7 PC's remotely using SCC 4.0.

I now have one PC that is returning this message.

'0000003a - Installation involves creating a scheduled task on the computer. Access was denied when creating this task. The default admin share (called C$) may not be accessible or a required service may not be running.'

I have done as suggested in this link on the KB but no joy. Used several domain accuonts and even the domain admin accounts and that still does not work

http://www.sophos.com/support/knowledgebase/article/13063.html

Any ideas anyone?

C$ admin share is there and I am using the same domain admin account to deploy from SCC

Thanks

Andy

:1734


This thread was automatically locked due to age.
Parents
  • 0

    None of the above have fixed the issue for me. The site I've just built is a 2008 R2 server 64bit with purely windows 7 clients. These clients vary in that some are 32 bit but the issue remains the same throughout.

    There's very little logged to help with this other than the Sophos console (4.5.0.9) reports ffffffff awaiting response from computer. This is not due to the fact that the client cannot report back to the sophos console and more to do with the fact that the installation never took place and so therefore has nothing to commincate to the console with.

    All the GPO's are set as described in the multitude of sophos articles on the subject and even when I take a brutal approach the issue remains. I have in the past turned off all firewalls and UAC. the installation still doesn't take place automatically.

    I still feel this is a MSFT problem however. The task is created after deployment from the console but the task remains in a ready state (never running) until the timeout period removes the task, logging no events in the process(at least none that I can locate).

    SO this proves that the firewall is allowing comminication to the client and access has not been blocked by either firewall or permissions. If you click on the run button with the task selected it executes as it should have done AUTOMATICALLY. I've tried connections to and from the clients and all seems fine. Once installed the client and console perform well and reinstalls can be performed if required.

    Over around 150 machines this task failed on approximately 98% of the machines. 2% were fine. The only thing I could point the successes to is that these few laptops were also performing other remote installs as they booted up.

    I'm miserable now having looked at this for over 8months.

    Can anyone HELP

    :( 

    :14437
Reply
  • 0

    None of the above have fixed the issue for me. The site I've just built is a 2008 R2 server 64bit with purely windows 7 clients. These clients vary in that some are 32 bit but the issue remains the same throughout.

    There's very little logged to help with this other than the Sophos console (4.5.0.9) reports ffffffff awaiting response from computer. This is not due to the fact that the client cannot report back to the sophos console and more to do with the fact that the installation never took place and so therefore has nothing to commincate to the console with.

    All the GPO's are set as described in the multitude of sophos articles on the subject and even when I take a brutal approach the issue remains. I have in the past turned off all firewalls and UAC. the installation still doesn't take place automatically.

    I still feel this is a MSFT problem however. The task is created after deployment from the console but the task remains in a ready state (never running) until the timeout period removes the task, logging no events in the process(at least none that I can locate).

    SO this proves that the firewall is allowing comminication to the client and access has not been blocked by either firewall or permissions. If you click on the run button with the task selected it executes as it should have done AUTOMATICALLY. I've tried connections to and from the clients and all seems fine. Once installed the client and console perform well and reinstalls can be performed if required.

    Over around 150 machines this task failed on approximately 98% of the machines. 2% were fine. The only thing I could point the successes to is that these few laptops were also performing other remote installs as they booted up.

    I'm miserable now having looked at this for over 8months.

    Can anyone HELP

    :( 

    :14437
Children
No Data
Cookie Information Banner