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
    For those of you whose problem was not fixed by the suggestion above:
    This can also happen if the machine in question was at one point infected with the conficker virus.  There are some changes that the virus made to some machines that aren't fixed when the virus is cleaned off of the machine.
    One of the things Conficker did was change the permissions for task creation on the local machine.  You can fiix this by running a batch file with these lines in it on the machine that may have been infected:

    cacls c:\windows\tasks /T /E /P Administrators:F
    cacls c:\windows\tasks /T /E /P SYSTEM:F

    Once you run this batch file try to create your own scheduled task.  If it lets you create one you have fixed the issue. However, that tells you that the machine was indeed infected.  If that is the case you should also check out these other things"

    Verify that the following services are started:
       - Automatic Updates (wuauserv)
       - Background Intelligent Transfer Service (BITS)
       - Windows Defender (windefend) (if applicable)
       - Windows Error Reporting Service

    I got all of this info from other forums talking about conficker.  None of these solutions are my own but were provided by other helpful people.

    Good Luck,

    Paul

    :12443
Reply
  • 0
    For those of you whose problem was not fixed by the suggestion above:
    This can also happen if the machine in question was at one point infected with the conficker virus.  There are some changes that the virus made to some machines that aren't fixed when the virus is cleaned off of the machine.
    One of the things Conficker did was change the permissions for task creation on the local machine.  You can fiix this by running a batch file with these lines in it on the machine that may have been infected:

    cacls c:\windows\tasks /T /E /P Administrators:F
    cacls c:\windows\tasks /T /E /P SYSTEM:F

    Once you run this batch file try to create your own scheduled task.  If it lets you create one you have fixed the issue. However, that tells you that the machine was indeed infected.  If that is the case you should also check out these other things"

    Verify that the following services are started:
       - Automatic Updates (wuauserv)
       - Background Intelligent Transfer Service (BITS)
       - Windows Defender (windefend) (if applicable)
       - Windows Error Reporting Service

    I got all of this info from other forums talking about conficker.  None of these solutions are my own but were provided by other helpful people.

    Good Luck,

    Paul

    :12443
Children
No Data
Cookie Information Banner