The New-CimSession cmdlet creates a CIM session. A CIM session is a client-side object representing a connection to a local computer or a remote computer. The CIM session contains information about the connection, such as ComputerName, the protocol used for the connection, session ID and instance ID.

This cmdlet returns a CIM session object that can be used by all other CIM cmdlets.

You cannot use the NtlmDomain authentication type for connection to the local computer. CredSSP authentication is available only in firstref_vista, firstref_longhorn, and later versions of Windows.

Caution: Credential Security Service Provider (CredSSP) authentication, in which the user’s credentials are passed to a remote computer to be authenticated, is designed for commands that require authentication on more than one resource, such as accessing a remote network share. This mechanism increases the security risk of the remote operation. If the remote computer is compromised, the credentials that are passed to it can be used to control the network session.

By default, the value of this parameter is 0, which means that the cmdlet uses the default timeout value for the server.

If the OperationTimeoutSec parameter is set to a value less than the robust connection retry timeout of 3 minutes, network failures that last more than the value of the OperationTimeoutSec parameter are not recoverable, because the operation on the server times out before the client can reconnect.

Specifies the network port on the remote computer that is used for this connection. To connect to a remote computer, the remote computer must be listening on the port that the connection uses. The default ports are 5985 (the WinRM port for HTTP) and 5986 (the WinRM port for HTTPS).

Before using an alternate port, you must configure the WinRM listener on the remote computer to listen at that port. Use the following commands to configure the listener:

Do not use the Port parameter unless you must. The port setting in the command applies to all computers or sessions on which the command runs. An alternate port setting might prevent the command from running on all computers.

By default, the New-CimSession cmdlet establishes a connection with a remote WS-Management endpoint for two reasons: to verify that the remote server is listening on the port number that is specified by using the Port parameter, and to verify the specified account credentials. The verification is accomplished by using a standard WS-Identity operation. You can add the SkipTestConnection switch parameter if the remote WS-Management endpoint cannot use WS-Identify, or if you want to reduce some data transmission time.

Inputs

Outputs

Examples

This command creates a local CIM session with default options. If ComputerName is not specified, New-CimSession creates a DCOM session to the local computer.

Create a CIM session to a specific computer:

PS C:> New-CimSession -ComputerName Server01

This command creates a CIM session to the computer specified by ComputerName. By default, New-CimSession creates a WsMan session when ComputerName is specified.

Create a CIM session to multiple computers:

PS C:> New-CimSession -ComputerName Server01,Server02,Server03

This command creates a CIM session to each of the computers specified by ComputerName, in the comma separated list.

Create a CIM session with a friendly name:

Then you can use the friendly name of a CIM session to easily refer to the session in other CIM cmdlets, for example, Get-CimSession.PS C:> New-CimSession -ComputerName Server01,Server02 -Name FileServers
PS C:> Get-CimSession -Name File*

This command creates a remote CIM session on each of the computer specified by ComputerName, in the comma separated list, and assigns a friendly name to the new sessions, by specifying Name.