Running task scheduler under normal user

[Alexander Grech]

I was wondering if it was possible to run scheduled task under a normal user
account while no user is logged on to the machine. I need to run a VBS
script.
any information would be greatly appreciated

 

[Pegasus \(MVP\)]

I was wondering if it was possible to run scheduled task under a normal user
account while no user is logged on to the machine. I need to run a VBS
script.
any information would be greatly appreciated

Sure - just specify the desired account when you create the
scheduled task. The job will run whether that user is logged
on or not.

 

[Alexander Grech]

thank you for you reply,

I have tried that and the scheduler tell me that the program could not
start. This is a stand alone computer. I checked the scheduler logs and it
is telling me that the user does not have enough access privilages. When I
run the task with the user logged in it works fine, but when I log off and
log back on, I am greeted with the could not start error. Does the user have
to have admin privilages to run a task while logged off?

 

[Pegasus \(MVP\)]

thank you for you reply,

I have tried that and the scheduler tell me that the program could not
start. This is a stand alone computer. I checked the scheduler logs and it
is telling me that the user does not have enough access privilages. When I
run the task with the user logged in it works fine, but when I log off and
log back on, I am greeted with the could not start error. Does the user have
to have admin privilages to run a task while logged off?

Run gpedit.msc, locate "User Rights" and ensure that the selected
user has the right to log in as a batch job.

 

[Alexander Grech]

thanks again.

Yes, the user is part of the backup operators group, which is listed, I have
added the user too. This error does not happen when I try to run the
scheduled task under system or administrator. User rights Deny are not set,
so no user or group is denied to log on as batch or service. when I am
logged on as Admin and I run the scheduled task under the test user, the
task runs but nothing happens. Logs say the task ran successfully but the
VBS script was not executed.

Please help, I have been trying to trouble shoot this problem for 2 weeks
now. Windows installations are fresh and fully updated

 

[Pegasus \(MVP\)]

Did you run gpedit as I suggested?

You should also add some diagnostics to your job:

@echo off
echo %date% %time% Start of job > c:\test.log
YourVBSJob 1>>c:\test.log 2>>c:\test.err
echo %date% %time% End of job >> c:\test.log

Now examine the two log files.

 

[Alexander Grech]

ok, I ran gpedit and now the user has access to log on as a batch job, when
I run the task, the scheduler log reports that the task was run successfully
but the .cmd or .bat file does not execute. the logs are not created and no
files are moved. The bat works perfectly when I double click on it. this
happens when I run it under a normal user but not when I run it under the
admin or system account. The user is a power user and backup operator.

could it be that my task scheduler corrupted or I need an update which is
not supplied with the service pack?

 

[Pegasus \(MVP\)]

Post the first few lines of your batch file here.

 

[Alexander Grech]

this is the batch file:

@echo off
echo %date% %time% Start of job > c:\test.log
c:\83.vbs 1>>c:\test.log 2>>c:\test.err
echo %date% %time% End of job >> c:\test.log

I use it to run a VBS script which moves files from one folder to another.

 

[Pegasus \(MVP\)]

There is nothing wrong with this batch job. Now go to
the Control Panel / Scheduled Tasks / Advanced /
View Log. Use Edit-Find to locate the word "recent". This
should get you to this line:
[ ***** Most recent entry is above this line ***** ]
Now copy & paste the lines above this line into your
next post.

 

[Alexander Grech]

"83.job" (83.cmd)
Started 5/25/2004 3:08:00 PM
"83.job" (83.cmd)
Finished 5/25/2004 3:08:00 PM
Result: The task completed with an exit code of (1).
[ ***** Most recent entry is above this line ***** ]

There is nothing wrong with this batch job. Now go to
the Control Panel / Scheduled Tasks / Advanced /
View Log. Use Edit-Find to locate the word "recent". This
should get you to this line:
[ ***** Most recent entry is above this line ***** ]
Now copy & paste the lines above this line into your
next post.

this is the batch file:

@echo off
echo %date% %time% Start of job > c:\test.log
c:\83.vbs 1>>c:\test.log 2>>c:\test.err
echo %date% %time% End of job >> c:\test.log

I use it to run a VBS script which moves files from one folder to another.

under
the which
is are
not

when

I successfully
but

for

2 I
log Does
the

need

to

 

[Pegasus \(MVP\)]

