I myself think it is a pretty bad idea, but it works...
In fact, it all depends on the real privilege needed, if this can be done
with an account with very light privileges, that may be a good solution.
Moreover, the batch itself can be restricted to system and admin
Marc
> -----Original Message-----
> From: Bunting, Jeff [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, August 14, 2001 3:48 PM
> To: NT System Admin Issues
> Subject: RE: AT COMMAND PROBLEM
>
>
> I should have clarified my original statement.
> You can do that, but then you'll have a username & password
> in plain text in
> the batch file which usually isn't a good idea.
>
> Jeff
>
> -----Original Message-----
> From: Marc Neiger [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, August 14, 2001 4:04 AM
> To: NT System Admin Issues
> Subject: RE: AT COMMAND PROBLEM
>
>
> NET USE shall work if you specify a user and password :
>
> net use x: \\server\share /user:adomain\asuser apassword
>
> However do not try to mix the same letters in the gui and AT
> batch, and
> always disconnect at the end of the batch
>
> net use x: /d
>
> Cheers,
>
> Marc Neiger
> Groupe Synergie Informatique
> 14 rue Saint Papoul
> 31000 Toulouse
> Tel 05 34 41 38 38 Fax: 05 34 41 38 39
>
>
> > -----Original Message-----
> > From: Bunting, Jeff [mailto:[EMAIL PROTECTED]]
> > Sent: Monday, August 13, 2001 10:50 PM
> > To: NT System Admin Issues
> > Subject: RE: AT COMMAND PROBLEM
> >
> >
> > NET USE won't work under the local system account. You'll
> > need to run the
> > job under another security context (assuming you have the
> > new scheduler
> > that lets you do this). Alternatively, you could change the account
> > scheduler runs under and create a share to use that has appropriate
> > permissions.
> >
> > jeff
> >
> > -----Original Message-----
> > From: Stephen Chiang [mailto:[EMAIL PROTECTED]]
> > Sent: Friday, August 10, 2001 5:22 PM
> > To: NT System Admin Issues
> > Subject: RE: AT COMMAND PROBLEM
> >
> >
> > Ahhh.... found out whats wrong. I cant switch to the L:
> > (network drive
> > mapped through GUI) through command even though its
> mapped.... Any way
> > around this or do I have to use net use?
> >
> > -----Original Message-----
> > From: xylog [mailto:[EMAIL PROTECTED]]
> > Sent: Friday, August 10, 2001 9:01 AM
> > To: NT System Admin Issues
> > Subject: Re: AT COMMAND PROBLEM
> >
> >
> > OK the local system account has no network access, that is
> > why it has that
> > name, Local means local not network. You need to either
> > assign the Scheduler
> > Service a network account or use the GUI task scheduler that
> > lets you assign
> > network permissions on a per job basis (
> > start->run->\\[server-name] and u
> > will see a scheduled tasks folder ...)
> >
> > -xylog
> >
> > ----- Original Message -----
> > From: "Stephen Chiang" <[EMAIL PROTECTED]>
> > To: "NT System Admin Issues" <[EMAIL PROTECTED]>
> > Sent: Friday, August 10, 2001 11:50 AM
> > Subject: RE: AT COMMAND PROBLEM
> >
> >
> > > I'm seeing the same thing. My .bat file runs when I double
> > click it, it
> > > even runs as scheduled on two other servers running Windows
> > 2000 server,
> > but
> > > on two other servers. I've checked permissions on the
> > scheduler service,
> > it
> > > is set for the Local System account... should work, it
> > works that way on
> > > the other two servers that work. The status code says 0x1
> > in the scheduled
> > > tasks screen whenever I try to run it from there.
> > >
> > >
> > >
> > >
> > > -----Original Message-----
> > > From: Bill Higgins [mailto:[EMAIL PROTECTED]]
> > > Sent: Friday, August 10, 2001 7:59 AM
> > > To: NT System Admin Issues
> > > Subject: RE: AT COMMAND PROBLEM
> > >
> > >
> > > Check permissions on the scheduler service
> > >
> > > -----Original Message-----
> > > From: Murray Freeman [mailto:[EMAIL PROTECTED]]
> > > Sent: Friday, August 10, 2001 07:58
> > > To: NT System Admin Issues
> > > Subject: AT COMMAND PROBLEM
> > >
> > >
> > >
> > > This is really weird. Our AT command works just fine for
> several bat
> > files,
> > > but we have one that just won't work. The bat file does
> > nothing more than
> > > copy some files from one server to another. If we double
> > click on the bat
> > > file, it works just fine. But when the AY command runs,
> > nothing happens.
> > If
> > > we try to run the AT using the bat file in question just
> > once, it deletes
> > > the line from the AT list OK, but it does not copy the
> > files. Any ideas?
> > >
> > > Murray
> > >
> > > http://www.sunbelt-software.com/ntsysadmin_list_charter.htm
> > >
> > > http://www.sunbelt-software.com/ntsysadmin_list_charter.htm
> > >
> > >
> > > http://www.sunbelt-software.com/ntsysadmin_list_charter.htm
> > >
> > >
> >
> >
> > http://www.sunbelt-software.com/ntsysadmin_list_charter.htm
> >
> >
> > http://www.sunbelt-software.com/ntsysadmin_list_charter.htm
> >
> > http://www.sunbelt-software.com/ntsysadmin_list_charter.htm
> >
> >
>
>
> http://www.sunbelt-software.com/ntsysadmin_list_charter.htm
>
> http://www.sunbelt-software.com/ntsysadmin_list_charter.htm
>
>
http://www.sunbelt-software.com/ntsysadmin_list_charter.htm
