When using PowerShell, Objects play a really important and fundamental role in how the system operates and interacts with data. They form the core of PowerShell’s ability to manage and manipulate information effectively. Then, moving beyond just understanding Objects, we also encounter the third key concept that is essential to grasp for working efficiently in PowerShell environments, Get-Member.

When using Get-Member, we often encounter hidden properties.

What does that mean?

When running a cmdlet in PowerShell, we typically see only the information Microsoft intends for us to view initially.

Here’s an example:

I ran Get-ChildItem on my Code folder.

The output is an object featuring properties like Mode, LastWriteTime, Length, and Name.

However, this object contains many more properties beyond these.

To discover all the properties, pipe the cmdlet to Get-Member as follows:

Get-ChildItem -Path C:\Code | Get-Member

Get-ChildItem -Path C:\Code | Get-Member

Then I will get two lists of information about two different types of objects.
This is because I have both files and folders in my C:\Code folder.

System.IO.DirectoryInfo and System.IO.FileInfo

And we will see both methods and different properties.
To only see the properties we can do like this:

Get-ChildItem -Path C:\Code | Get-Member -MemberType Properties

Get-ChildItem -Path C:\Code | Get-Member -MemberType Properties

The same thing happens for almost all cmdlets.

If we do the same thing with Get-Service.

Get-Service

Get-Service

Then we only see Status, Name and DisplayName.

But if we use Get-Member again we can se more properties for Get-Service.

Get-Service | Get-Member -MemberType Properties

Get-Service | Get-Member -MemberType Properties

The last two errors are normal; some services cannot be accessed.

This section of the summer tips series demonstrates in detail how to find and explore object properties using the Get-Member cmdlet. In upcoming parts of the series, I will also explain how to display additional properties beyond the default set that are initially shown. This will help you gain a deeper understanding of object properties and how to customize the output according to your needs.

The post PowerShell Summer Tips part 3 – Get-Member first appeared on The PowerAdmin.

Last edited: 2025-07-23

It’s been nearly a month since the PSConf EU conference took place in Malmö.
The event was truly an excellent conference, featuring a wide range of engaging speakers and attracting many wonderful people from the community.

I had the opportunity to attend, and I gained a tremendous amount of knowledge.
In fact, I learned far more than I ever did during a traditional PowerShell training course.

Here are my reflections and thoughts based on my experience at the conference.

The hard thing was not to find good sessions with good speakers. The hard part was to chose what to miss every time attending a session.

The quote came from one of the attendees, and it was truly insightful.

In total, there were more than 100 sessions.

The best way to explore all the conference videos is to watch them online on YouTube. They can be found here.

Not all sessions are available online yet, but 34 sessions are already accessible.

I have reflected on all the sessions I attended and will share my insights here as well as in a PowerPoint presentation.

The conference took place from June 23-26, 2025. I traveled to Malmö a day early by train from Stockholm.

The conference is about the sessions and to meet people with the same passion for PowerShell.

This was my third time attending, but I missed some community activities this year because I was tired from working so much. Next time, I need to be more active and engaged. There’s great value in catching up with old community friends who share my passion for PowerShell and meeting new people.

A huge thank you to all people behind PowerShell Conference Europe.
You are doing a super good job with everything.

It’s always super fun to listen to the PowerShell team about PowerShell related news.

The Powerpoint presentation
The video

Nice information about WinGet

WinGet DSC Samples
The video

It’s always interesting to learn more about stuff that I already knows about.
You will always learn more. And this session was great in that way.

The code
The video

A great session about modules.

The code and slides
The video

It was a truly enjoyable and pleasant first day at the conference, where I had the wonderful opportunity to meet both new faces and reconnect with old community friends. The atmosphere was warm and welcoming, making it a great start to the event.
The sessions were especially impressive and engaging! Every single session throughout all the days of the conference was well-organized and informative, offering valuable insights and knowledge. Overall, it was a fantastic experience from start to finish.

It’s always really great and quite interesting to get the chance to see what other people are doing when it comes to application installations and related setups like those. Observing different approaches and techniques can be very insightful and helpful.

The code
The video

This was an incredibly valuable and enriching session for me. I truly love attending this conference because it often surprises me; you might walk in thinking you already know a great deal about a particular subject, but then you participate in a session and realize how much more there is to discover. After each session, I am reminded once again that learning is a lifelong journey, and no matter how much knowledge you accumulate, there will always be new insights and information to absorb as long as you live.

I have been using Visual Studio Code for a long time and teaching others how to use it. Now, I have an even deeper understanding of it!

The Powerpoint presentation
The video

Nice information about migrating to PowerShell 7

The video

This was a great session about types in PowerShell.
I’m not a developer, but I really enjoy these kinds of sessions.
They always help me gain a deeper understanding of why things are done in a particular way.

The video

This was an excellent session on a topic I frequently use, though I’ve always felt a bit apprehensive about it.

James did an excellent job demonstrating how simple it can be and showing exactly how you should approach it.

The video

A nice presentation about what you can do with parameters.

The code
The video

A nice presentation about the new AI Shell.

The Powerpoint presentation

Day 2 was also a very good day filled with many positive experiences. There were numerous new things to learn and discover throughout the day, making it both exciting and enriching. The opportunity to gain fresh knowledge kept the day engaging and rewarding.

I really enjoyed this session a great deal because I have been meaning to use Pester more frequently in my work. This session provided me with a helpful and motivating push in the right direction, encouraging me to incorporate Pester into my routine.

A really nice session overall, and it provided me with another important area where I definitely need to improve and do better in the future.

The code and Powerpoint presentation
The video

It’s always incredibly fun and enjoyable to listen to my friend Alexandar when he talks about various interesting topics.
In this particular session, he shares a number of insights and discoveries that he has come across, focusing on some aspects of Graph PowerShell that can sometimes be a bit tricky and challenging to understand.

The video

It’s exciting to discover a fresh approach to OS deployment.

The video

It is always incredibly fun and quite interesting to see the different ways that others have approached and tackled a problem that I have also worked with in the past. Observing these varied methods provides valuable insights and often sparks new ideas or perspectives.

PoShaKucha was a refreshing and enjoyable twist compared to a typical session format. The challenge of presenting within a strict time limit of 6 minutes and 40 seconds per speaker was quite demanding, yet every presenter rose to the occasion and delivered their content impressively well!

The last day of the conferense!

A really nice and insightful session about what exactly makes a Git commit good and effective.
I truly love attending these kinds of sessions because they help me remember the important practices I need to follow.

