Re: Problem with SCHTASKS parameters

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

Thanks for the pointers, but the documentation is quite misleading. It would
appear that /U and /P are NOT necessary(at least when the logged in user owns
the job), but as via the GUI, /RP is necessary to change the job
characteristics. This is true whether the job is on the local machine, or a
remote one. This is obscurely obvious in the wording of the password prompt,
requesting the 'RUN AS psw for domain\user".

In addition, because of this apparent duplicate user of the /RP value, it is
impossible to change the run time password of an existing job via the owning
user, since you can't authenticate the job and change its psw in the same
command, eg.
"schtasks /change /tn xxx [/U owner /P userpsw] /RP xyz" doesn't work, since
xyz is NOT the right password for the current job. On the other hand,
changing the job /RU to another user first, eg. SYSTEM, then back /RU
origuser /RP newpsw DOES work.

The bug is that even with authentification failures, at least the EN/DISable
setting can be changed; I haven't tried all the others.

"Bill Stewart" wrote:

> Jenksa wrote:
>
> > I'm trying to use schtasks to modify existing jobs, but while my
> > QUERY's work, and my syntax seesm to match the documentation, I keep
> > getting an error on my /CHANGE commands: schtasks /change /S vidar /U
> > "AMSA\username" /P password /tn test /enablerunning on Vidar.
>
> Use "schtasks /change /?" for help.
>
> Carefully read the descriptions for /U and /P, and compare these with
> /RU and /RP.
>
> /U and /P define the credentials that Schtasks should use when
> authenticating on the remote system. /RU and /RP define the credentials
> used for the task itself.
>
> --
> Bill Stewart
>
.

Relevant Pages

  • NT User A/C Lock
    ... The account locked by the web auto reflash after changing the password. ... That is part of documentation. ... > machine and the credentials they use are supposed to be documented. ... > Understanding the ISA 2004 Access Rule Processing ...
    (microsoft.public.security)
  • ANNOUNCEMENT: Network Identity Manager Version 2.0 Beta 3 available for public testing
    ... * The user documentation has been significantly rewritten. ... In addition to the Kerberos v5 identity provider, ... Unlocking the KeyStore results in the acquisition of credentials ...
    (comp.protocols.kerberos)
  • RE: asp.net login control not authenticating?
    ... I'm finding the Visual Studio 2005 Documentation to be very helpful ... > some documentation on the login control, but, I haven't found any. ... >> authenticated user to a specific URL based on the referring URL (admin roles ... >>> by the login control if Authenticate is NOT handled. ...
    (microsoft.public.dotnet.framework.aspnet.security)
  • Re: Help, Ive been hijacked! :-(
    ... can use to authenticate to the SMTP service to relay mail. ... use that username/password to authenticate to the SMTP server. ... >> a) Reading the documentation is a good start. ... >> what clients you can use) for authentication purposes ...
    (microsoft.public.inetserver.iis.smtp_nntp)
  • SCHTASKS with Local user
    ... According to the Microsoft "documentation," /s defaults to the current ... Cannot specify user name without specifying ... So, %computername% works fine, but I can not authenticate. ...
    (microsoft.public.windows.server.general)