By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
435,620 Members | 1,303 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 435,620 IT Pros & Developers. It's quick & easy.


P: 3
This used to work on a Windows 2000 PC.
I have an Access database on a shared network that calls a task on a now Windows 7 PC that does not appear to be working. I am using the following in the command line:
Expand|Select|Wrap|Line Numbers
  1. SCHTASKS /run/s \\"computer name" /tn "Name of scheduled task".
Any ideas why this would not work? I am not receiving an error message so it is hard to determine.
Thank you
Sep 4 '12 #1
Share this Question
Share on Google+
3 Replies

Expert Mod 5K+
P: 5,397
Check group policies under windows.
Win7 changed a lot of things that the scheduler used to be able to do... also, if the PC is part of an enterprise network, the IT-Security team could have restricted what can and can not be done.

A lot of my autoschedules were broken this way when the company went to Win7

Sep 4 '12 #2

Expert Mod 15k+
P: 31,494
I've moved this to the Windows forum (as it's fundamentally a Windows question).
Sep 5 '12 #3

P: 3
Thank you for your assistance
Sep 7 '12 #4

Post your reply

Sign in to post your reply or Sign up for a free account.