The video

Yet another great session by Fred. This time on what to think about when designing commands for PowerShell Pipeline.

The code and presentation
The video

This session stood out as one of the very best from the entire conference, and it might have even been the absolute best session overall. What made it particularly unique was that it was the only non-technical session offered, which provided a refreshing change of pace. It was truly enjoyable and valuable to hear perspectives and insights from others in a format that was different from the usual technical presentations.

The Powerpoint presentation

An insightful and engaging session focused on various effective strategies and best practices that you can implement to enhance the security of PowerShell 7. This session provides valuable information on how to make your PowerShell 7 environment significantly more secure and resilient against potential threats and vulnerabilities.

The code and presentation
The video

The community session offered a unique and refreshing format compared to traditional sessions. There were some excellent speakers who brought valuable insights and energy to the event. Each speaker was given less than 10 minutes to deliver their presentation, creating a fast-paced and engaging atmosphere. As soon as one speaker finished, the next session began immediately, keeping the momentum going without any delays.

This was my take aways from the conference.
It was a great conference and great sessions.

When all of the videos are online I will post my Powerpoint as well.

The post Thoughts from PowerShell Conference Europe 2025 in Malmö first appeared on The PowerAdmin.

The second PowerShell command that you absolutely cannot live without is Get-Help, an essential tool for any PowerShell user.

In the first part of this series, we encountered the cmdlet Set-Culture while listing cmdlets for the International module.

If we want to obtain more detailed information about the Set-Culture cmdlet, we can do it in the following way:

Get-Help Set-Culture -Full

Get-Help Set-Culture -Full

The parameter -Full is used to display all help information.

However, if you haven’t worked with Get-Help before, you might encounter a minor issue or feature.

This is what you will see then.

PowerShell requires fetching the help information before you can use it.

This is simple, just run the following command in PowerShell with Administrator privileges:

Update-Help -Force

Update-Help -Force

If you are using another language then english you might run into some errors when doing this that will say something about trouble updating helpfiles for UI culture(s) {se-SV} or something like that.

Then try to add the parameter -UICulture with you culture.

Update-Help -UICulture se-SV -Force

Update-Help -UICulture se-SV -Force

If you write Get-Help Set-Culture again you should see little more information.

Usually, there is more help and additional examples available for a module.

Another way to use the help is with the parameter -Online.

Get-Help Set-Culture -Online

Get-Help Set-Culture -Online

This will open your default browser with the online version of the help.

In some cases you can get some extra information this way.
At least it’s easier to follow links for more information.

Next blog post in this series is about Get-Member.

The post PowerShell Summer Tips part 2 – Get-Help first appeared on The PowerAdmin.

Master PowerShell This Summer: Essential Tips for Using Get-Command Like a Pro

Back in 2018, I wrote a series of blog posts focused on the fundamental PowerShell commands that every user should know.
These are the essential cmdlets that you truly can’t live without when working in PowerShell.

Now, I have revamped and updated this article series, and I will begin by diving into the powerful and versatile Get-Command.

When you run Get-Command without any parameters, it returns all commands loaded in your PowerShell session. In my case, this lists a total of 1,791 commands.

Often, you don’t need to distinguish whether a command is an Alias, Function, Cmdlet, or Script—especially if your goal is simply to retrieve information or perform a task.

If you want to display only Cmdlets, you can use the -CommandType parameter with the value Cmdlet to filter the results accordingly.

Get-Command -CommandType Cmdlet

Get-Command -CommandType Cmdlet

Using this approach, I get 651 commands listed.

While this may not be the most precise method to find a specific command, it effectively narrows down the list.

Another way to get an smaller list is to use the parameter -Verb and then with Get or Set or another Verb.

Get-Command -Verb Get

Get-Command -Verb Get

With this approach, we will only list commands that provide us with information.

If we want more information about a specific cmdlet we can jus write:

Get-Command Get-TimeZone

Get-Command Get-TimeZone

If we want to know if there is other cmdlets for TimeZone usage we can use the parameter -Noun.

Get-Command -Noun TimeZone

Get-Command -Noun TimeZone

And if we know that we want to use some cmdlets that are a part of a module then we can do this:

Get-Command -Module International

Get-Command -Module International

To display all cmdlets that perform Set operations within the International module, simply use the following command:

Get-Command -Verb Set -Module International

Get-Command -Verb Set -Module International

This was a short summer blog post and I will be posting more basic PowerShell commands all summer long.

Next up is Get-Help, to go from listing commands to get help using them.

The post PowerShell Summer Tips part 1 – Get-Command first appeared on The PowerAdmin.

In my previous guide, I demonstrated the detailed process of how to download and install VirtualBox on your computer.

In this guide, I will walk you through the steps needed to set up a Windows 11 Lab Machine within VirtualBox.

Although setting up a Windows 11 virtual machine in VirtualBox requires a few more steps compared to the Quick Setup option available in Hyper-V, the process is still quite manageable and straightforward once you get familiar with it.

All the code and information provided on this website are offered “as is” without any guarantees or warranties of any kind. Although the code and information are tested, we do not warrant that the code is error-free or that it will meet your specific requirements. Use the code at your own risk. We disclaim all liability for any damages or losses arising from the use or inability to use the provided materials.

Download Windows 11

I will guide you through setting up an evaluation version of Windows 11, making the process simple and accessible for everyone. If you already have a licensed copy, you can use it as well.

In VirtualBox, you can install Windows 11 using an ISO file. You can download the ISO file here.

Simply scroll down to the section labeled “Download Windows 11 Disk Image (ISO) for x64 devices,” select your edition, click Download, and then press Confirm.

Next, select the language and click Confirm.

I have selected English International for this guide.

Just click 64-bit Download.

The download size is approximately 5.4GB.

Once the ISO has been downloaded, you can proceed to the next step.

Create Virtual Machine

In this step we will Create a Virtual Machine in Virtual Box.
Start VirtualBox and click on New.

Now you need to provide some information

Name: Windows 11 Lab Machine
Feel free to select any name you prefer!

Folder: The chosen folder is easy to use and you will have access to it.
Please ensure there is enough free space available on the hard drive!

ISO Image: Click the arrow on the right and select Other…
Then navigate to the ISO file you downloaded earlier.

Then click Open

Edition: Select from a variety of options available.
I choose Windows 11 pro for this guide.

Then click Next

VirtualBox facilitates unattended Guest OS installation.
Now, let’s provide some details.

