Windows Forum

Ask something
Discussion Locked

Configuring AT scheduler w login script

0 helpful
9 replies

by joshua1 1 view

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
I'm trying to add entries to the Task Scheduler of NT 4.0 clients via login scripts w/ AT command. Problem: when the user logs in, the script fails due to insufficient user access. How do I over come this? I could configure this to do be done in the context of the local system account? I've tried the RunOnce parameter. I should change the acct the Task Scheduler uses? Thx.

9 replies

by rappenp

If you're running this from a login script the user is kicking off, my first thought is the user doesn't have right to run it.
Simple test create a user that does have rights to run it (I believe your missing run as service) Then login as that user. If this work it will give you a starting point.

by joshua1

I'm running this from a test account until I get it working. The test acct looks like a typical user. As mentioned, it is failing due to insufficient access. I also verified that the Run as Service. The script works great if you're an Administrator, but not if you're a user.
I think I've tried everything, gonna throw in the towel soon.
Thanks for your input.

by micahsdad

What are you trying to schedule? Why are you trying to schedule something at logon. Either you want something to run at a certain time, or you want it to run when they logon?

by joshua1

Things to schedule would be events such as: Virus Updates, Forced system shutdowns, automated backups, etc.

I want to configure the AT scheduler at logon. The logon script is meant to populate the AT scheduler. The AT scheduler would then run the specified event (like copying data files to a server) at the appropriate date/time.

by spydergst1

Your problem is a security issue. You must have administrative rights to run the at command. Either as the server admin or a domain admin. You might want to create a seperate script to run that at command and have the logon script call that script. That would secure the network a little more. You will have to use the net use command in the second script with the user name and password (this is a security risk), so the at command will run. also use the @ option in your script so users can't see the command excute. do this for the call command and the at command in the second script. This is tho most secure way to run and at command from a logon. good luck.

by joshua1

I thought that would work, too! It should work (according to theory), right? No luck. I've already tried this route several times. Have you gotten this to work? I've run it with a Domain Admin username/password to a logon server, and also triedmapping back to the Administrative share on the local machine. It seems to always run in the context of the logged-on user. It's looking to me like the AT scheduler can't be configured via login script. I'm assuming it's part of the security model? Wanted to see if I had missed something. Thanks for your time.

by rappenp

Try this. Open user manager, up at the top next to where it says User, Pull down the policies tab, then click User rights. Check the Show Advanced User Rights. Then pull down the rights window I think your looking for log on as batch file, but it may also need act as part of O.S. Shoot maybe even something else in there..

Anyway be real careful with this I would set up a group to play with and if could be a local group on the workstation even better.

Hope this helps you

Pete

This discussion is closed to new replies.