Compute Engine: Qwik Start - Windows (GSP093) Lab Walkthrough | Create a Windows Server VM and Connect with RDP

Windows Server is still the backbone of a huge number of company systems. It powers Active Directory, SQL Server, .NET applications, file servers, remote work desktops and a long list of legacy business software that is not going away any time soon. The good news is that you no longer need to buy hardware, rack it in a server room or install an operating system from a disc to run it. On Google Cloud, you can have a Windows Server virtual machine up and running in a few minutes, and the Compute Engine: Qwik Start - Windows (GSP093) lab on Google Cloud Skills Boost is one of the fastest ways to learn how.

The lab itself is short, usually around fifteen minutes. You create a Windows virtual machine, wait for it to finish booting, generate a password, and connect to its desktop using Remote Desktop Protocol (RDP). It sounds simple, but those few steps touch several ideas that every cloud beginner needs to understand: machine types, boot disks, regions and zones, firewall rules, serial port logs, credentials and remote access. If you only click through the instructions, you will finish the lab but may not remember anything a week later. If you understand why each step exists, the knowledge sticks and carries over to every other Compute Engine task you do.

This post walks through the entire lab step by step and explains what each setting actually does. It also covers common errors, security habits, cost awareness, real-world use cases and answers to frequently asked questions. Watch the full video walkthrough below first, then keep this page open as a reference while you complete the lab yourself.

Introduction: Why Windows on Compute Engine?
Lab Details at a Glance
What You Will Learn
Before You Start: Prerequisites and Setup Tips
Key Concepts Explained Simply
Step-by-Step: Complete the GSP093 Lab
What Happens Behind the Scenes
Common Problems and How to Fix Them
Windows VM vs Linux VM on Compute Engine
Cost and Licensing Basics
Security Best Practices for Windows VMs
Real-World Use Cases
Why This Lab Matters for Your Cloud Career
Quick Glossary
Frequently Asked Questions
Conclusion and Next Steps

Introduction: Why Windows on Compute Engine?

Compute Engine is Google Cloud's Infrastructure as a Service (IaaS) offering. It lets you create virtual machines that run on Google's global infrastructure and pay only for the resources you use. Most people think of Linux when they hear the words "cloud VM", but Compute Engine supports Windows Server images as well, and the operating system license is handled for you as part of the VM pricing.

That matters in real projects. Companies move Windows workloads to the cloud for many reasons: to host internal applications, to run build agents and test software on Windows, to set up secure remote desktops, to migrate old on-premises servers without rewriting the software on them, or simply to scale up and down without buying new machines. Whether you plan to become a cloud engineer, a DevOps engineer, a system administrator or a solutions architect, knowing how to launch and reach a Windows VM is a basic skill you will use again and again.

The Qwik Start format of Google Cloud Skills Boost is designed for exactly this kind of first contact. You get a temporary Google Cloud project, temporary credentials and a set of guided tasks. There is no risk of breaking anything and no bill to worry about, which makes it a perfect place to experiment.

Lab Details at a Glance

Lab Name	Compute Engine: Qwik Start - Windows
Lab ID	GSP093
Platform	Google Cloud Skills Boost
Level	Introductory
Duration	About 15 minutes
Main Skills	Create a Windows VM, configure it, connect with RDP
Tools Used	Google Cloud Console, Cloud Shell (optional), RDP client
Cost	Uses temporary lab credentials, no personal billing

What You Will Learn

How to create a Windows Server virtual machine in Compute Engine
How to choose a machine type, boot disk image and firewall options
How regions and zones affect where your VM runs
How to check that the VM has finished booting by reading the serial port output
How to generate Windows login credentials for your instance
How to connect to the VM desktop using Remote Desktop Protocol (RDP)
How to confirm your progress inside Google Cloud Skills Boost
The basic building blocks of Google Compute Engine

Before You Start: Prerequisites and Setup Tips

You do not need any prior cloud experience for this lab, but a few preparation steps will save you time and frustration.

Use the lab credentials only. Skills Boost gives you a temporary username and password in the left panel. Do not sign in with your personal or work Google account, because that can cause permission conflicts and failed progress checks.
Open the lab in an Incognito or private window. This keeps your personal Google session separate from the lab session and avoids the endless login loop many learners run into.
Click Start Lab and wait. The credentials, project ID and countdown timer appear only after the environment is ready. Do not rush ahead before they show up.
Prepare an RDP client. On Windows, the built-in Remote Desktop Connection app works well. On a Mac, install Microsoft Remote Desktop. On Linux, a client such as Remmina is a good option. If you use a Chromebook or prefer the browser, the lab may offer a Chrome-based RDP option.
Keep an eye on the timer. The lab is time-limited. Fifteen minutes of work usually fits comfortably, but do not leave the lab idle while you do other things.
Check your internet connection. RDP needs a stable connection. A weak connection can make the desktop laggy or cause it to disconnect.

Key Concepts Explained Simply

What is a Virtual Machine (VM)?

A VM is a computer that exists only as software. Google runs enormous numbers of physical servers in its data centers, and each one can host many virtual machines. Each VM behaves like a separate, complete computer with its own CPU, memory, disk and operating system. You get the power of a real server without owning any hardware.

What is Compute Engine?

Compute Engine is the Google Cloud service that creates and manages these virtual machines. You choose the operating system, the size of the machine, the location and the network settings, and Google handles the physical infrastructure underneath.

What is Remote Desktop Protocol (RDP)?

RDP is Microsoft's protocol for displaying a remote computer's desktop on your own screen. It listens on TCP port 3389 by default. When you connect, you can see the Windows desktop, move the mouse, type on the keyboard and run applications on the VM as if you were sitting in front of it.

What is a Boot Disk?

The boot disk holds the operating system and the files needed to start the machine. When you pick a Windows Server image, Compute Engine creates a persistent disk with that operating system preinstalled and attaches it to your VM. Because it is a persistent disk, its data survives even if you stop the VM.

What are Regions and Zones?

A region is a geographic area, such as Mumbai, Iowa or London. Each region contains several zones, which are separate data center locations within that area. When you create a VM you pick a zone. Choosing a region close to your users reduces latency, and spreading resources across zones improves reliability.

What is a Machine Type?

The machine type defines how many virtual CPUs and how much memory your VM gets. Small machine types are cheap and fine for learning. Larger ones are used for databases, applications and heavy workloads. Windows generally needs more memory than a minimal Linux server, so do not choose a machine that is too small in real projects.

What is a Firewall Rule?

Firewall rules control which network traffic is allowed to reach your VM. To connect with RDP, inbound traffic on port 3389 must be allowed. If that rule is missing or too restrictive, your connection will simply time out with no clear error message.

What is the Serial Port Output?

The serial port output is the VM's console log. It shows what the machine is doing while it starts up, including messages from the Windows setup process. It is the best place to check whether the VM is genuinely ready or still busy.

Step-by-Step: Complete the GSP093 Lab

Step 1: Sign in to the Google Cloud Console

Click Start Lab on the Skills Boost page. When the environment is ready, you will see a username, a password and a project ID in the left panel. Click Open Google Cloud Console, paste the username and password into the sign-in page, accept the terms of service, and skip any recovery option or free trial prompts that appear. You are now inside a temporary Google Cloud project created just for this lab.

Step 2: Open Compute Engine

In the Cloud Console, open the Navigation menu (the three horizontal lines at the top left) and go to Compute Engine, then VM instances. The first time you open this page, it may take a minute while the Compute Engine API is prepared. Wait until the Create instance button becomes active before continuing.

Step 3: Create the Windows VM

Click Create instance. This opens a form with several sections. Fill them in as your lab instructions say. The main settings you will deal with are:

Name: use the name given in the lab, or a simple descriptive one such as windows-vm. Names must be lowercase letters, numbers and hyphens.
Region and Zone: use the values provided by the lab. In real projects, pick the region closest to your users or the one required by your company policy.
Machine type: the lab uses a small general-purpose machine. This keeps resource usage low while still being enough to run Windows for a short demonstration.
Boot disk: click Change in the boot disk section, set the operating system to Windows Server, choose the Windows Server version specified in your lab (for example a Datacenter edition), and confirm with Select. The default boot disk is Linux, so this step is essential.
Firewall: tick the options to allow HTTP and HTTPS traffic if your lab instructions ask for them.

When everything matches the lab instructions, click Create. Your new VM appears in the list with a spinning icon. When the icon turns into a green check, Google has provisioned the machine. This is not the same as Windows being ready to log into, which is why the next step exists.

Step 4: Check That Windows Has Finished Booting

A green tick only tells you the VM exists and is running. Windows still needs a few minutes to complete its first-time setup, install drivers, and prepare the guest environment. You can watch this happening through the serial port output:

Click the VM name to open its details page.
Click Serial port 1 (console), or View logs depending on your console layout.
Scroll to the bottom of the log and look for a message saying the instance setup has finished and Windows is ready to use.

You can read the same log from Cloud Shell with a command like this (replace the name and zone with your own values):

gcloud compute instances get-serial-port-output INSTANCE_NAME --zone=YOUR_ZONE

Do not try to log in before the ready message appears. A large share of failed connection attempts happen simply because the learner was a minute or two too early. If the log still looks busy, wait and refresh it.

Step 5: Set the Windows Password

Windows VMs on Compute Engine do not come with a default password, which is a good security decision. Instead, you generate one yourself:

On the VM instances page, find the RDP dropdown next to your instance.
Choose Set Windows password.
Enter a username, or keep the suggested one, and click Set.
Copy the password shown in the dialog and store it somewhere safe. It is displayed only once.

The same task can be done from the command line:

gcloud compute reset-windows-password INSTANCE_NAME --zone=YOUR_ZONE --user=YOUR_USERNAME

Behind the scenes, Compute Engine uses an agent running inside the VM to create or reset the user account. The password is encrypted so that only the requester can read it.

Step 6: Connect with Remote Desktop (RDP)

Now comes the satisfying part. You have two common ways to connect, and your lab will point you to one of them:

RDP client on your computer: copy the VM's external IP address from the instance list, open Remote Desktop Connection on Windows (or Microsoft Remote Desktop on a Mac), paste the IP address, and sign in with the username and password you generated. You will see a certificate warning because the VM uses a self-signed certificate. For this lab it is safe to accept it.
Browser or Chrome-based RDP: if the lab recommends it, click RDP on the instance row and follow the prompt to connect straight from your browser without installing anything extra.

After a few seconds, the Windows Server desktop appears. You are now controlling a machine running in a Google data center from your own screen. Take a moment to look around. Open Server Manager, check the system information, and see how the operating system looks just like any other Windows Server installation.

Step 7: Check Your Progress and Finish the Lab

Go back to the Skills Boost lab page and click Check my progress for each task to confirm your work has been detected. Once every check shows a green tick, click End Lab. This deletes the temporary project and its resources, so you do not need to clean up anything manually.

What Happens Behind the Scenes

It helps to picture what Google Cloud does when you press the Create button. First, Compute Engine picks a physical host in the zone you selected that has enough free capacity. Next, it creates a persistent disk from the Windows Server image you chose and attaches it to a new virtual machine with the CPU and memory of your selected machine type. A virtual network interface is attached inside your project's default network, and an external IP address is assigned so that you can reach it from the internet.

When the VM starts, Windows runs its specialization process. During this phase, the Google guest environment for Windows is activated. This software lets the platform communicate with the VM, handle password resets, set up metadata access, and report status messages to the serial port. Only after these tasks complete does Windows accept RDP logins. This is why the serial port log is so useful: it shows exactly where the boot process currently stands.

Finally, when you click Set Windows password, the console sends a request through the guest agent. The agent creates the local user account, sets the password, and returns it in encrypted form. Your RDP client then connects to the VM's external IP on port 3389, and the firewall rules in your project's network decide whether that traffic is allowed through.

Common Problems and How to Fix Them

Problem	Likely Cause	Fix
RDP connection times out	Firewall blocks port 3389, or the VM is still booting	Check the serial port log for the ready message and confirm an inbound rule allows TCP 3389
Password incorrect error	Typed manually with an extra space, or an old password is being used	Copy and paste the generated password, or reset it again
Set Windows password option is missing	VM is not fully running yet	Wait for the green tick and refresh the page
Lab progress check fails	Wrong name, zone or image used	Recreate the VM exactly as the lab instructions specify
Console login loops	Conflict with your personal Google account	Use an Incognito window with the lab credentials only
Slow or laggy desktop	Small machine type or distant region	This is normal for lab-sized machines. Choose a larger type in real projects.
Create instance button is greyed out	Compute Engine API is still initializing	Wait one to two minutes and refresh the page
Certificate warning on connection	VM uses a self-signed certificate	Accept the warning for the lab. For production, install a trusted certificate.
Quota or resource error on creation	Selected zone has no available capacity	Try the zone specified in the lab, or switch to another zone in the same region

A Simple Troubleshooting Checklist

Is the VM showing a green check in the instance list?
Does the serial port log say that Windows is ready?
Did you generate a password and copy it correctly?
Are you using the VM's external IP address, not the internal one?
Does a firewall rule allow inbound TCP 3389?
Is your own network or company firewall blocking outgoing RDP traffic?

If all six answers are yes and the connection still fails, restart the VM from the console, wait for it to boot completely, and try again.

Windows VM vs Linux VM on Compute Engine

If you have already done a Linux VM lab, you will notice that creating the machine is almost identical. The differences appear in how you configure and reach it.

Feature	Windows VM	Linux VM
Boot disk image	Windows Server	Debian, Ubuntu, Rocky Linux and others
Remote access	RDP on port 3389	SSH on port 22
Initial login	Generate a password first	SSH keys managed automatically
Interface	Graphical desktop	Command line by default
Typical memory need	Higher	Lower
Licensing	Included in VM pricing	Usually free for open source images
Common workloads	.NET apps, SQL Server, Active Directory	Web servers, containers, open source stacks

Cost and Licensing Basics

In the lab, you do not pay anything because Google Cloud Skills Boost covers the resources. In your own project, cost is a very important consideration. A Windows VM costs more than a comparable Linux VM because the price includes the Windows Server license. You are billed for the machine type, the boot disk size, any additional storage, network egress and the Windows license fee.

A few habits help keep costs under control:

Stop VMs you are not using. A stopped VM does not incur compute charges, although its disks still cost a small amount.
Delete resources after practice. Remove the VM, extra disks and unused static IP addresses.
Right-size your machines. Start small and scale up only if performance requires it.
Use budgets and alerts. Set a budget in Google Cloud Billing so you receive an email before costs surprise you.
Check the pricing calculator. Always estimate costs with Google's official pricing tools before running Windows workloads for long periods.

Pricing changes over time, so always confirm current figures on the official Google Cloud pricing pages instead of relying on numbers you saw in an older tutorial.

Security Best Practices for Windows VMs

The lab is a safe, controlled environment. In real projects, exposing RDP to the entire internet is risky, because port 3389 is one of the most frequently attacked ports online. Automated bots constantly scan for open RDP servers and try common passwords. Keep these habits in mind:

Restrict the source IP range in the firewall rule to your own address or your office network, instead of allowing 0.0.0.0/0.
Use strong, unique passwords and rotate them regularly.
Consider Identity-Aware Proxy (IAP) TCP forwarding or a VPN so that RDP is never open to the public internet.
Keep Windows updated with the latest security patches.
Avoid using the built-in Administrator account for daily work. Create standard users where possible.
Enable logging and monitoring so that you can detect unusual login attempts.
Take snapshots of important disks so that you can recover quickly if something goes wrong.
Stop or delete VMs you do not need, which reduces both cost and attack surface.

Only use these techniques on cloud resources that you own or are authorized to access.

Real-World Use Cases

Once you can launch and connect to a Windows VM, a wide range of practical scenarios opens up:

Hosting .NET and IIS applications: run internal tools or customer-facing sites built on the Microsoft stack.
Running SQL Server: host databases that existing applications depend on.
Active Directory and identity services: deploy domain controllers for companies that use Windows-based authentication.
Remote workstations: give developers or analysts a powerful Windows desktop they can reach from any laptop.
Testing and build servers: run automated builds, UI tests and compatibility checks on Windows.
Lift-and-shift migrations: move old on-premises Windows servers to the cloud with minimal changes.
Training and demos: spin up a clean Windows environment for a class, delete it afterwards, and start fresh next time.

Why This Lab Matters for Your Cloud Career