Username: vboxuser is a solid option, but you can pick another if you prefer.
Password: Create a strong password and make sure to record it!
Product Key: Use the default key to obtain an evaluation copy
Hostname: I use Win11Lab01, you can choose another one, but the default name will not work.
Domain Name: Default will work for this Lab Machine.

VirtualBox Guest Additions are a set of drivers and system applications that enhance the performance and usability of virtual machines.

Next, click Next.

Then select the amount of memory and the number of virtual processors you’d like to allocate to this Virtual Machine.

The default settings are sufficient for most use cases.

Next, let’s create a Virtual Hard Drive. Simply click Next to continue.

Please ensure you have at least 80GB of free disk space available before proceeding!

When you click Next, you will see a Summary. Simply click Finish to complete the process.

The process to Create a new Virtual Machine will start.
But you need to Press any key to boot from CD or DVD…
Or you will get this prompt:

Choose the ISO file in the DVD drop down list and press Mount and Retry Boot.

This time, be sure to press any key (and tap the screen with the mouse first).

If the Product Key window appears, simply click I don’t have a product key.

Now the installation will start

When you see the screen below, please wait a moment for the initial setup to complete. Once ready, you can proceed.

You can now maximize the window for a better view.
Simply click the maximize button in the upper right corner.

On the right side of the screen, you may see the same information as shown in the picture above.

To remove it, click the icon on the right, as shown in the image below.

Now that the operating system installation is complete, we can move on to configuring the language settings.

Before that, we need to restart the Virtual Machine to be able to enable all features of the VirtualBox Guest Additions, such as copying and pasting between your computer and the Virtual Lab Machine.

After the restart, we need to enable the Shared Clipboard for this virtual machine and possibly activate Drag and Drop functionality between the host and guest operating systems.

We can do this in the menu under Devices.

Copy and Paste

I use Bidirectional to be able to Copy and Paste to and from the Lab Computer.

Drag and Drop

I use Bidirectional here too.

Take Snapshot

Before using the Lab Computer, it’s a good idea to create a snapshot that you can restore later if needed.

You can do this now or after setting the language.

To do this, go to the menu, select Machine, and then click Take Snapshot…

Name the Snapshot after what it is.
Like Clean Install

Now you can see the Snapshot name with your Virtual Machine.

Setup the lab computer

This step will show you how to set up the Windows Language settings as we want and install all tools needed for PowerShell and Visual Studio Code in the Lab Machine.

This is the same steps as in the guide how to setup a Lab Machine on Hyper-V.

Language

First, open PowerShell ISE as Administrator.

Click the arrow next to Script to open the Editor in PowerShell ISE.
Then close the Commands view on the right to have more space for scripting.

First of all I want to set all language settings to Swedish.
Just copy and past the code below and run it to do the changes.
You can do it bit by bit or all at once.

This can be done in different ways but I like my scripts to have more checks built in.
So this is not the easiest way

We start with a check for Run As Administrator and a Clear-Host.

# Check if the script is running with administrative privileges
#Requires -RunAsAdministrator

# Clear the terminal part
Clear-Host

Then we set the input method to Swedish if it is not already.

# Set the default input method to Swedish (Sweden) - Keyboard layout: Swedish
if ((Get-WinDefaultInputMethodOverride).InputMethodTip -ne "041D:0000041D") {
    Set-WinDefaultInputMethodOverride -InputTip "041D:0000041D"
}

If you want another input method you can look at the Default input profiles (input locales) in Windows page at Microsoft Learn for more language codes.

You just need to use the same language codes for the Get and for the Set.

And now we change the user language list to Swedish.

# Set the user language list to Swedish (Sweden)
if ((Get-WinUserLanguageList).LanguageTag -notcontains "sv-SE") {
    Set-WinUserLanguageList -LanguageList "sv-SE" -Force
}

For this one you will get this warning and it’s normal:

WARNING: If the Windows Display Language has changed, it will take effect after the next sign-in.

And to set the system locale to Swedish we write:

# Set the system locale to Swedish (Sweden)
if ((Get-WinSystemLocale).Name -ne "sv-SE") {
    Set-WinSystemLocale -SystemLocale "sv-SE"
}

Setting user locale to Swedish:

# Set the user locale to Swedish (Sweden)
if ((Get-Culture).Name -ne "sv-SE") {
    Set-Culture -CultureInfo "sv-SE"
}

Home location:

# Set the home location to Sweden
if ((Get-WinHomeLocation).GeoID -ne "221") {
    Set-WinHomeLocation -GeoID "221"
}

For a table of GeoIDs, see Table of Geographical Locations at Microsoft Learn.

The last language setting is the Time Zone:

# Ensure the time zone is set to W. Europe Standard Time (CET/CEST) 
if ((Get-TimeZone).Id -ne "W. Europe Standard Time") {
    Set-TimeZone -Id "W. Europe Standard Time"
}

To get another time zone, you can use the cmdlet Get-TimeZone.

Get-TimeZone -ListAvailable

The last step for the Language section is to restart the Lab computer.
This can be done manually or with PowerShell.

Using PowerShell for a quick restart, we do the following:

Restart-Computer -Force -Confirm:$false

Now we have the following code:

<#
.SYNOPSIS
    Configures Windows system and user locale settings for Swedish (Sweden).

.DESCRIPTION
    This script sets the following to Swedish (Sweden):
    - Default input method (keyboard layout)
    - User language list
    - System locale
    - User locale
    - Home location (region)
    - Time zone (W. Europe Standard Time)
    The script will restart the computer to apply changes.

.NOTES
    Requires administrative privileges.
    Some changes may require a restart to take effect.
#>

# Check if the script is running with administrative privileges
#Requires -RunAsAdministrator

# Clear the terminal part
Clear-Host

# Set the default input method to Swedish (Sweden) - Keyboard layout: Swedish
if ((Get-WinDefaultInputMethodOverride).InputMethodTip -ne "041D:0000041D") {
    Set-WinDefaultInputMethodOverride -InputTip "041D:0000041D"
}

# Set the user language list to Swedish (Sweden)
if ((Get-WinUserLanguageList).LanguageTag -notcontains "sv-SE") {
    Set-WinUserLanguageList -LanguageList "sv-SE" -Force
}

# Set the system locale to Swedish (Sweden)
if ((Get-WinSystemLocale).Name -ne "sv-SE") {
    Set-WinSystemLocale -SystemLocale "sv-SE"
}

# Set the user locale to Swedish (Sweden)
if ((Get-Culture).Name -ne "sv-SE") {
    Set-Culture -CultureInfo "sv-SE"
}

