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

    Hello Andy,

    couldn't evoke the 0000003a error (logging on as local user results in a timeout and error ffffffff). Other "misconfigurations" yield the known 0000002x errors. Perhaps someone reading this forum has encountered this error.

    One thing I'd check - can you create a scheduled task when browsing to computer?

    Christian

    :1796
  • 0

    We have just encountered the same problem, and tried the same fixes.  Did you resolve it? 

    SCC4.0 on SBS2008 r2

    Win7 Pro 64-bit pc's

    11/12 new pc's installed fine; 1 shows 0000003a error.

    :6831
  • 0

    Hello,

    I'm reviving an old thread, but it's the same error.

    I've just completed a Windows SBS 2008 server install with all Microsoft updates installed, followed by Sophos, the Control Center is version 4.0.0.2362.

    I'm trying to protect Windows 7 client computers. The Sophos dashboard shows the client as Windows 7.

    When adding the computer, I have tried using the domain administrator, or a user with administrator rights. I also had to enable "Remote Registry" service on the client computer to go pass the initial error "0000002e  The installation did not start.  The computer may have been shut down, renamed or disconnected, or a required service may not be running.  It may be running Windows XP Home or Windows Vista."

    I now get the error "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.".

    From the server, I can access \\client\c$, the client registry and \\client\c$\windows\ tasks. I note that there is a file Sophos_InstTask.job in \\client\c$\windows\tasks. But from what I've read, Windows 7 Tasks are in \\client\c$\windows\system32\tasks and they are in xml format, not .job binary format.

    Is this the problem? Or is there something else I'm missing?

    Thanks

    Thierry

    :9185
  • 0

    resolved

    in group policy for domain: computer-policies windows setting - security- file system

    add %SystemRoot%\Tasks   - add rights to user who install

    You have to have rights to write to folder \\computer\c$\windows\tasks to all computers in domain

    by dafault even domain admins have no rights to wrtite to this folder from network

    :9369
  • 0

    Unfortunnately, this is not "resolved".

    As I mentioned, a file (Sophos_InstTask.job) is indeed created in %SystemRoot%\Tasks on the Windows 7 client computer,  so yes, the domain admins have full control to this folder. However, just after the file is created, a warning is shown in the console with code 0000003a.

    Also, as I understand Windows 7 doesn't run .job files from %SystemRoot%\Tasks, but it runs xml files from system32\Tasks.

    Any more suggestions?

    Thanks

    :9467
  • 0

    I have the problem with windows XP station.

     And I have tried to run  \\computername\windows\tasks from my windows 2008 server and I have seen that Domain Admins have only read permisions from this folder from this server for all XP stations  

    After i gave write permitions like above and wait a day or made gpupdate/force on the station- everything was ok.

    I

    I have one windows 7 workstation - i see that i have a error 0000002e  I will try to resolve it tomorrow.

    :9499
  • 0

    This is what I've been told by Sophos support today, I'm in the middle of trying this, so can't report on the results yet!

    please follow the steps below and advise results
    1. Open the Group Policy Management and edit the appropriate Domain Group Policy.
    2. Navigate to Computer Configuration | Policies | Windows Settings | Security Settings | System Services.
    3. Configure the following services:
        o Task Scheduler: Automatic
        o Windows Installer: Automatic
        o Remote registry: Automatic
        o Computer browser: Automatic
    4. Go back to Security Settings and select Windows Firewall with Advanced Security | Windows Firewall with Advanced Security.
    5. Set up the following rules for both inbound and outbound traffic:
        1. Rule Type: Port
            - Protocol and ports: TCP and 8192-8194
            - Action: Allow
            - Profile: Domain
            - Name: RMS rules
        2. Rule Type: Predefined: File and Printer Sharing
            - Rules: All
            - Action: Allow the connection
    6. Apply the Group Policy to the machines in the domain.
    7. In Sophos Control Center re-protect the computers using the 'Protect Computers' Wizard.

    :9501
  • 0

    5 out of my 6 Windows 7 clients were able to be updated by the Sophos Control Center after following the previous instructions. 1 didn't, still with the 0000003a error.

    There was an Event in the System Log of the Domain Controller, to do with the “trust” relation between the Domain Controller and the client computer.

    ------------------------

    Source:        NETLOGON

    Event ID:      5722

    Description:

    The session setup from the computer MACHINENAME failed to authenticate. The name(s) of the account(s) referenced in the security database is MACHINENAME $.  The following error occurred:

    Access is denied.

    ------------------------

    I had to “Reset Account” on the machine object using “AD Users and Computers” and then on the client I re-run the “Network ID” wizard (System Properties) to rejoin the domain.

    After a reboot, Sophos Control Center managed to “talk” to the client computer.

    All done now. All my Windows 7 clients are seen and updated by Sophos Control Center.

    :9585
  • 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
  • 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
Cookie Information Banner