Get-NetView is a tool that collects local system and network configuration data, to streamline diagnosis of Windows networking issues.
To install this module from PowerShell Gallery, run:
Install-Module Get-NetView -SkipPublisherCheck -Force
It is also part of MSFT.Network.Diag
, which can be installed with:
Install-Module MSFT.Network.Diag
If your servers are disconnected or air-gapped, use:
Save-Module Get-NetView C:\SomeFolderPath
Then move the Get-NetView folder (from C:\SomeFolderPath
) to C:\Program Files\WindowsPowerShell\Modules
on your target server.
This script also supports direct execution:
Invoke-WebRequest "aka.ms/Get-NetView" -OutFile "Get-NetView.ps1"
.\Get-NetView.ps1 -OutputDir .\
If blocked by execution policy:
Powershell.exe -ExecutionPolicy Bypass -File .\Get-NetView.ps1 -OutputDir .\
To begin data collection, simply run:
Get-NetView
The output is saved to Desktop\msdbg.<username>
, and can be inspected with any file manager. On completion, a .zip file is created for easy sharing.
For additional help and advanced options, run:
Get-Help Get-NetView
This tool is also run automatically by Get-SDDCDiagnosticInfo by including the -IncludeGetNetView parameter.
Find more from the Core Networking team using the MSFTNet topic.
To see all modules from the Microsoft Core Networking team, use:
Find-Module -Tag MSFTNet
This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit https://cla.microsoft.com.
When you submit a pull request, a CLA-bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., label, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA.
This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.