# Set the home location to Sweden
if ((Get-WinHomeLocation).GeoID -ne "221") {
    Set-WinHomeLocation -GeoID "221"
}

# Ensure the time zone is set to W. Europe Standard Time (CET/CEST) 
if ((Get-TimeZone).Id -ne "W. Europe Standard Time") {
    Set-TimeZone -Id "W. Europe Standard Time"
}

Restart-Computer -Force -Confirm:$false

Windows should now have all language settings configured to Swedish or your preferred language.

PowerShell 7

Now that the language has been successfully set, we can move forward with the next step, which is installing PowerShell 7. This installation is essential to enable and run labs that specifically require PowerShell 7 for their execution and functionality.

The simplest and officially recommended method by Microsoft to install PowerShell 7 on Windows is by using WinGet.

However, this method will only be effective if the lab computer is completely and thoroughly updated with the latest system updates. Without having the most recent updates installed, WinGet will not operate correctly and may encounter various issues or fail to function altogether.

The simplest and most straightforward way to ensure your system is fully up to date is to manually navigate to the Check for Updates section and carefully install all available updates. This process should include not only the critical and recommended updates but also optional ones, such as those related to .NET framework components, which can be essential for certain applications to function properly.

Start Windows PowerShell with Administrator privileges to ensure you have the necessary permissions.

Then enter the following command:

winget list --id Microsoft.PowerShell

After reviewing the MS Store terms carefully, proceed by pressing the Y key to indicate your agreement and acceptance of all the conditions outlined.

Now we can start PowerShell ISE as administrator and write the following code:

# Check if the script is running with administrative privileges
#Requires -RunAsAdministrator

# Clear the terminal part
Clear-Host

# Check if PowerShell 7 is installed using winget
$Pwsh = winget list --id Microsoft.PowerShell | Select-String "PowerShell"
if ($Pwsh) {
    Write-Output "PowerShell 7 is installed."
} else {
    Write-Output "PowerShell 7 is NOT installed."
    # Install PowerShell 7
    winget install --id Microsoft.PowerShell --source winget --accept-source-agreements --accept-package-agreements
}

PowerShell will be downloaded and installed automatically.

Visual Studio Code

Now it is time to move forward and proceed with the installation of Visual Studio Code on the Lab computer, ensuring that we have the latest tools ready for our development work.

We will perform this installation process using WinGet along with PowerShell, following the same method we previously used when installing PowerShell 7, to maintain consistency and efficiency in our setup steps.

# Check if the script is running with administrative privileges
#Requires -RunAsAdministrator

# Clear the terminal part
Clear-Host

# Install Visual Studio Code
# Check if Visual Studio Code is installed using winget
$VsCode = winget list --id Microsoft.VisualStudioCode | Select-String "Visual Studio Code"
if ($VsCode) {
    Write-Output "Visual Studio Code is installed."
} else {
    Write-Output "Visual Studio Code is NOT installed."
    # Install Visual Studio Code
    winget install --id Microsoft.VisualStudioCode --source winget --accept-source-agreements --accept-package-agreements
}

Visual Studio Code will be downloaded and installed automatically.

VSCode Extensions

Now we are fully prepared and ready to start working with our development environment.

HOWEVER, Visual Studio Code (VSCode) becomes much more powerful and enjoyable to use when enhanced with some useful extensions, and I personally recommend these 5 essential extensions as a great starter kit to improve your workflow.

PowerShell for Visual Studio Code

This extension allows you to seamlessly integrate full PowerShell support within Visual Studio Code, making scripting and command execution much easier and more efficient.

VSCode-Icons

This extension adds visually appealing and distinctive icons to the Explorer view, helping you quickly identify file types and folders.
After installing, you must enable it within the extensions panel to activate the icon set.

Without:

With:

CodeSnap

Takes a clear and nice screenshot of your code and saves it to a file on your computer.

Press Ctrl-Shift-P to open the Command Palette, then type CodeSnap in the search bar, and select the CodeSnap option from the list.

After that, simply highlight the portion of code you want to capture, and the tool will create a neat screenshot for you.

Then press the shutter button to capture the image and save the screenshot to your desired location.
The picture shown below is taken from the CodeSnap extension.

GitHub CoPilot

GitHub CoPilot provides you with the incredible power of artificial intelligence directly within Visual Studio Code, making your coding experience much more efficient and enjoyable.

All you need to start using this amazing tool is a simple GitHub account, which enables you to access its full range of features without any hassle.

In my opinion, it is especially useful for assisting with the creation of documentation and for debugging code, offering valuable suggestions and insights that can save time and improve the quality of your projects.

XML Tools

XML Tools by Josh Johnson.

I frequently work with XML files in my projects, and this tool has proven to be incredibly helpful for me. It assists greatly with the formatting of XML files whenever it is needed, making the process much smoother and more efficient.

Install Extensions

To install extensions, you have several options available. You can easily do it directly from Visual Studio Code using the graphical user interface (GUI), which provides a user-friendly way to browse and add extensions. Alternatively, if you prefer using the command line, you can install extensions through PowerShell or from a Command Prompt window running with administrator privileges. Each method allows you to efficiently manage your extensions according to your preferred workflow.

# Install PowerShell Extension
code --install-extension ms-vscode.PowerShell

# Install VSCode-Icons Extension
code --install-extension vscode-icons-team.vscode-icons

# Install CodeSnap Extension
code --install-extension adpyke.codesnap

# Install GitHub CoPilot incl CoPilot Chat Extension
code --install-extension github.copilot

# Install XML Tools by Josh Johnson
code --install-extension dotjoshjohnson.xml

If you get an error when doing this It’s probably because you did not restart PowerShell after you installed Visual Studio Code.

Restore Snapshot

To revert to the snapshot you created after installing Windows 11, simply shut down your computer.

And then look at the VirtualBox Manager and your Virtual Machine.

Click the lines on the right, then select Snapshot.

Click on the Snapshot you want to restore.

And then click on Restore.

You can choose to have VirtualBox create a snapshot of the current machine state.

The End

This marks the official conclusion of this comprehensive and detailed guide.

Up to this point, we have successfully completed the setup of a Lab computer that is fully equipped with the latest version of PowerShell 7 (7.5). In addition, we have installed the powerful and versatile Visual Studio Code editor along with five carefully selected and highly useful extensions.

All of these components are running smoothly and efficiently within a VirtualBox virtual environment. Furthermore, the system has been configured with the appropriate language settings to significantly enhance overall usability and user experience.

