What account is the scheduled task using? Does the job work fine if you manually run it using the same credentials as the scheduled task?
If not, what error is received? -ASB: http://XeeSM.com/AndrewBaker On Wed, Jun 2, 2010 at 4:03 PM, Steve Kelsay <[email protected]> wrote: > The thing is, it all worked for years in all earlier version of > Microsoft using UNC connections. Now in 2008, it is screwed. I need to > do some workarounds, as this is a "big bucks going into the bank" issue. > > > -----Original Message----- > From: Ben Scott [mailto:[email protected]] > Sent: Wednesday, June 02, 2010 2:56 PM > To: NT System Admin Issues > Subject: Re: Server 2008 reading from Novell server > > On Wed, Jun 2, 2010 at 1:55 PM, Steve Kelsay <[email protected]> wrote: > > It is just that when running as a scheduled task, > > the Novell login is popping up, which doesn't work if no one is on the > > machine, and it will not run unattended. > > Scheduled Tasks don't have access to things like network drives when > using the Microsoft SMB client. It's almost like they run in a > different user profile. I would expect the same to apply to NetWare. > > Try using a local batch file as the Scheduled Task target. Have > that batch file map the network drives, and then run whatever you want > to run. You might still need to provide credentials to the NetWare > client, but that's at least scriptable with a batch file. > > -- Ben > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ > ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ > > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ > ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