It looks like a beginner exercise, but the skills carry straight into bigger tasks. Creating a VM teaches you about compute, storage and networking all at once. Reading the serial console teaches basic troubleshooting. Setting credentials teaches you how cloud platforms handle authentication. Connecting over RDP is something you will do repeatedly as a cloud engineer or support engineer.

If you are preparing for a certification such as Google Cloud Associate Cloud Engineer or the Cloud Digital Leader exam, Compute Engine is a core topic, and hands-on practice like this makes the theory far easier to remember. Interviewers also love practical questions such as "How would you connect to a Windows VM in the cloud?" or "Why can't I RDP into my instance?" After finishing this lab, you will be able to answer both confidently.

Quick Glossary

Term	Meaning
IaaS	Infrastructure as a Service, where you rent virtual servers, storage and networks
Instance	Another word for a virtual machine in Compute Engine
External IP	The public address used to reach the VM from the internet
Internal IP	The private address used inside your Google Cloud network
Persistent Disk	Durable block storage that holds the VM's operating system and data
Guest Agent	Software inside the VM that talks to Google Cloud for tasks like password resets
RDP	Remote Desktop Protocol used to view and control a Windows desktop remotely
Serial Port Output	The console log that shows boot and startup messages

Frequently Asked Questions

How long does the GSP093 lab take?

The estimated time is 15 minutes. Most of that is spent waiting for the VM to boot and for Windows to finish its first-time setup.

Do I need a credit card or my own Google Cloud account?

No. Google Cloud Skills Boost provides temporary credentials and a temporary project for the lab. You should not use your personal account for it.

Why can't I log in right after the VM is created?

Windows needs a few minutes to complete setup after the VM shows as running. Check the serial port output for the ready message before trying to connect.

What port does RDP use?

RDP uses TCP port 3389 by default.

Can I use a Mac or Linux computer to connect?

Yes. Install the Microsoft Remote Desktop app on a Mac, or a client such as Remmina on Linux. Use the VM's external IP address, the username and the generated password.

Is it free to run Windows VMs in my own project?

No. Windows VMs include a licensing cost on top of normal compute charges, so always check Google Cloud's current pricing and delete resources you no longer need.

What is the difference between this lab and a Linux VM lab?

The main differences are the boot disk image, the need to generate a Windows password, and using RDP instead of SSH for access.

Why did my progress check fail even though I created the VM?

The most common reasons are using a different VM name, zone or operating system image than the lab requires. Re-read the task instructions carefully and recreate the VM if needed.

What should I do after finishing this lab?

Try other Qwik Start labs, such as Cloud Storage or Cloud Shell, then move on to topics like instance templates, managed instance groups, load balancing and VPC networking.

Can I install software on the Windows VM?

Yes, in a normal project you can install applications, enable Windows roles such as IIS, and configure the server just like any physical Windows Server. In the lab, simply follow the given tasks.

Conclusion and Next Steps

In the Compute Engine: Qwik Start - Windows (GSP093) lab, you learned how to launch a Windows Server VM, confirm it is ready, generate credentials and connect through Remote Desktop. These are the same steps real cloud teams use every day, just at a smaller scale. You also saw how regions, machine types, boot disks, firewall rules and serial port logs fit together, which gives you a solid base for everything else in Google Cloud.

Once you are comfortable with these basics, you can move on to more advanced topics such as custom machine types, startup scripts, instance templates, managed instance groups, load balancing, snapshots and secure access with Identity-Aware Proxy. Every one of them builds on the exact skills you practiced here.

If this walkthrough helped you, watch the full video above, like it and subscribe on YouTube for more Google Cloud Skills Boost lab tutorials. Leave a comment below if you got stuck on any step, and I will do my best to help.

Keep learning: explore more labs on this blog, including the Cloud Storage: Qwik Start - Console (GSP073) walkthrough and the Cloud Storage: Qwik Start - CLI/SDK (GSP074) lab solution.

Disclaimer: This post is created for educational and learning purposes only. The cloud environment and resources shown are part of a controlled training lab. Please use the commands and configurations only on cloud resources that you own or are authorized to access. This content is not affiliated with or endorsed by Google Cloud unless explicitly stated.

#googlecloud #googlecloudskillsboost #computeengine #windowsserver #gcp #cloudcomputing #GSP093 #GoogleCloudTutorial