This guide was little bit longer then the guide with Hyper-V, but I think if you have followed all of the steps it should not be difficult.

It is my sincere hope that this guide will assist you in setting up your Lab environment quickly and efficiently, allowing you to have a strong and effective start to your Lab experience.

The post How to Create a Lab Machine with VirtualBox first appeared on The PowerAdmin.

In my detailed article about setting up Hyper-V using the Quick Create feature to establish a comprehensive Lab Environment with Windows 11, specifically designed for PowerShell and Visual Studio Code labs, all of the setup procedures and configurations rely heavily on the fact that you are running Windows 11 Pro or Enterprise editions on your system.

However, if you are working from your personal home computer and it runs the Windows 11 Home edition, and you still want to perform similar labs, an alternative solution is available. You can install VirtualBox, which is a free and open-source virtualization software that supports installation on almost every major Operating System currently available, providing a flexible and accessible option for lab setups outside the Windows 11 Pro or Enterprise environment.

This method requires a bit more time to set up, especially if you are not using the Quick Setup option that comes with a pre-configured Windows 11 installation. However, it is not overly complicated, and I will carefully guide you through every single step in detail here to ensure you can follow along without any difficulties.

VirtualBox requires your computer to support virtualization technology, which is available on almost all modern computers. If it is not enabled by default, you may need to activate it in your BIOS settings.

You also need free space on a hard drive for the installation of VirtualBox and then for the installation of Windows 11.

In this guide I will show you how to Install VirtualBox and in my next guide I will show you how to setup an evaluation version of Windows 11 as an Lab Environment.

All the code and information provided on this website are offered “as is” without any guarantees or warranties of any kind. Although the code and information are tested, we do not warrant that the code is error-free or that it will meet your specific requirements. Use the code at your own risk. We disclaim all liability for any damages or losses arising from the use or inability to use the provided materials.

If you are using Windows, you can begin by checking your operating system. Open PowerShell as an Administrator and enter the following command:

(Get-CimInstance Win32_OperatingSystem).Caption

You can also install VirtualBox on Windows 11 Pro and Enterprise editions if you wish.

Supported Operating Systems include:

You can find VirtualBox here.

Visit the download page and select the version that matches your computer and download it.

I will show you the Windows installation.

Begin the installation process

Simply select I accept… and press Next

Just click Next

Make sure you are not running any tasks that could be interrupted when VirtualBox updates the network settings. Then, click Yes to proceed.

VirtualBox relies on Python Core and win32api bindings. If these are not already installed, you will need to click Yes to proceed with the installation.

If you agree to create shortcuts on the Start Menu, Desktop, and Quick Launch Bar, simply click Next to continue.

Just click Install if you want to start the installation.

The installation will be quick.

When you press the Finish button, VirtualBox will launch and start running for the very first time on your system.

I believe this installation process was not significantly more difficult than simply enabling Hyper-V on your system.

In my upcoming guide, I will walk you through the detailed steps on how to download and install a fully functional evaluation version of Windows 11, providing all the necessary instructions to get you started.

The post What to do when you can’t install Hyper-V first appeared on The PowerAdmin.

In a previous blog post, I demonstrated how to configure Visual Studio Code by installing the necessary extensions and adjusting the settings specifically for PowerShell development.

If you happen to use Visual Studio Code across multiple computers, different work environments, or various lab machines, it can quickly become a tedious and time-consuming task to set up everything individually on each device.

Fortunately, there are much easier and more efficient methods to streamline this process.

Begin by setting up all your preferred settings, installing all required extensions, and customizing any snippets you want directly in your Visual Studio Code environment first.

In this guide, I will demonstrate two methods. Later, I will also show how to automate the process using scripts.

All the code and information provided on this website are offered “as is” without any guarantees or warranties of any kind. Although the code and information are tested, we do not warrant that the code is error-free or that it will meet your specific requirements. Use the code at your own risk. We disclaim all liability for any damages or losses arising from the use or inability to use the provided materials.

Profiles

If you want to share your VSCode setup with others or prefer not to log in to your GitHub or Microsoft account, you can use profiles.

Profiles allow you to export and import the following settings:

• Contents
• Settings
• Keyboard Shortcuts
• Tasks
• Snippets
• Extensions

Create

Easiest way to create a profile for export is to go to Manage -> Profiles.

Click on Default profile and click on the three dots.
And then Duplicate…

Now you will get a copy of the Default profile.
Rename it by changing the Name and then press the button Create.

Export

Now it’s time to Export the profile and here you have two options.
GitHub (gist) and Local (file).

GitHub

When exporting to GitHub (gist) you need to sign in to your GitHub account.

Click allow and then you need to login to GitHub.

And Authorize Visual Studio Code

Copy the link and save it.

Local

Just choose a name and where to save your profile and click Save.

Import

On a new computer you just need to install Visual Studio Code and then go to Profiles and click on the arrow right to New Profile and choose Import Profile…

GitHub

Just copy the url to your profile and paste it in the box for Profile Template URL and press Enter.

Local

For local just press Select File… and locate your saved profile file.

Create

And then it’s the same for GitHub profile or Local file.

And press Create

Now you will get some popups regarding trusting publishers.
These are for the extensions you have in your exported profile.

Choose Trust Publishers and Install

It will take some time before it has created the profile.

To use it you need to click on the Use button right to your profile

Now you will see all extensions, snippets and settings that you exported.

Settings Sync

If you can and want to login with your GitHub or Microsoft account you can sync your settings with Settings Sync.

This are a bit easier. You do Backup and Sync first on your perfect setup and then you can Sync it to other computers where you have Visual Studio Code Installed.

Note that syncing between your lab and office/work computers will apply changes to both, so be mindful when syncing across different environments.

Go to Manage and then Backup and Sync Settings.
Choose what to backup and Sync and then Click on Sign In.

Choose the option you prefer to Sign In with.

For this example, I will choose GitHub.

Next, you will need to Sign In to your GitHub account, then Authorize the application, and finally click Continue.

Wait patiently while Visual Studio Code completes the Backup and Sync process. After that, navigate to Manage, and you should see the message Settings Sync is On.

Now you can move to another computer and perform the sync there as well.

If you have created a profile, make sure to go to Profiles and set it as active.
And that’s all there is to it!

The End

I sincerely hope you find this guide helpful and informative.

The two methods described here have been incredibly useful for me, especially when I am transitioning from one customer site to another or working on different Lab computers.

I tend to using the Profile option because I prefer not to log in with my GitHub or Microsoft account on Lab computers or within customer environments for security and privacy reasons.