The exit code of 1 indicates that something was not quite
right in your batch job. In order to walk before you run,
modify the batch job like below, then post these things:
- c:\test.log
- The task scheduler log file entry

You must also make absolutely sure that you enter the
correct password for the scheduled job.

@echo off
echo %date% %time% %UserName% Start of job > c:\test.log
echo %date% %time% End of job >> c:\test.log

I am signing out now - my time zone is 9 hours ahead
of yours.

"83.job" (83.cmd)
Started 5/25/2004 3:08:00 PM
"83.job" (83.cmd)
Finished 5/25/2004 3:08:00 PM
Result: The task completed with an exit code of (1).
[ ***** Most recent entry is above this line ***** ]

There is nothing wrong with this batch job. Now go to
the Control Panel / Scheduled Tasks / Advanced /
View Log. Use Edit-Find to locate the word "recent". This
should get you to this line:
[ ***** Most recent entry is above this line ***** ]
Now copy & paste the lines above this line into your
next post.

this is the batch file:

@echo off
echo %date% %time% Start of job > c:\test.log
c:\83.vbs 1>>c:\test.log 2>>c:\test.err
echo %date% %time% End of job >> c:\test.log

I use it to run a VBS script which moves files from one folder to another.

Post the first few lines of your batch file here.


ok, I ran gpedit and now the user has access to log on as a batch job,
when
I run the task, the scheduler log reports that the task was run
successfully
but the .cmd or .bat file does not execute. the logs are not

created
and

no
files are moved. The bat works perfectly when I double click on

it.
this

happens when I run it under a normal user but not when I run it under
the
admin or system account. The user is a power user and backup operator.

could it be that my task scheduler corrupted or I need an update which
is
not supplied with the service pack?


Did you run gpedit as I suggested?

You should also add some diagnostics to your job:

@echo off
echo %date% %time% Start of job > c:\test.log
YourVBSJob 1>>c:\test.log 2>>c:\test.err
echo %date% %time% End of job >> c:\test.log

Now examine the two log files.

thanks again.

Yes, the user is part of the backup operators group, which is
listed,
I
have
added the user too. This error does not happen when I try to

run
the

scheduled task under system or administrator. User rights Deny are
not
set,
so no user or group is denied to log on as batch or service.

when

I
am
logged on as Admin and I run the scheduled task under the test user,
the
task runs but nothing happens. Logs say the task ran successfully
but
the
VBS script was not executed.

Please help, I have been trying to trouble shoot this problem

for

2
weeks
now. Windows installations are fresh and fully updated

thank you for you reply,

I have tried that and the scheduler tell me that the program
could
not
start. This is a stand alone computer. I checked the scheduler
logs
and
it
is telling me that the user does not have enough access
privilages.
When
I
run the task with the user logged in it works fine, but

when

I need

 

[Ricardo M. Urbano - W2K/NT4 MVP]

Sure - just specify the desired account when you create the
scheduled task. The job will run whether that user is logged
on or not.

Pegasus, I could be wrong, but I am certain that a user needs to have
local admin rights to run scheduled jobs. That could be a serious
security exposure otherwise.

 

[Pegasus \(MVP\)]

Pegasus, I could be wrong, but I am certain that a user needs to have
local admin rights to run scheduled jobs. That could be a serious
security exposure otherwise.

To be sure of what I was talking about, I created an ordinary
user on one of my machines. As soon as I gave him the ability
to log on as a batch job, he was able to run scheduled jobs.

 

[Alexander Grech]

Hi All

Pegasus, could you tell me what scheduled task you tried giving your user
please. On my computer the scheduled task in the GUI is running, and I see
it run however the .bat job is not working. Without any errors, it is like
the .bat job is totally ignored by the system.

 

[Alexander Grech]

Hi Pegasus

here is the result, again exit code 1.

"83.job" (83.cmd)
Finished 5/26/2004 11:44:38 AM
Result: The task completed with an exit code of (1).
[ ***** Most recent entry is above this line ***** ]

The exit code of 1 indicates that something was not quite
right in your batch job. In order to walk before you run,
modify the batch job like below, then post these things:
- c:\test.log
- The task scheduler log file entry

You must also make absolutely sure that you enter the
correct password for the scheduled job.

@echo off
echo %date% %time% %UserName% Start of job > c:\test.log
echo %date% %time% End of job >> c:\test.log

