Hard to believe but in all these years I've never had the need to use the AT
scheduler on a Win NT 4 (SP6a) server.
My first posting here, hope I have the correct address!
I made two schedules as follows:
at 04:30 /every:m,t,w,th c:\settings\backmail.cmd
at 18:30 /every:f c:\settings\backmail.cmd
Running AT yields the following result:
c:\WINNT\system32>at
Status ID Day Time Command Line
----------------------------------------------------------------------------
--
0 Each F 6:30 PM c:\settings\backmail.bat
2 Each M T W Th 4:30 AM c:\settings\backmail.bat
The contents of this batch file copies the a group of files from a local
server volume to a networked server volume.
The network server volume is on a Novell server, which is attached though
Microsoft client for NetWare using the account this server logs in as.
In other words, the batch file runs successfully if initiated manually.
However, if this batch file is initiated from the scheduled jobs, nothing
occurs.
Further investigation revealed the following:
I made a batch file called test.bat (and test.cmd) - either extension made
no difference.
The batch file was to make a folder and copy local files into the new
folder. If the new folder was
on the local system than the scheduled job worked.
Now, if the batch file was to create a folder on a network drive, the
scheduled batch file does not
work.
So, it seems that scheduled jobs do not function if the destination is a
network drive.
Again, please be aware that if I run the batch file manually, it does work
as intended.
So... how to I make scheduled jobs work regardless of the contents of the
batch files and why does it
even matter?
Next, I tried the following:
1. I went into services/schedule and set Log on as (choose the same account
this server is logging in
as and has rights to the folder where the batch file is saving to).
2. Stopped the service then started it up again.
3. Edited the test batch file to include both a local copy and network copy.
Example:
c:
cd \test
md test2
copy c:\test test2
md f:\test2
copy c:\test\*.* f:\test2
(note f: is a Novell network volume)
Running this batch file from explorer works, as it should. Allowing the AT
scheduler to run this batch
file only creates the local (c:) changes.
Finally, I changed the 'log on as' parameters to the admin password (that
has GOD rights) and still
no success.
Again, not willing to give up, I modified my test batch file to redirect
folder listings to a test file.
As expected, the resulting files for the networked volumes were 0k (no
errors, no text within). Only
the local drive volumes were recorded.
So now my question should be, how do I give an AT scheduled batch file the
SAME permissions as the currently
logged in account. It seems that the 'log on as' doesn't work!
UNLESS.... stopping and restarting the service is not sufficient!! Perhaps
I must restart the computer??
At this time, I have not rebooted this server during any of these changes
because of the 24/7 nature.
Your help is appreciated.
Thank you
----------------------------------------------------------------------------
---
Shawn Connelly, Network Engineer. Dipix Technologies Inc.
email: [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED]
------
You are subscribed as [email protected]
Archives: http://www.swynk.com/sitesearch/search.asp
To unsubscribe send a blank email to [EMAIL PROTECTED]