The post Export and Import settings in different ways for Visual Studio Code first appeared on The PowerAdmin.

In my guide Create a Lab Machine, I walk you through the complete process of setting up a virtual Lab Machine running Windows 11 within Hyper-V using the Quick Create feature.

This includes configuring the language settings properly to suit your preferences, installing the latest version of PowerShell 7 for enhanced scripting testing, and setting up Visual Studio Code along with several useful extensions to streamline your development workflow.

In this guide I will show you some helpfull tips and trix on setting up Visual Studio Code for PowerShell editing.

All the code and information provided on this website are offered “as is” without any guarantees or warranties of any kind. Although the code and information are tested, we do not warrant that the code is error-free or that it will meet your specific requirements. Use the code at your own risk. We disclaim all liability for any damages or losses arising from the use or inability to use the provided materials.

Settings menu

We can configure all of our settings within the dedicated settings section.
This particular section can be accessed through several different methods.

One common way is by clicking the Manage icon located at the bottom left corner of the screen, and then selecting Settings from the menu that appears.

Alternatively, you can access it by clicking on the Manage icon first, followed by selecting the Command Palette. Another way is to press the keyboard shortcut Ctrl+Shift+P, and then type settings in the search bar. From the search results, choose the option labeled “Open settings (UI)” to proceed.

Default language

When creating a PowerShell script file we want to go to File and Click on New Text File for a new PowerShell Script.

But as default in Visual Studio Code a New Text File is not associated with PowerShell.

To fix this we need go to the settings section as described above and search for “Default Language“.

Then enter powershell in the Files: Default Language text box.

If you write PowerShell as Microsoft and the PowerShell community recommend, it will not work…

so we need to write powershell using only lowercase letters

Tab completion

Another thing that is not there by default is Tab Completion.
This is because Visual Studio Code is not just made for PowerShell.

To enable tab completion we need to search for Tab Completion in the Settings search.

And in the Editor: Tab Completions section, change off to on.

Mouse Wheel Zoom

Another seeting that I can’t be without is the Mouse Wheel Zoom setting, both for the editor and the terminal window.

It will enable zoom the font of the editor and terminal when using mouse wheel and holding Ctrl.

In the video below I show first when using Mouse Wheel Zoom on the editor and then using on the terminal window.

The font size for the terminal window is better to set with the Terminal Font Size setting. This is described below.

Terminal Font Size

The terminal font size is pretty small as default and as you can see in the video with the mouse wheel zoom, it can be a challenge to get a good size of the terminal font with the mouse wheel.

So it’s easier to use the settings search and search for terminal font size and change the Terminal > Integrated: Font Size.

I like 20, at least when I share my screen and show something in Visual Studio Code. But I think the settings is pretty personal so you need to test for your self.

The End

These were my fundamental and essential settings for Visual Studio Code specifically tailored for working with PowerShell.
These are truly my “must-have” configurations that I rely on for an optimized coding experience!

In the near future, I plan to share a detailed guide explaining how to export and import your Visual Studio Code settings using various methods.

This way, you won’t have to go through the hassle of manually adjusting your preferences every time you start working on a new computer or find yourself in a lab environment.

The post Setting up Visual Studio Code for PowerShell first appeared on The PowerAdmin.

This is my first User Snippet posted for Visual Studio Code.
I know there is a default snippet included with the PowerShell extension.

All the code and information provided on this website are offered “as is” without any guarantees or warranties of any kind. Although the code and information are tested, we do not warrant that the code is error-free or that it will meet your specific requirements. Use the code at your own risk. We disclaim all liability for any damages or losses arising from the use or inability to use the provided materials.

However, I want to add additional information and have it inserted automatically.

To access the default Comment-Based help snippet, simply type comm in Visual Studio Code, and IntelliSense will display the comment-help snippet, as shown in the image below.

This option is better than not using Comment-Based Help for your script or function.

It’s great! Everything required for Comment-Based Help is included.

HOWEVER…

<#
.SYNOPSIS
    A short one-line action-based description, e.g. 'Tests if a function is valid'
.DESCRIPTION
    A longer description of the function, its purpose, common use cases, etc.
.NOTES
    Information or caveats about the function e.g. 'This function is not supported in Linux'
.LINK
    Specify a URI to a help page, this will show when Get-Help -Online is used.
.EXAMPLE
    Test-MyTestFunction -Verbose
    Explanation of the function or its result. You can include multiple examples with additional .EXAMPLE lines
#>

I always include name, author, version, and date in the Notes section, and the script name in the Example section.

But I don’t want to type this information manually every time.
I’m a bit lazy!

Here is my standard Comment Based Help:

<#
    .SYNOPSIS
        A short description
    .DESCRIPTION
        A longer description  
    .PARAMETER Name
        Specifies the name of the parameter
    .EXAMPLE
        Get-Information.ps1 -Parameter "ParameterValue"
    .NOTES
        NAME:       Get-Information
        AUTHOR:     Fredrik Wall
        VERSION:    1.0
        CREATED:    2025-06-04
#>

I have also created a PowerShell user snippet for this.

There are many variables available for Snippets in Visual Studio Code, and I use several of them.

Example – To get the PowerShell script name, I use $TM_FILENAME.

Name – For the script name without the .ps1 extension, I use $TM_FILENAME_BASE.

Author – This one was a bit tricky to automate. I use ${WORKSPACE_NAME}.

Created – I use ${CURRENT_YEAR}-${CURRENT_MONTH}-${CURRENT_DATE} here. You can adjust this format to match your country’s date style.

All available variables can be found on the User Defined Snippets page:
https://code.visualstudio.com/docs/editing/userdefinedsnippets

To be able to get the automatically Comment Based Help with all information as above you first of all need to add this to the PowerShell User Snippet JSON file.

"Comment Based Help": {
		"prefix": "Comment Based Help",
		"body": [
		  "<#",
		  "    .SYNOPSIS",
		  "        A short description",
		  "    .DESCRIPTION",
		  "        A longer description  ",
		  "    .PARAMETER Name",
          "        Specifies the name of the parameter",
		  "    .EXAMPLE",
		  "        $TM_FILENAME -Parameter \"ParameterValue\"",
		  "    .NOTES",
		  "        NAME:       $TM_FILENAME_BASE",
		  "        AUTHOR:     ${WORKSPACE_NAME}",
		  "        VERSION:    1.0",
		  "        CREATED:    ${CURRENT_YEAR}-${CURRENT_MONTH}-${CURRENT_DATE}",
		  "#>"
		],
		"description": "Comment Based Help By PowerAdmin.se"
	  }

