Local Security Properties. Look at all the locations that Local Service
Account are and put your user id in there. We use a local account for
running remote procedures on Windows servers. We create our own named
service account for the application, run the remote command under that
profile, not allow the profile to logon locally, no other privileges
than necessary, and grant access to what ever applications and folders
necessary, no more and no less. With this being a local profile, it
will not have any access to your domain and the password can be saved in
your remote command. Really it should be secured in a file or data area
with restricted access and the application would read the user id /
password at run time.
Search the archives for the list of service properties, it has been
Director of Information Services
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of tim
Sent: Monday, March 31, 2008 12:57 PM
To: 'Midrange Systems Technical Discussion'
Subject: RE: RUNRMTCMD question - service property (log on)
I have looked at the "Iseries Access for Windows Remote Command" service
property Logon tab.
I changed the "log on as" from "local system account" to "this account"
specifying the user and password I use to log on to the pc. I am getting
the following error:
"could not start the iseries access for windows remote command service
on local computer".
"error 1314: a required privilege is not held by the client"
This mailing list archive is Copyright 1997-2019 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact