Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from http://cloud.google.com/compute/docs/instances/windows/connecting-powershell below:

Connect to Windows VMs using PowerShell | Compute Engine Documentation

Stay organized with collections Save and categorize content based on your preferences.

Windows

This document describes how to connect to a Windows virtual machine (VM) instance by using PowerShell.

• If you haven't already, then set up authentication. Authentication is the process by which your identity is verified for access to Google Cloud services and APIs. To run code or samples from a local development environment, you can authenticate to Compute Engine by selecting one of the following options:

  Select the tab for how you plan to use the samples on this page:

  Console

  When you use the Google Cloud console to access Google Cloud services and APIs, you don't need to set up authentication.

  gcloud

  1. Install the Google Cloud CLI. After installation, initialize the Google Cloud CLI by running the following command:

     gcloud init

     If you're using an external identity provider (IdP), you must first sign in to the gcloud CLI with your federated identity.

     Note: If you installed the gcloud CLI previously, make sure you have the latest version by running gcloud components update.
  2. Set a default region and zone.

If you have a Windows workstation with PowerShell, you can connect to your Windows Server instances through a remote PowerShell session.

1. If you have not created a username and password on the remote Windows instance yet, create or reset your Windows password.

2. Add a firewall rule that opens port 5986 on the Google Cloud VPC network where your Windows Server instance is located.

3. On your local workstation, open the PowerShell terminal.

4. Optional: You can initialize a variable to hold your user credentials so you do not need to enter them each time you connect to the instance. If you skip this step, you receive a prompt for your username and password later.

   $credentials = Get-Credential
   

5. Choose whether you want to establish an interactive Powershell session, or invoke commands on your Windows Server VM remotely.

To establish a PowerShell session, run the following command:

Enter-PSSession -ComputerName IP_ADDRESS -UseSSL -SessionOption (New-PSSessionOption -SkipCACheck -SkipCNCheck) -Credential $credentials

Replace IP_ADDRESS with the external IP address, DNS name, or Windows computer name for the instance to which you want to connect.

After you connect, the command prompt changes to include the IP address of the remote Windows instance. You can now use the terminal to run PowerShell commands on the remote Windows Server instance.

As an alternative to the Enter-PSSession command, you can run Invoke-Command with the -ScriptBlock flag to execute PowerShell commands on the remote instance without establishing an interactive session.

Invoke-Command -ComputerName IP_ADDRESS -ScriptBlock { SCRIPT } -UseSSL -SessionOption (New-PSSessionOption -SkipCACheck -SkipCNCheck) -Credential $credentials

Replace the following:

• IP_ADDRESS: the IP address, DNS name, or Windows computer name for the instance to which you want to connect.
• SCRIPT: one or more commands to run on the remote instance. For example, specify Get-EventLog -log "Windows PowerShell" to get a list of log events.

• Learn how to manage access to instances for multiple users across a project or organization.
• Securely connect to VM instances.
• Transfer files to your Linux instances.

Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License, and code samples are licensed under the Apache 2.0 License. For details, see the Google Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.

Last updated 2025-08-07 UTC.

[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-07 UTC."],[[["This document guides you through connecting to a Windows virtual machine (VM) instance using PowerShell, enabling remote management and command execution."],["Before connecting, ensure you have set up authentication via the Google Cloud CLI or are using the Google Cloud console, and have created or reset your Windows password on the remote instance."],["Connecting to a Windows Server instance requires opening port 5986 in your Google Cloud VPC network's firewall rules, in order to accept remote PowerShell connections."],["You can establish either an interactive PowerShell session using `Enter-PSSession` or remotely invoke commands on the VM without an interactive session by using the `Invoke-Command` method."],["When a user connects to a VM, they can utilize all IAM permissions granted to the service account attached to that specific VM."]]],[]]

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4