The easiest way to open the JSON file is by using Shift+Ctrl+P (Command Palette) and searching for Snippets: Configure Snippets. Then select powershell.json (PowerShell).

Next, insert the code above between the { and }.

If you already have other snippets, add a , after the last one before pasting the new code. Save the file afterward.

Now, you will have a snippet that inserts this information automatically…
…as long as you save your script first with your chosen name.

In my example: Get-Information.ps1

Finally, go to File and select Save Workspace As with your name to set your name as the Author.

This was a brief guide, but it provides helpful insights that assist me every single day without fail.

The post Comment Based help as a snippet first appeared on The PowerAdmin.

This comprehensive guide will walk you through setting up Hyper-V on your Windows 11 computer using PowerShell commands, as well as how to utilize the Windows 11 development environment available via the Quick Create feature. By following these steps, you’ll gain all the knowledge needed to install and run Hyper-V efficiently on your system.

All the code and information provided on this website are offered “as is” without any guarantees or warranties of any kind. Although the code and information are tested, we do not warrant that the code is error-free or that it will meet your specific requirements. Use the code at your own risk. We disclaim all liability for any damages or losses arising from the use or inability to use the provided materials.

Enable Hyper-V

First, we need to verify whether Hyper-V is enabled on your computer.
There are multiple ways to check this, but for consistency, this guide will use PowerShell whenever possible.

You probably need like 100 GB of free disk space to be able to do this.
The download is almost 22 GB and then you need disk for the installation and the lab.

And you will need some free memory as well.
I use 4096 MB and It’s okay for a Lab Machine for PowerShell and Visual Studio Code.

Start by opening Visual Studio Code or PowerShell ISE with “Run as Administrator” privileges.

Next, let’s check if the Hyper-V feature is currently enabled.
Write or Copy and paste the code below to your PowerShell editor and run the code.

Get-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V

If you get this status you need to enable it.

If you get this status you don’t need to enable it.

To enable it we just need to write or copy and paste this code (all on the same line):

Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V -All

This will enable Hyper-V with all subfeatures and tools.
When prompted to restart, it is best to press Y and restart.

Quick Create

Now that the Hyper-V feature is installed, we can open the Hyper-V Quick Create tool by searching for Hyper-V Quick Create.

Make sure to open it as an administrator.

Then just click on Windows 11 dev environment and after that Create Virtual Machine.

First of all the Quick Create will download the image.

And then the image will be extracted.

When Quick Create is finished, you will have the option to connect or edit settings.

Connect and start

Just press Start!

Waiting a bit longer

Sign In

Click on Sign In

Some more waiting

And then we are good to go with a fully installed Windows 11 for development.

Setup the lab computer

This guide will show you how to set up and install all tools needed for PowerShell and Visual Studio Code in the Lab Machine.

Language

First, open PowerShell ISE as Administrator.

Click the arrow next to Script to open the Editor in PowerShell ISE.
Then close the Commands view on the right to have more space for scripting.

First of all I want to set all language settings to Swedish.
Just copy and past the code below and run it to do the changes.
You can do it bit by bit or all at once.

This can be done in different ways but I like my scripts to have more checks built in.
So this is not the easiest way

We start with a check for Run As Administrator and a Clear-Host.

# Check if the script is running with administrative privileges
#Requires -RunAsAdministrator

# Clear the terminal part
Clear-Host

Then we set the input method to Swedish if it is not already.

# Set the default input method to Swedish (Sweden) - Keyboard layout: Swedish
if ((Get-WinDefaultInputMethodOverride).InputMethodTip -ne "041D:0000041D") {
    Set-WinDefaultInputMethodOverride -InputTip "041D:0000041D"
}

If you want another input method you can look at the Default input profiles (input locales) in Windows page at Microsoft Learn for more language codes.

You just need to use the same language codes for the Get and for the Set.

And now we change the user language list to Swedish.

# Set the user language list to Swedish (Sweden)
if ((Get-WinUserLanguageList).LanguageTag -notcontains "sv-SE") {
    Set-WinUserLanguageList -LanguageList "sv-SE" -Force
}

For this one you will get this warning and it’s normal:

WARNING: If the Windows Display Language has changed, it will take effect after the next sign-in.

And to set the system locale to Swedish we write:

# Set the system locale to Swedish (Sweden)
if ((Get-WinSystemLocale).Name -ne "sv-SE") {
    Set-WinSystemLocale -SystemLocale "sv-SE"
}

Setting user locale to Swedish:

# Set the user locale to Swedish (Sweden)
if ((Get-Culture).Name -ne "sv-SE") {
    Set-Culture -CultureInfo "sv-SE"
}

Home location:

# Set the home location to Sweden
if ((Get-WinHomeLocation).GeoID -ne "221") {
    Set-WinHomeLocation -GeoID "221"
}

For a table of GeoIDs, see Table of Geographical Locations at Microsoft Learn.

The last language setting is the Time Zone:

# Ensure the time zone is set to W. Europe Standard Time (CET/CEST) 
if ((Get-TimeZone).Id -ne "W. Europe Standard Time") {
    Set-TimeZone -Id "W. Europe Standard Time"
}

To get another time zone, you can use the cmdlet Get-TimeZone.

Get-TimeZone -ListAvailable

The last step for the Language section is to restart the Lab computer.
This can be done manually or with PowerShell.

Using PowerShell for a quick restart, we do the following:

Restart-Computer -Force -Confirm:$false

Now we have the following code:

<#
.SYNOPSIS
    Configures Windows system and user locale settings for Swedish (Sweden).

.DESCRIPTION
    This script sets the following to Swedish (Sweden):
    - Default input method (keyboard layout)
    - User language list
    - System locale
    - User locale
    - Home location (region)
    - Time zone (W. Europe Standard Time)
    The script will restart the computer to apply changes.

.NOTES
    Requires administrative privileges.
    Some changes may require a restart to take effect.
#>

# Check if the script is running with administrative privileges
#Requires -RunAsAdministrator

# Clear the terminal part
Clear-Host

# Set the default input method to Swedish (Sweden) - Keyboard layout: Swedish
if ((Get-WinDefaultInputMethodOverride).InputMethodTip -ne "041D:0000041D") {
    Set-WinDefaultInputMethodOverride -InputTip "041D:0000041D"
}

# Set the user language list to Swedish (Sweden)
if ((Get-WinUserLanguageList).LanguageTag -notcontains "sv-SE") {
    Set-WinUserLanguageList -LanguageList "sv-SE" -Force
}

