Improve this question. Add a comment. Active Oldest Votes. Improve this answer. Mathias R. Jessen Mathias R. Jessen From this relevant blog post by Margosis : Having said all that, there is a Local Security Policy option to change the behavior of the elevation prompt for Administrators to "elevate without prompting".
Ryan Ries Ryan Ries Then Now when you right click a program in the start menu you will get the pop-up with the options like "Run as administrator", "Pin to Taskbar", etc. Now you just have to remember to start your PowerShell or cmd window with Run as Administrator.
Ray Ray Sign up or log in Sign up using Google. Sign up using Facebook. Some items, such as the Printers folder and desktop items, are opened indirectly and cannot be started with the runas command. If the runas command fails, the Secondary Logon service might not be running or the user account you are using might not be valid. To test the user account, try logging on to the appropriate domain using the account.
Group Policy is not processed for the user whose credentials are supplied to the runas command. This is by design. The runas command can load the user profile of the secondary user whose identity is being used to create the process, and that user profile may contain registry keys and values from previous interactive logons when Group Policy was processed for that user. User GPO is only processed for users who log on interactively to their own desktops by using the logon user interface.
The following command starts an instance of the command prompt as an administrator on the local computer:. The following command starts an instance of a command prompt window, saved MMC console, Control Panel item, or program that will administer a server in another forest:. When prompted, type the account password. Remove From My Forums. Answered by:. Archived Forums. Directory Services. Sign in to vote. Hi I am currently going through the microsoft academic courseware book for 2k8 active directory and I am doing the lab 6.
This RunAs functionality allows you to logon to a server with low level permissions and still run programs that require higher permissions, thereby keeping your server safe and happy. The only problem with ShellRunAs is that it is a per user installation. That means that it needs to be "installed" for each user on the server. This can be a real problem for servers where a lot of different people logon, such as a Terminal Server.
0コメント