I am signing out now - my time zone is 9 hours ahead
of yours.

"83.job" (83.cmd)
Started 5/25/2004 3:08:00 PM
"83.job" (83.cmd)
Finished 5/25/2004 3:08:00 PM
Result: The task completed with an exit code of (1).
[ ***** Most recent entry is above this line ***** ]

There is nothing wrong with this batch job. Now go to
the Control Panel / Scheduled Tasks / Advanced /
View Log. Use Edit-Find to locate the word "recent". This
should get you to this line:
[ ***** Most recent entry is above this line ***** ]
Now copy & paste the lines above this line into your
next post.


this is the batch file:

@echo off
echo %date% %time% Start of job > c:\test.log
c:\83.vbs 1>>c:\test.log 2>>c:\test.err
echo %date% %time% End of job >> c:\test.log

I use it to run a VBS script which moves files from one folder to another.

Post the first few lines of your batch file here.


ok, I ran gpedit and now the user has access to log on as a

batch
job,

when
I run the task, the scheduler log reports that the task was run
successfully
but the .cmd or .bat file does not execute. the logs are not created
and
no
files are moved. The bat works perfectly when I double click on it.
this
happens when I run it under a normal user but not when I run it under
the
admin or system account. The user is a power user and backup operator.

could it be that my task scheduler corrupted or I need an update which
is
not supplied with the service pack?


Did you run gpedit as I suggested?

You should also add some diagnostics to your job:

@echo off
echo %date% %time% Start of job > c:\test.log
YourVBSJob 1>>c:\test.log 2>>c:\test.err
echo %date% %time% End of job >> c:\test.log

Now examine the two log files.

thanks again.

Yes, the user is part of the backup operators group, which is
listed,
I
have
added the user too. This error does not happen when I try to run
the
scheduled task under system or administrator. User rights

Deny
are

not
set,
so no user or group is denied to log on as batch or service. when
I
am
logged on as Admin and I run the scheduled task under the test
user,
the
task runs but nothing happens. Logs say the task ran successfully
but
the
VBS script was not executed.

Please help, I have been trying to trouble shoot this

problem
for

2
weeks
now. Windows installations are fresh and fully updated

thank you for you reply,

I have tried that and the scheduler tell me that the program
could
not
start. This is a stand alone computer. I checked the scheduler
logs
and
it
is telling me that the user does not have enough access
privilages.
When
I
run the task with the user logged in it works fine, but

when

I
log
off
and
log back on, I am greeted with the could not start

error.
Does

the
user
have
to have admin privilages to run a task while logged off?






I was wondering if it was possible to run scheduled task
under
a
normal
user
account while no user is logged on to the machine. I need
to
run
a
VBS
script.
any information would be greatly appreciated



Sure - just specify the desired account when you

create
the

scheduled task. The job will run whether that user is logged
on or not.





Run gpedit.msc, locate "User Rights" and ensure that the
selected
user has the right to log in as a batch job.

 

[Pegasus \(MVP\)]

You did not actually say so but I assume that c:\test.log
does not exist, indicating that the job never ran, or that
the user account you used does not have write-access
to both c:\test.log and c:\test.bat.

Your results are at variance with the results I observe on
one of my own machines, working with an ordinary user
account that I created specifically for the purpose of this
thread. They are also at variance with all my past observations.

Incidentally, the job I specified in the GUI of the Task
Scheduler was c:\test.bat.

I'm sorry but this is as far as I can take you.

Hi Pegasus

here is the result, again exit code 1.

"83.job" (83.cmd)
Finished 5/26/2004 11:44:38 AM
Result: The task completed with an exit code of (1).
[ ***** Most recent entry is above this line ***** ]

The exit code of 1 indicates that something was not quite
right in your batch job. In order to walk before you run,
modify the batch job like below, then post these things:
- c:\test.log
- The task scheduler log file entry

You must also make absolutely sure that you enter the
correct password for the scheduled job.

@echo off
echo %date% %time% %UserName% Start of job > c:\test.log
echo %date% %time% End of job >> c:\test.log

I am signing out now - my time zone is 9 hours ahead
of yours.

"83.job" (83.cmd)
Started 5/25/2004 3:08:00 PM
"83.job" (83.cmd)
Finished 5/25/2004 3:08:00 PM
Result: The task completed with an exit code of (1).
[ ***** Most recent entry is above this line ***** ]

