Topic: Win XP Scheduled Task Error

So our lovely home office decided to disable Windows Scheduled Tasks. I guess it's easier to get rid of the problem instead of fixing it. Only problem with that is that I have a few scripts that backup very important files. They said they "re-enabled" it but it's still not working. When I try to add a task, I get an error ("Access Denied 0x80070005") which sounds like this problem but I have that patch installed already.

And yes, I am logged in as an administrator. ;-)

Does anyone have an idea or is it something that was probably done via group policies?

Thanks in advance.

Later,

C:\

judging from the other stories of your work, I'd say: group polices are a good guess.

hehehe....yeah. I am guessing that as well. However, our IT department has came back with the typical story "We haven't changed anything"


Oh well, when their crucial data is lost, they will then fix it

Later,

C:\

I am having the same issue, I do not believe it's related to group policy because I have reconfigured a PC and it currently has up-to-date windows updates, it is receiving the same group policy as computers that are not working. I thought it may have been a Windows Update that caused this issue, but to this point I am unable to pinpoint it.

This is probably a daft question, but what security software are you using (firewall, antivirus)?

quote:

---

White Hawk said:

This is probably a daft question, but what security software are you using (firewall, antivirus)?

---

our company has hardware firewalls and the AV is Trend Micro

Later,

C:\

eipee73, your answer?

CPrompt - I have to agree with the rest, group policies sound like your culprits. Eipee73's issue, despite the similarity in symptoms, is likely not related. Some firewall/AV solutions protect their own files while resident, which may lead to backup processes failing as a result of restricted access. Two possible workarounds are 1) run the backup process in networked safe mode, or 2) disable all security solutions while backing up.

It is admittedly a shot in the dark...

White Hawk - I actually think that C:\ and I may have the same issue on our hands. The timing of the whole thing is what lead me to believe that it may have been a Windows Update.

We are actually running the same as C:\ (Hardware firewalls and Trend Micro AV). I have uninstalled TrendMicro and attempted to schedule a task with no success.

****UPDATE****

I found this solution on another site a bit earlier in the morning and I tried it out during my last post. It has finished and I am now able to schedule tasks on the machine I ran it on. This isn't a good solution if a large number of machines are having the issue, but if you need to get a few back up and going this should work:

http://blogs.msdn.com/astebner/archive/2006/09/04/739820.aspx

Please let me know what happens.

eipee73 : doesn't look like our situations are the same. I just did what you suggested on a test box here and I still can't schedule a task.
I did see when the script was running that Access was denied in the C:\Windows\Tasks directory.

I am sure that our HO did some type of Group Policy here that disabled it. Now...the question is, do they know what they did to disable it and how to fix it?

Later,

C:\

C:\ : Do you have administrator privileges on your computer? If not I think you'll need to have someone with admin rights to log into the machine and run this. I'm about to test it on another PC and I'll let you know the results. If they still have it disabled in GP then you may be in trouble...did you try this workaround:

To work around this problem, add the "Access this computer from the network" permission to the user account that will run the
scheduled task. To do this for the local computer policy, follow these steps:

1. Click Start, click Run, type Gpedit.msc, and then click OK.
2. Expand the following items in the Local Computer Policy list:
Computer Configuration
Windows Settings
Security Settings
Local Policies
3. Click User Rights Assignment.
4. Double-click Access this computer from the network, and then click Add User or Group.
5. Add the new user name or the group name in the Enter the object names to select area.
6. Click Check Names to verify the entries.
7. Click OK two times.

I just ran the subacl and those commands on another PC that had the issue and it is working properly again. This seems to be resolving my issues, like I said though, I'm logging in as an administrator to do this.

quote:

---

eipee73 said:

C:\ : Do you have administrator privileges on your computer?

---

Of course. Local and network.

Later,

C:\

I suppose I should have read your first post a little bit better! I'm not really sure what to tell you if that program and script from that website don't work... I'm kind of left drawing a blank, I presume that you do reboot your computer on a nightly basis so it would have up to date group policy and it wouldn't still have the old one in there that prevented your use of Scheduled Tasks?

Ah, well... it was a shot in the dark anyway.

It seems that our issue may have been the result of a GPO to disable autorun during the conficker attacks. The GPO has since been disabled and the fix that was provided is working for us, you may want to check with your home office to see if there is still a group policy to prohibit autorun in effect.

quote:

---

eipee73 said:

It seems that our issue may have been the result of a GPO to disable autorun during the conficker attacks. The GPO has since been disabled and the fix that was provided is working for us, you may want to check with your home office to see if there is still a group policy to prohibit autorun in effect.

---

Now you may be on to something eipee733 !! They did issue a registry hack to disable AutoRun. I think I still have the registry file that was pushed out. I can change it and test it. If it works, then I can send it to them and have them re-issue it.

Thanks!! This has been driving me nuts!

Later,

C:\

I hope this helps you out. By chance do you think you could send me a copy of that registry file so I can take a look at it? Hopefully I can draw a conclusion from that and maybe even narrow down my fix.

Matt_filip@yahoo.com

You may have to change the extension from .reg to .txt to get it to come through.

Thanks!

I'll send it to you shortly. However, changing it back did not fix my problem and the HO claims they did nothing including a GP on AutoPlay. I doubt it though

Later,

C:\