There is no mention of this in the OP's question, although I believe you might be wrong. In that case, my answer is not salvageable with editing.
PowerShell does have -Credentials switch but going that way leads to what runas already does. Blerg Blerg 1, 6 6 silver badges 17 17 bronze badges. Eric D Eric D 1 1 1 bronze badge. Can you provide more specifics regarding what the user should look for?
Sign up or log in Sign up using Google. Sign up using Facebook. Sign up using Email and Password. Post as a guest Name. Email Required, but never shown. The Overflow Blog. Stack Gives Back Safety in numbers: crowdsourcing data on nefarious IP addresses. Featured on Meta. New post summary designs on greatest hits now, everywhere else eventually. Linked Related 3. I hope this will provide you the assistance that you require. Please feel free to contact Microsoft Community for Windows related queries.
Was this reply helpful? Yes No. Sorry this didn't help. Thanks for your feedback. Reading time: less than 1 minute Often comes across to give administrative permissions to ordinary user in certain software.
Related posts. Next Post 5. Nothing to see here! Good afternoon, When you do this in other shortcuts, for the first time, the system will ask the administrator password; only the command will not give permission, the first time you run the shortcut with this command you have to put the admin user password, or the user password that you used the command. I think they wanted to say the following about the security breach: -Open shortcut properties for which runas with a saved password has been configured -Change the path that is there to the path of any other installed program but without a saved password or even any executable that hasn't even been installed yet.
Because its a job that needs to run each weekday it needs to run without human intervention. For the first week it ran fine, then on the Monday one week later I noticed the job had failed. In the windows task manager the user account used for the job was stuck on the RunAs.
About a week later the same thing happended again, and then it happend a third time after only 3 days.
In all this time the password has not expired or been changed, in fact to get it going again all I have to do is log on as the account and re-confirm the password.
For an automatted job this is not a solution. I've run the gpresult command and studied the output, but can find nothing out of the oridinary or justification for the cached credentials expiring. I am afraid it is difficult to help. Partly it is by lack of basic information about system used and configuration. Do not expect we could give you advice for Windows , , R2, and R2. TEN years from now is , which means Windows Is this true?
Are you using this operating system now? Please attach files as requested - this may make the problem solved sooner.
0コメント