Examples of using Computername parameter in English and their translations into German
{-}
-
Colloquial
-
Official
-
Ecclesiastic
-
Medicine
-
Financial
-
Ecclesiastic
-
Political
-
Computer
-
Programming
-
Official/political
-
Political
The following cmdlets have a ComputerName parameter.
ComputerName parameter is sufficient for most commands.
No. Several cmdlets have a ComputerName parameter that lets.
The ComputerName parameter is not necessary when connecting to the local system.
Instead, the command uses the ComputerName parameter to indicate the computers.
ComputerName parameter or in a PSSession by using the Session parameter. .
But, the second command fails because when you use the ComputerName parameter, Windows PowerShell creates a connection just to run the command.
The ComputerName parameters of the New-PSSession, Enter-PSSession and Invoke-Command cmdlets accept an IP address as a valid value.
Many other cmdlets that get data from remote computers, such as Get-Process, Get-Service, Get-EventLog,and Get-WmiObject have only a ComputerName parameter.
You can use the ComputerName parameter to start a temporary session.
C:\PS> $s1, $s2, $s3 new-session-computername server1,server2,server3 This command creates three new PSSessions,one on each of the computers specified by the ComputerName parameter.
Have a ComputerName parameter that gets the objects on a remote computer.
The property has the same name as the parameter, or the property has the same alias as the parameter. For example,if the function has a ComputerName parameter, and the piped object has a ComputerName property, the value of the ComputerName property is assigned to the ComputerName parameter of the function.
Because the ComputerName parameter is specified, the command runs against the remote server01 computer.
Invoke-command-computername Server01-scriptblock{get-culture} The ComputerName parameter is designed for situation in which you run a single command or several unrelated commands on one or many computers.
ComputerName parameter to perform a template export(or import) on a remote computer, the templates are written to(or copied from) an XML file on the local computer.
These Service cmdlets do not have a ComputerName parameter, but you can run them on a remote computer by using the Invoke-Command cmdlet.
The ComputerName parameter of the Invoke-Command cmdlet accepts multiple computer names, and the Session parameter accepts multiple PSSessions.
Many Windows PowerShell cmdlets have a ComputerName parameter that enables you to collect data and change settings one or more remote computers.
The ComputerName parameter accepts multiple values and wildcard characters, so you can get the services on multiple computers with a single command.
You can use the ComputerName parameter even if your computer is not configured to run remote commands.
You can use the ComputerName parameter of Get-Process even if your computer is not configured to run remote commands.
In the following example, the ComputerName parameter can contain a value of Null even though this parameter is a mandatory parameter. .
In the following example, the ComputerName parameter can contain an empty string("") even though this parameter is a mandatory parameter. .
When you use the ComputerName parameter, Windows PowerShell creates a temporary connection that is used only to run the specified command and is then closed.
When you use the ComputerName parameter, Windows PowerShell creates a temporary connection that is used for the interactive session or for a single command and is then closed.
Because the ComputerName parameter of Get-Service does not use Windows PowerShell remoting, you can use this parameter even if the computer is not configured for remoting in Windows PowerShell.