Is it possible to use GPO to run a batch file once a week? NOT login/logout scripts!!

Hello Experts,

I'm not an AD guru by any means, and have little experience with GPO's. I would like to know if it's possible to use GPO to run a bat file once a week on my DCs. I have created a folder on one of my DCs (C:\scripts). I know that I can use Task Scheduler to run the bat file, which works beautifully. However, what if I had 100 machines onto which I wanted to do the same thing? Would I have to use the Task Scheduler on all 100 machines? Yikes! I only have 8 DCs, which is not too bad, but I'm convinced that there's gotta be a way thru AD/GPO in which I can accomplish this.
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

You should be able to create the batch file the make a batch file to copy it to the administrative shares for the task scheduler on each machine
bnditAuthor Commented:
Hi LVNeptune,

Could you elaborate a bit? I think you're suggesting that I create a batch file that would copy my folder containing my scripts to each server, correct? However, I don't quite understand the second part about the task scheduler. Are you offering an automated way to "copy" the task to each server or you're just saying that once I have copied the folder to each server I can use the task scheduler to setup the individual jobs?
Perhaps have a look at this previous question:

It will give you some info on running jobs remotely (perhaps you can shcedule the task on the main server that runs the jobs remotely).
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

I haven't had to implement it manually as I use Level Platforms at my office but my idea was this:


copy \\SERVER\c$\windows\tasks\taskname.job \\workstation\c$\windows\tasks\

Make a little more sense? You create the task on the server then create a batch file that copies the file to the workstations. I am not a batch file guru but if your workstations are named WRK1-WRK20 I am sure you can use a variable and increase it so you don't need to manually type out the workstation names.
The GPO improvements in Windows Server 2008 (which will back-port to 2K3 and XP) will allow you to manipulate Scheduled Tasks via GPO on target machines. At present anything you would configure like that would either involve something 3rd-party like SMS or else would be a bit of a kludge; typically I'll use psexec from an administrative workstation to push out scheduled tasks rather than mucking with Scheduled Tasks on remote machines.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
bnditAuthor Commented:
I noticed your handle has "MVP", are you a Microsoft MVP?
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Active Directory

From novice to tech pro — start learning today.