There is nothing wrong with this batch job. Now go to
the Control Panel / Scheduled Tasks / Advanced /
View Log. Use Edit-Find to locate the word "recent". This
should get you to this line:
[ ***** Most recent entry is above this line ***** ]
Now copy & paste the lines above this line into your
next post.


this is the batch file:

@echo off
echo %date% %time% Start of job > c:\test.log
c:\83.vbs 1>>c:\test.log 2>>c:\test.err
echo %date% %time% End of job >> c:\test.log

I use it to run a VBS script which moves files from one folder to
another.

Post the first few lines of your batch file here.


ok, I ran gpedit and now the user has access to log on as a batch
job,
when
I run the task, the scheduler log reports that the task was run
successfully
but the .cmd or .bat file does not execute. the logs are not created
and
no
files are moved. The bat works perfectly when I double click

on
it.

this
happens when I run it under a normal user but not when I run it
under
the
admin or system account. The user is a power user and backup
operator.

could it be that my task scheduler corrupted or I need an update
which
is
not supplied with the service pack?


Did you run gpedit as I suggested?

You should also add some diagnostics to your job:

@echo off
echo %date% %time% Start of job > c:\test.log
YourVBSJob 1>>c:\test.log 2>>c:\test.err
echo %date% %time% End of job >> c:\test.log

Now examine the two log files.

thanks again.

Yes, the user is part of the backup operators group, which is
listed,
I
have
added the user too. This error does not happen when I try

to
run

the
scheduled task under system or administrator. User rights Deny
are
not
set,
so no user or group is denied to log on as batch or service.
when
I
am
logged on as Admin and I run the scheduled task under the test
user,
the
task runs but nothing happens. Logs say the task ran
successfully
but
the
VBS script was not executed.

Please help, I have been trying to trouble shoot this problem
for
2
weeks
now. Windows installations are fresh and fully updated

thank you for you reply,

I have tried that and the scheduler tell me that the program
could
not
start. This is a stand alone computer. I checked the
scheduler
logs
and
it
is telling me that the user does not have enough access
privilages.
When
I
run the task with the user logged in it works fine,

but
when

I
log
off
and
log back on, I am greeted with the could not start error.
Does
the
user
have
to have admin privilages to run a task while logged off?






I was wondering if it was possible to run

scheduled
task

under
a
normal
user
account while no user is logged on to the machine. I
need
to
run
a
VBS
script.
any information would be greatly appreciated



Sure - just specify the desired account when you create
the
scheduled task. The job will run whether that user is
logged
on or not.





Run gpedit.msc, locate "User Rights" and ensure that the
selected
user has the right to log in as a batch job.

 

[Alexander Grech]

Thanks alot for your help and for your time. I really appreciated it. If I
may ask one more favour. could you just post the steps you took when
creating and assigning privilages to the new task user. they needn't be
detailed. point form is good and I will try to follow the tasks listed from
a fresh installation of Windows 2000

Thanks again.

You did not actually say so but I assume that c:\test.log
does not exist, indicating that the job never ran, or that
the user account you used does not have write-access
to both c:\test.log and c:\test.bat.

Your results are at variance with the results I observe on
one of my own machines, working with an ordinary user
account that I created specifically for the purpose of this
thread. They are also at variance with all my past observations.

Incidentally, the job I specified in the GUI of the Task
Scheduler was c:\test.bat.

I'm sorry but this is as far as I can take you.

Hi Pegasus

here is the result, again exit code 1.

"83.job" (83.cmd)
Finished 5/26/2004 11:44:38 AM
Result: The task completed with an exit code of (1).
[ ***** Most recent entry is above this line ***** ]

The exit code of 1 indicates that something was not quite
right in your batch job. In order to walk before you run,
modify the batch job like below, then post these things:
- c:\test.log
- The task scheduler log file entry

You must also make absolutely sure that you enter the
correct password for the scheduled job.

@echo off
echo %date% %time% %UserName% Start of job > c:\test.log
echo %date% %time% End of job >> c:\test.log

I am signing out now - my time zone is 9 hours ahead
of yours.


"83.job" (83.cmd)
Started 5/25/2004 3:08:00 PM
"83.job" (83.cmd)
Finished 5/25/2004 3:08:00 PM
Result: The task completed with an exit code of (1).
[ ***** Most recent entry is above this line ***** ]

