Hello all,

I realize that NT4 has been on M$ DL for a while, but we are trying to phase out our two servers. Part of which requires a backup script to be run at night. Which currently doesn't run, unless double clicked while logged in as admin. I checked this article http://www.windowsitpro.com/Articles/ArticleID/20769/20769.html?Ad=1

From there I can effectively rule out...
Reason #1 because, I set the task to run as Administrator and use the password for the account
Reason #2 because, I do not use %temp% variables anywhere in the vb script. (As far as I can tell.)
Reason #3 article is cut off because I am not a subscriber.

Does anyone have any thoughts on this or can point me in a direction, it would be much appreciated.

Thanks!VB script? BAT script?

I did not have problems with scheduled tasks (but this does not means that they are not).
Your scheduled task is launched? What error do you get? Where the script stops?VIKING thanks for the reply!

Believe it or not, the server I was working from was on the wrong time and date, so I was scheduling the job to run in the past. Though I had discovered that my vb script would fail to backup because it could not map the network drive correctly.

So far I am looking into creating a .bat file to map the network drive on the NT4 server and copy the needed files from the NT4 machine into the 2003 server through the map.I'm tired now, I am preparing to sleep 1-2 HOURS (and wake up at 7pm).
I don't recall a reason for which you will have to create a network map and than copy files. Why can't you just copy the files into that share? With no network mapping?[LE]
Later Edit:
To create a network map drive.
Let's SUPPOSE you wish that the share \\station1\TheShare to be mapped in the L:

net use L: \\station1\TheShare

Pay attention at network USER rights for accessing that share.
See a little more here: http://www.cae.wisc.edu/site/public/?title=nt4netuse .
[/LE]Thanks Viking!! I think I have it all working now!

Though that might change right when we get everything switched to the 2k3 servers. I guess I should look at it as job security.  You are most welcomed.
No, I don't think you will have to change big DEAL in the script or scheduled task with the windows 2003 servers.