Examples of using These cmdlets in English and their translations into Portuguese
{-}
-
Colloquial
-
Official
-
Medicine
-
Financial
-
Ecclesiastic
-
Ecclesiastic
-
Computer
-
Official/political
To find these cmdlets in your session, type.
For more information about these cmdlets, type the following command.
These cmdlets share two important characteristics.
For information about these cmdlets, see the cmdlet help topic for each cmdlet.
These cmdlets do not use Windows PowerShell remoting.
To import the modules that are created by these cmdlets, either by using Import-PSSession or Import-Module, the execution policy in the current session cannot be Restricted or AllSigned.
These cmdlets let you create and manage persistent connections.
For more information about andexamples of how to use any of these cmdlets, in a Windows PowerShell session into which the Server Manager module is loaded, enter Get-Help cmdlet_name-full, in which cmdlet_name represents one of the following values.
These cmdlets let you manage the breakpoints and display the call stack.
When you use these cmdlets, you do not need to specify the Alias: drive in the name.
If these cmdlets are not included in the session configuration on the remote computer, the Enter-PSSession commands fails.
The objects that these cmdlets return store the name of the remote computer in the MachineName property.
Second, these cmdlets use the Windows PowerShell verb Out because they send information out from Windows PowerShell to somewhere else.
You can use these cmdlets to complete the end-to-end tasks necessary to manage local and remote computers.
These cmdlets are the same as the Export-CSV and Import-CSV cmdlets, except that they do not save the CSV strings in a file.
These cmdlets do not have a Session parameter, but you can use the Invoke-Command cmdlet to run these commands in a PSSession.
These cmdlets are the same as the ConvertTo-CSV and ConvertFrom-CSV cmdlets, except that they save the CSV strings in a file.
You can use these cmdlets to complete the end-to-end tasks necessary to manage WS-Management settings on local and remote computers.
These cmdlets do not use Windows PowerShell remoting, so you can use them even on computers that are not configured for remoting in Windows PowerShell.
Because these cmdlets do not use WS-Management-based Windows PowerShell remoting, you can use the ComputerName parameter of these cmdlets on any computer that is running Windows PowerShell.