# Set the system locale to Swedish (Sweden)
if ((Get-WinSystemLocale).Name -ne "sv-SE") {
    Set-WinSystemLocale -SystemLocale "sv-SE"
}

# Set the user locale to Swedish (Sweden)
if ((Get-Culture).Name -ne "sv-SE") {
    Set-Culture -CultureInfo "sv-SE"
}

# Set the home location to Sweden
if ((Get-WinHomeLocation).GeoID -ne "221") {
    Set-WinHomeLocation -GeoID "221"
}

# Ensure the time zone is set to W. Europe Standard Time (CET/CEST) 
if ((Get-TimeZone).Id -ne "W. Europe Standard Time") {
    Set-TimeZone -Id "W. Europe Standard Time"
}

Restart-Computer -Force -Confirm:$false

PowerShell 7

Now that the language has been successfully set, we can move forward with the next step, which is installing PowerShell 7. This installation is essential to enable and run labs that specifically require PowerShell 7 for their execution and functionality.

The simplest and officially recommended method by Microsoft to install PowerShell 7 on Windows is by using WinGet.

However, this method will only be effective if the lab computer is completely and thoroughly updated with the latest system updates. Without having the most recent updates installed, WinGet will not operate correctly and may encounter various issues or fail to function altogether.

The simplest and most straightforward way to ensure your system is fully up to date is to manually navigate to the Check for Updates section and carefully install all available updates. This process should include not only the critical and recommended updates but also optional ones, such as those related to .NET framework components, which can be essential for certain applications to function properly.

Start Windows PowerShell with Administrator privileges to ensure you have the necessary permissions.

Then enter the following command:

winget list --id Microsoft.PowerShell

After reviewing the MS Store terms carefully, proceed by pressing the Y key to indicate your agreement and acceptance of all the conditions outlined.

Now we can start PowerShell ISE as administrator and write the following code:

# Check if the script is running with administrative privileges
#Requires -RunAsAdministrator

# Clear the terminal part
Clear-Host

# Check if PowerShell 7 is installed using winget
$Pwsh = winget list --id Microsoft.PowerShell | Select-String "PowerShell"
if ($Pwsh) {
    Write-Output "PowerShell 7 is installed."
} else {
    Write-Output "PowerShell 7 is NOT installed."
    # Install PowerShell 7
    winget install --id Microsoft.PowerShell --source winget --accept-source-agreements --accept-package-agreements
}

Visual Studio Code

Now it is time to move forward and proceed with the installation of Visual Studio Code on the Lab computer, ensuring that we have the latest tools ready for our development work.

We will perform this installation process using WinGet along with PowerShell, following the same method we previously used when installing PowerShell 7, to maintain consistency and efficiency in our setup steps.

# Check if the script is running with administrative privileges
#Requires -RunAsAdministrator

# Clear the terminal part
Clear-Host

# Install Visual Studio Code
# Check if Visual Studio Code is installed using winget
$VsCode = winget list --id Microsoft.VisualStudioCode | Select-String "Visual Studio Code"
if ($VsCode) {
    Write-Output "Visual Studio Code is installed."
} else {
    Write-Output "Visual Studio Code is NOT installed."
    # Install Visual Studio Code
    winget install --id Microsoft.VisualStudioCode --source winget --accept-source-agreements --accept-package-agreements
}

VSCode Extensions

Now we are fully prepared and ready to start working with our development environment.

HOWEVER, Visual Studio Code (VSCode) becomes much more powerful and enjoyable to use when enhanced with some useful extensions, and I personally recommend these 5 essential extensions as a great starter kit to improve your workflow.

PowerShell for Visual Studio Code

This extension allows you to seamlessly integrate full PowerShell support within Visual Studio Code, making scripting and command execution much easier and more efficient.

VSCode-Icons

This extension adds visually appealing and distinctive icons to the Explorer view, helping you quickly identify file types and folders.
After installing, you must enable it within the extensions panel to activate the icon set.

Without:

With:

CodeSnap

Takes a clear and nice screenshot of your code and saves it to a file on your computer.

Press Ctrl-Shift-P to open the Command Palette, then type CodeSnap in the search bar, and select the CodeSnap option from the list.

After that, simply highlight the portion of code you want to capture, and the tool will create a neat screenshot for you.

Then press the shutter button to capture the image and save the screenshot to your desired location.
The picture shown below is taken from the CodeSnap extension.

GitHub CoPilot

GitHub CoPilot provides you with the incredible power of artificial intelligence directly within Visual Studio Code, making your coding experience much more efficient and enjoyable.

All you need to start using this amazing tool is a simple GitHub account, which enables you to access its full range of features without any hassle.

In my opinion, it is especially useful for assisting with the creation of documentation and for debugging code, offering valuable suggestions and insights that can save time and improve the quality of your projects.

XML Tools

XML Tools by Josh Johnson.

I frequently work with XML files in my projects, and this tool has proven to be incredibly helpful for me. It assists greatly with the formatting of XML files whenever it is needed, making the process much smoother and more efficient.

Install Extensions

To install extensions, you have several options available. You can easily do it directly from Visual Studio Code using the graphical user interface (GUI), which provides a user-friendly way to browse and add extensions. Alternatively, if you prefer using the command line, you can install extensions through PowerShell or from a Command Prompt window running with administrator privileges. Each method allows you to efficiently manage your extensions according to your preferred workflow.

# Install PowerShell Extension
code --install-extension ms-vscode.PowerShell

# Install VSCode-Icons Extension
code --install-extension vscode-icons-team.vscode-icons

# Install CodeSnap Extension
code --install-extension adpyke.codesnap

# Install GitHub CoPilot incl CoPilot Chat Extension
code --install-extension github.copilot

# Install XML Tools by Josh Johnson
code --install-extension dotjoshjohnson.xml

The End

This marks the official conclusion of this comprehensive and detailed guide.

Up to this point, we have successfully completed the setup of a Lab computer that is fully equipped with the latest version of PowerShell 7 (7.5). In addition, we have installed the powerful and versatile Visual Studio Code editor along with five carefully selected and highly useful extensions.

All of these components are running smoothly and efficiently within a Hyper-V virtual environment. Furthermore, the system has been configured with the appropriate language settings to significantly enhance overall usability and user experience.

It is my sincere hope that this guide will assist you in setting up your Lab environment quickly and efficiently, allowing you to have a strong and effective start to your Lab experience.

The post Create a lab machine first appeared on The PowerAdmin.