There is nothing wrong with this batch job. Now go to
the Control Panel / Scheduled Tasks / Advanced /
View Log. Use Edit-Find to locate the word "recent". This
should get you to this line:
[ ***** Most recent entry is above this line ***** ]
Now copy & paste the lines above this line into your
next post.


this is the batch file:

@echo off
echo %date% %time% Start of job > c:\test.log
c:\83.vbs 1>>c:\test.log 2>>c:\test.err
echo %date% %time% End of job >> c:\test.log

I use it to run a VBS script which moves files from one folder to
another.

Post the first few lines of your batch file here.


ok, I ran gpedit and now the user has access to log on as a batch
job,
when
I run the task, the scheduler log reports that the task was run
successfully
but the .cmd or .bat file does not execute. the logs are not
created
and
no
files are moved. The bat works perfectly when I double click on
it.
this
happens when I run it under a normal user but not when I run it
under
the
admin or system account. The user is a power user and backup
operator.

could it be that my task scheduler corrupted or I need an update
which
is
not supplied with the service pack?


Did you run gpedit as I suggested?

You should also add some diagnostics to your job:

@echo off
echo %date% %time% Start of job > c:\test.log
YourVBSJob 1>>c:\test.log 2>>c:\test.err
echo %date% %time% End of job >> c:\test.log

Now examine the two log files.

thanks again.

Yes, the user is part of the backup operators group,

which
is

listed,
I
have
added the user too. This error does not happen when I

try

to rights
Deny the
test

machine.

I

 

[Pegasus \(MVP\)]

I did not take any special steps. I simply created a new user
under Win2000, accepting the default settings. I then ran
gpedit.msc and allowed this user to log on as a batch job.

Thanks alot for your help and for your time. I really appreciated it. If I
may ask one more favour. could you just post the steps you took when
creating and assigning privilages to the new task user. they needn't be
detailed. point form is good and I will try to follow the tasks listed from
a fresh installation of Windows 2000

Thanks again.

You did not actually say so but I assume that c:\test.log
does not exist, indicating that the job never ran, or that
the user account you used does not have write-access
to both c:\test.log and c:\test.bat.

Your results are at variance with the results I observe on
one of my own machines, working with an ordinary user
account that I created specifically for the purpose of this
thread. They are also at variance with all my past observations.

Incidentally, the job I specified in the GUI of the Task
Scheduler was c:\test.bat.

I'm sorry but this is as far as I can take you.

Hi Pegasus

here is the result, again exit code 1.

"83.job" (83.cmd)
Finished 5/26/2004 11:44:38 AM
Result: The task completed with an exit code of (1).
[ ***** Most recent entry is above this line ***** ]
The exit code of 1 indicates that something was not quite
right in your batch job. In order to walk before you run,
modify the batch job like below, then post these things:
- c:\test.log
- The task scheduler log file entry

You must also make absolutely sure that you enter the
correct password for the scheduled job.

@echo off
echo %date% %time% %UserName% Start of job > c:\test.log
echo %date% %time% End of job >> c:\test.log

I am signing out now - my time zone is 9 hours ahead
of yours.


"83.job" (83.cmd)
Started 5/25/2004 3:08:00 PM
"83.job" (83.cmd)
Finished 5/25/2004 3:08:00 PM
Result: The task completed with an exit code of (1).
[ ***** Most recent entry is above this line ***** ]

There is nothing wrong with this batch job. Now go to
the Control Panel / Scheduled Tasks / Advanced /
View Log. Use Edit-Find to locate the word "recent". This
should get you to this line:
[ ***** Most recent entry is above this line ***** ]
Now copy & paste the lines above this line into your
next post.


this is the batch file:

@echo off
echo %date% %time% Start of job > c:\test.log
c:\83.vbs 1>>c:\test.log 2>>c:\test.err
echo %date% %time% End of job >> c:\test.log

I use it to run a VBS script which moves files from one folder to
another.

Post the first few lines of your batch file here.


ok, I ran gpedit and now the user has access to log on as a
batch
job,
when
I run the task, the scheduler log reports that the task

was
run

successfully
but the .cmd or .bat file does not execute. the logs are not
created
and
no
files are moved. The bat works perfectly when I double

click
on

it.
this
happens when I run it under a normal user but not when I

run
it

