PowerShell's Get-Credential disappointed me. I had hoped that this
cmdlet
would 'capture' my current credentials and encrypt them. I now realize that
Get-Credential has a different purpose, which is to supply a dialog box for us to enter an
alternative name
and its password.
A typical scenario for Get-Credential, is when you are logged on as
ordinary user and you need the credentials of an administrator so that the
rest of the PowerShell script will execute successfully. You may wish
to append the -credential parameter followed by the name of a user account
with more rights.
Get-Credential -credential administrator # A dialog box should appear
populated with administrator # See screenshot above
Note 1: Most people put the user name
"administrator" in double quotes.
Note 2: As with all PowerShell nouns, remember
that credential is singular.
The point of this example, in fact the only reason for using
Get-Credential is that the current user has insufficient privileges to run
the rest of the PowerShell commands.
Note 1: If you were already logged on with
administrative privileges on the network computer it would be pointless to
add the Get-Credential code.
Note 2: This command won't work on your network
unless you change -Computer ExchSrv to the hostname of a machine on your
network. Incidentally, if the command still does not work try
disabling the firewall.
-ConsolePrompting
The idea of adding this registry setting is twofold, firstly to suppress the
credential dialog box, secondly so that you can type the username and
password at the command line.
While this technique just would not work for me in Windows Server 2008 PowerShell v 2.0
(CTP3); it DID WORK in WINDOWS 7.
You have to imagine that you are now at the PowerShell command
prompt. When you type:
Get-Credential
You should get a line saying:
Supply values for the following parameters: Credential User:
Then when you type Administrator this is what you see:
Supply values for the following parameters: Credential User: Administrator Password for Administrator
Note 1: I say again, this did not work in Windows Server 2008, even though I could see
and control the ConsolePrompting key in the registry at:
HKLM:\SOFTWARE\Microsoft\PowerShell\1\ShellIds. And the value was set to
'True'.
Note 2: The above technique did work in Windows 7.
I kept it simple just launched the PowerShell command line and typed: Get-Credential. Incidentally, there is no need to type a -ConsolePromting
switch.
# This is wrong Get-Credential -consolePrompting
Guy Recommends: Solarwinds' Free Bulk Import Tool
Import users from a spreadsheet. Just provide a list of the
users with their fields in the
top row, and save as .csv file. Then launch this FREE utility and match
your fields with AD's
attributes, click to import the users. Optionally, you can
provide the name of the OU where the new accounts will be born.
There are also two bonus tools in this free download, and all 3 have been approved by Microsoft:
The dialog box says it all. If a PowerShell script needs elevated
privileges - administrative rights, then include the Get-Credential code to
collect the relevant information.
If you like this page then please share it with your friends
See more PowerShell examples for Shutdown commands
Please email me if you have a better example script. Also please report any factual mistakes, grammatical errors or broken links, I will be happy to correct the fault.
Windows Management Instrumentation (WMI) is one of the hidden
treasures of Microsoft operating systems.
Fortunately, Solarwinds
have created the
Free WMI Monitor so that you can actually see and understand these gems of
performance information. Take the guess work out of which
WMI counters to use for applications like Microsoft Active Directory,
SQL or Exchange Server.