under
the
admin or system account. The user is a power user and backup
operator.

could it be that my task scheduler corrupted or I need an update
which
is
not supplied with the service pack?


Did you run gpedit as I suggested?

You should also add some diagnostics to your job:

@echo off
echo %date% %time% Start of job > c:\test.log
YourVBSJob 1>>c:\test.log 2>>c:\test.err
echo %date% %time% End of job >> c:\test.log

Now examine the two log files.

thanks again.

Yes, the user is part of the backup operators group, which
is
listed,
I
have
added the user too. This error does not happen when I

try

to
run
the
scheduled task under system or administrator. User rights
Deny
are
not
set,
so no user or group is denied to log on as batch or service.
when
I
am
logged on as Admin and I run the scheduled task under the
test
user,
the
task runs but nothing happens. Logs say the task ran
successfully
but
the
VBS script was not executed.

Please help, I have been trying to trouble shoot this
problem
for
2
weeks
now. Windows installations are fresh and fully updated

thank you for you reply,

I have tried that and the scheduler tell me that the
program
could
not
start. This is a stand alone computer. I checked the
scheduler
logs
and
it
is telling me that the user does not have enough access
privilages.
When
I
run the task with the user logged in it works

fine,
but

when
I
log
off
and
log back on, I am greeted with the could not start
error.
Does
the
user
have
to have admin privilages to run a task while

logged
off?

I was wondering if it was possible to run scheduled
task
under
a
normal
user
account while no user is logged on to the

machine.

I
need
to
run
a
VBS
script.
any information would be greatly appreciated



Sure - just specify the desired account when you
create
the
scheduled task. The job will run whether that

user
is

logged
on or not.





Run gpedit.msc, locate "User Rights" and ensure that the
selected
user has the right to log in as a batch job.

 

[Alexander Grech]

Ok thanks a real lot for your help

I did not take any special steps. I simply created a new user
under Win2000, accepting the default settings. I then ran
gpedit.msc and allowed this user to log on as a batch job.

Thanks alot for your help and for your time. I really appreciated it. If I
may ask one more favour. could you just post the steps you took when
creating and assigning privilages to the new task user. they needn't be
detailed. point form is good and I will try to follow the tasks listed from
a fresh installation of Windows 2000

Thanks again.

You did not actually say so but I assume that c:\test.log
does not exist, indicating that the job never ran, or that
the user account you used does not have write-access
to both c:\test.log and c:\test.bat.

Your results are at variance with the results I observe on
one of my own machines, working with an ordinary user
account that I created specifically for the purpose of this
thread. They are also at variance with all my past observations.

Incidentally, the job I specified in the GUI of the Task
Scheduler was c:\test.bat.

I'm sorry but this is as far as I can take you.


Hi Pegasus

here is the result, again exit code 1.

"83.job" (83.cmd)
Finished 5/26/2004 11:44:38 AM
Result: The task completed with an exit code of (1).
[ ***** Most recent entry is above this line ***** ]
The exit code of 1 indicates that something was not quite
right in your batch job. In order to walk before you run,
modify the batch job like below, then post these things:
- c:\test.log
- The task scheduler log file entry

You must also make absolutely sure that you enter the
correct password for the scheduled job.

@echo off
echo %date% %time% %UserName% Start of job > c:\test.log
echo %date% %time% End of job >> c:\test.log

I am signing out now - my time zone is 9 hours ahead
of yours.


"83.job" (83.cmd)
Started 5/25/2004 3:08:00 PM
"83.job" (83.cmd)
Finished 5/25/2004 3:08:00 PM
Result: The task completed with an exit code of (1).
[ ***** Most recent entry is above this line ***** ]

There is nothing wrong with this batch job. Now go to
the Control Panel / Scheduled Tasks / Advanced /
View Log. Use Edit-Find to locate the word "recent". This
should get you to this line:
[ ***** Most recent entry is above this line ***** ]
Now copy & paste the lines above this line into your
next post.


this is the batch file:

@echo off
echo %date% %time% Start of job > c:\test.log
c:\83.vbs 1>>c:\test.log 2>>c:\test.err
echo %date% %time% End of job >> c:\test.log

I use it to run a VBS script which moves files from one

folder
to

another.

Post the first few lines of your batch file here.


ok, I ran gpedit and now the user has access to log on

as

a I
try under
the that
the