How to Check SMB Share Scope Name in Windows 11

Learn how to check SMB share ScopeName in Windows 11 using PowerShell, identify scoped shares, and troubleshoot advanced SMB configurations.

If you manage SMB file sharing on Windows 11 or troubleshoot a Windows Server file-sharing environment, you may encounter the ScopeName and Scoped properties when inspecting SMB shares with PowerShell.

These properties are particularly relevant to advanced SMB configurations involving scoped shares and Windows Server failover cluster file-server resources. On a normal standalone Windows 11 computer, most ordinary SMB shares will not require a specialized scope configuration.

Windows provides the Get-SmbShare cmdlet for inspecting SMB share objects. Among its available parameters are -Scoped and -ScopeName, which can be used to filter and identify scoped SMB shares.

In this guide, you will learn how to check SMB Share ScopeName in Windows 11, determine whether a share is scoped, inspect the scope name, filter scoped shares, compare scope information with other SMB properties, export the results, and troubleshoot unexpected SMB share scope configurations.

What Is SMB Share Scope?

An SMB share scope is an advanced configuration concept used to associate a share with a particular scope or file-server resource. It is especially relevant in Windows Server failover cluster environments.

The ScopeName property identifies the scope associated with an SMB share, while the Scoped property indicates whether the share is scoped.

Microsoft's Get-SmbShare documentation specifically describes the ScopeName parameter as specifying the scope of a share by name and notes that it is used with Windows Server failover cluster file-server resources.

This means that ScopeName should not be confused with the ordinary SMB share name. The share name is the name users see when accessing a path such as \\server\share, while the scope identifies an additional management or cluster-related context.

Why Check SMB Share ScopeName?

For ordinary home or small-office file sharing, you may never need to examine SMB share scope. However, it becomes useful when investigating advanced configurations or troubleshooting a share hosted by clustered infrastructure.

Checking ScopeName can help you:

• Determine whether an SMB share is scoped.
• Identify the scope associated with a share.
• Investigate SMB shares in failover cluster environments.
• Distinguish ordinary shares from scoped shares.
• Document advanced SMB configurations.
• Filter SMB shares by scope.
• Compare multiple SMB share configurations.
• Troubleshoot unexpected share behavior.

Scope information should be considered separately from the current share state, permissions, availability type, and Continuous Availability settings.

For example, you can first check the current operational state using our guide to How to Check SMB Share State in Windows 11.

Open PowerShell in Windows 11

You can inspect SMB shares using PowerShell. For administrative SMB configuration, it is recommended to use an elevated PowerShell or Windows Terminal session.

1. Press Windows + X.
2. Select Terminal (Admin) or PowerShell (Admin).
3. Approve the User Account Control prompt if requested.

Once PowerShell is open, you can use the SmbShare module to inspect SMB shares.

Check SMB Share ScopeName

The basic command for listing SMB shares is:

Get-SmbShare

To specifically display the share name, path, scoped status, and scope name, use:

Get-SmbShare |
Select-Object Name, Path, Scoped, ScopeName

This provides a simple overview of the scope configuration.

A result may look similar to:

Name        Path                 Scoped  ScopeName
----        ----                 ------  ---------
Documents   C:\Shares\Documents  False   *
Projects    D:\Shares\Projects   False   *
Finance     D:\Shares\Finance    False   *

The exact values depend on the Windows SMB environment being queried.

Check One SMB Share

If you want to inspect a specific share, use the -Name parameter:

Get-SmbShare -Name "Projects" |
Select-Object Name, Path, Scoped, ScopeName

This is useful when you already know the share name and do not want to review every SMB share on the computer.

For example:

Name      Path              Scoped  ScopeName
----      ----              ------  ---------
Projects  D:\Shares\Projects False   *

Do not assume that a displayed scope value automatically means the share is part of a failover cluster. Always interpret Scoped and ScopeName together with the broader SMB and server configuration.

What Does the Scoped Property Mean?

The Scoped property indicates whether an SMB share is scoped.

You can inspect it directly:

Get-SmbShare |
Select-Object Name, Scoped

For example:

Name        Scoped
----        ------
Documents   False
Projects    False
Finance     False

On a normal standalone Windows 11 computer, ordinary file shares will commonly not require scoped-share configuration.

In an advanced clustered environment, however, scoped shares can be used in conjunction with cluster file-server resources.

What Does ScopeName Mean?

ScopeName identifies the scope associated with the SMB share.

You can display it with:

Get-SmbShare |
Select-Object Name, ScopeName

Or together with the other important properties:

Get-SmbShare |
Select-Object Name, Path, Scoped, ScopeName

The scope name should not be interpreted as another name for the physical folder. The Path identifies the local folder being shared, while ScopeName identifies the scope associated with the SMB share.

Check Only Scoped SMB Shares

If you want to find shares where Scoped is set to True, use:

Get-SmbShare |
Where-Object {$_.Scoped -eq $true} |
Select-Object Name, Path, Scoped, ScopeName

This is a useful auditing command because it removes ordinary unscoped shares from the output.

If the command returns no results, there may be no scoped SMB shares exposed by the computer being queried.

Check Unscoped SMB Shares

You can also list shares that are not scoped:

Get-SmbShare |
Where-Object {$_.Scoped -eq $false} |
Select-Object Name, Path, Scoped, ScopeName

This can be useful when comparing a standard SMB configuration with a clustered configuration.

Filter SMB Shares by ScopeName

If you know the scope name you want to investigate, you can use the -ScopeName parameter.

Get-SmbShare -ScopeName "*"

You can also use the property returned by the command:

Get-SmbShare |
Where-Object {$_.ScopeName -eq "*"} |
Select-Object Name, Path, Scoped, ScopeName

Be careful when interpreting wildcard or special scope values. The exact scope values available depend on the SMB and cluster environment being queried.

Use the Get-SmbShare Scoped Parameter

The Get-SmbShare cmdlet also provides a -Scoped parameter that can be used to filter the shares being enumerated.

To request scoped shares:

Get-SmbShare -Scoped $true

To request unscoped shares:

Get-SmbShare -Scoped $false

You can combine this with Select-Object for a cleaner result:

Get-SmbShare -Scoped $true |
Select-Object Name, Path, Scoped, ScopeName

Microsoft documents -Scoped as indicating that the shares to be enumerated should be scoped.

View All Properties of an SMB Share

If you are troubleshooting an advanced SMB configuration, display all properties of the share:

Get-SmbShare -Name "Projects" | Format-List *

This can expose information such as:

• Name
• Path
• Scoped
• ScopeName
• ShareState
• AvailabilityType
• ContinuouslyAvailable
• CurrentUsers
• ConcurrentUserLimit
• CachingMode
• LeasingMode
• FolderEnumerationMode
• EncryptData
• CompressData

This broader view is particularly useful when a share behaves differently from other shares on the same computer.

Check ScopeName With Share State

Scope configuration does not tell you whether an SMB share is currently online.

To compare scope information with the current share state, run:

Get-SmbShare |
Select-Object Name, Path, Scoped, ScopeName, ShareState

This produces a useful troubleshooting overview.

Property	Purpose
Name	The SMB share name.
Path	The local path exposed by the share.
Scoped	Indicates whether the share is scoped.
ScopeName	Identifies the scope associated with the share.
ShareState	Shows the current state of the SMB share.

For a deeper look at ShareState, see How to Check SMB Share State in Windows 11.

Check ScopeName With AvailabilityType

It can be useful to compare ScopeName with AvailabilityType, especially in environments that use clustering.

Get-SmbShare |
Select-Object Name, Path, Scoped, ScopeName, AvailabilityType

This lets you investigate whether a share's scope configuration is associated with a broader high-availability or clustered file-sharing environment.

For more information about AvailabilityType, see our guide to How to Check SMB Share Availability Type in Windows 11.

Check ScopeName With Continuous Availability

Continuous Availability is another important SMB property in clustered environments. It should not be confused with ScopeName.

To compare the settings:

Get-SmbShare |
Select-Object Name, Path, Scoped, ScopeName, AvailabilityType, ContinuouslyAvailable

ScopeName describes scope, while ContinuouslyAvailable indicates whether the share is configured for continuous availability.

You can learn more about Continuous Availability in How to Check SMB Continuous Availability in Windows 11.

Check ScopeName With Current Users

When troubleshooting a live SMB environment, you may also want to know whether users are actively connected to each share.

Get-SmbShare |
Select-Object Name, Path, Scoped, ScopeName, CurrentUsers

This helps distinguish a configuration issue from a share that is simply unused.

For a more focused investigation of user limits, see How to Check SMB Concurrent User Limit in Windows 11.

Check SMB Sessions and Connections

If a scoped SMB share is being accessed by users, inspect the active SMB sessions:

Get-SmbSession

You can also inspect active SMB client connections:

Get-SmbConnection

These commands provide information about current SMB activity, while ScopeName describes the share's configuration.

For more information, see:

• How to Check SMB Sessions in Windows 11
• How to Check SMB Connections in Windows 11

Check Open Files on a Scoped SMB Share

If users report problems accessing files through a scoped SMB share, checking open files can provide additional context.

Get-SmbOpenFile

You can then compare active file access with the share configuration.

See How to Check Open SMB Files in Windows 11 for a detailed explanation of this command.

Check SMB Share Permissions Separately

A share's scope does not determine which users have permission to access the share.

Check SMB share permissions separately:

Get-SmbShareAccess -Name "Projects"

You can also review the complete guide to How to Check SMB Share Permissions in Windows 11.

Remember that effective access can also depend on NTFS permissions on the underlying folder. A correctly scoped share can still deny a user access because of permissions.

Export SMB Scope Information to CSV

If you are documenting several SMB shares, exporting scope information can make comparisons easier.

Get-SmbShare |
Select-Object Name, Path, Scoped, ScopeName, AvailabilityType, ShareState |
Export-Csv "$env:USERPROFILE\Desktop\smb-share-scope.csv" -NoTypeInformation

The CSV file can then be opened in Excel or another spreadsheet application.

You can use this method to create a simple SMB share inventory before or after a configuration change.

Check SMB Share Scope on a Remote Computer

The Get-SmbShare cmdlet supports CIM sessions, allowing administrators to query SMB shares on a remote computer when the environment is configured for remote management.

Create a CIM session:

$session = New-CimSession -ComputerName "FILESERVER"

Then query the shares:

Get-SmbShare -CimSession $session |
Select-Object Name, Path, Scoped, ScopeName, AvailabilityType

When finished, remove the session:

Remove-CimSession $session

Replace FILESERVER with the appropriate computer name.

If the remote query fails, check credentials, remote management configuration, firewall rules, and network connectivity. Do not immediately assume that the SMB share's scope is the cause.

Scoped Shares and Failover Cluster Environments

Scoped SMB shares become especially relevant in Windows Server failover cluster environments.

Microsoft specifically documents the ScopeName parameter for use with Windows Server failover cluster file-server resources.

This is important because Windows 11 can act as both an SMB client and an SMB server, but advanced clustered file-server features are generally associated with Windows Server infrastructure rather than a normal Windows 11 workstation. Microsoft's SMB overview confirms that Windows client operating systems such as Windows 11 can host SMB shares while also connecting to remote SMB shares.

Therefore, if you see an advanced scope configuration while investigating a Windows Server environment from a Windows 11 administration workstation, interpret it in the context of the server's cluster architecture.

Do Not Confuse ScopeName With Share Name

One common source of confusion is treating ScopeName as another version of the SMB share name.

Consider the following conceptual example:

Name       Path                 Scoped  ScopeName
----       ----                 ------  ---------
Projects   D:\Shares\Projects   False   *

Projects is the SMB share name. It is the name used when a client connects to the share.

D:\Shares\Projects is the local filesystem path.

ScopeName represents scope information and should be interpreted separately from both the share name and the filesystem path.

Do Not Confuse ScopeName With AvailabilityType

AvailabilityType and ScopeName are related to advanced SMB configurations but are not interchangeable.

You can inspect both at the same time:

Get-SmbShare |
Select-Object Name, Path, Scoped, ScopeName, AvailabilityType

Availability type can identify a share's availability or cluster-related type, while scope information identifies whether and how the share is scoped.

For more information about availability type, see How to Check SMB Share Availability Type in Windows 11.

Troubleshooting Unexpected SMB Scope Information

1. Display All Share Properties

Get-SmbShare -Name "Projects" | Format-List *

Start by collecting the complete configuration rather than changing a single property immediately.

2. Check Whether the Share Is Scoped

Get-SmbShare -Name "Projects" |
Select-Object Name, Scoped, ScopeName

This confirms the basic scope configuration.

3. Check Availability Type

Get-SmbShare -Name "Projects" |
Select-Object Name, AvailabilityType

This can provide additional context about the share's infrastructure.

4. Check Continuous Availability

Get-SmbShare -Name "Projects" |
Select-Object Name, ContinuouslyAvailable, CATimeout

5. Check Active Sessions

Get-SmbSession

6. Check Active Connections

Get-SmbConnection

7. Check Share Permissions

Get-SmbShareAccess -Name "Projects"

8. Avoid Changing Advanced Cluster Configuration Without a Plan

If a share is associated with a failover cluster or other advanced file-server architecture, do not change scope-related configuration simply because the value looks unfamiliar.

First document the existing configuration and determine how the share is being used. An unexpected result may be an intentional part of the server's architecture.

Useful PowerShell Commands

Purpose	Command
List SMB shares	Get-SmbShare
Check scope information	Get-SmbShare | Select Name,Path,Scoped,ScopeName
Check one share	Get-SmbShare -Name "Projects"
List scoped shares	Get-SmbShare -Scoped $true
List unscoped shares	Get-SmbShare -Scoped $false
Filter by scope name	Get-SmbShare -ScopeName "*"
View all share properties	Get-SmbShare -Name "Projects" | Format-List *
Check availability type	Get-SmbShare | Select Name,AvailabilityType
Check share state	Get-SmbShare | Select Name,ShareState
Check share permissions	Get-SmbShareAccess -Name "Projects"
Check active sessions	Get-SmbSession
Check active connections	Get-SmbConnection
Check open files	Get-SmbOpenFile

Frequently Asked Questions

What is ScopeName in SMB?

ScopeName identifies the scope associated with an SMB share. Microsoft documents the parameter for specifying the scope of a share by name, particularly for Windows Server failover cluster file-server resources.

How do I check SMB ScopeName?

Use:

Get-SmbShare | Select-Object Name, Path, Scoped, ScopeName

What does the Scoped property mean?

Scoped indicates whether the SMB share is scoped. You can display it with:

Get-SmbShare | Select-Object Name, Scoped

How do I list only scoped SMB shares?

Use:

Get-SmbShare -Scoped $true

You can also use:

Get-SmbShare |
Where-Object {$_.Scoped -eq $true}

Is ScopeName the same as the SMB share name?

No. The SMB share name identifies the shared resource, while ScopeName identifies the scope associated with the share.

Is ScopeName the same as AvailabilityType?

No. They describe different aspects of the SMB configuration. AvailabilityType describes the availability or cluster-related type, while ScopeName identifies the share's scope.

Does ScopeName control SMB permissions?

No. SMB share permissions and NTFS permissions control access. Scope information should not be treated as an access-control mechanism.

Is SMB Share Scope important on a normal Windows 11 PC?

Usually it is not an important setting for basic file sharing. Most ordinary Windows 11 users will work with standard SMB shares without needing to manage advanced scoped-share configurations.

Why would I see scoped SMB shares?

Scoped shares are particularly relevant to advanced Windows Server file-sharing environments, including failover cluster file-server resources. If you encounter one, investigate the surrounding server and cluster configuration before making changes.

Final Thoughts

Checking SMB Share ScopeName in Windows 11 is a useful advanced troubleshooting and documentation technique for administrators working with SMB infrastructure.

The Get-SmbShare cmdlet makes it easy to inspect Scoped and ScopeName alongside other important SMB properties. On a normal standalone Windows 11 computer, you will generally encounter ordinary unscoped shares. In more advanced Windows Server environments, however, scope information can become important when working with failover cluster file-server resources.

When troubleshooting an unfamiliar SMB configuration, do not examine ScopeName in isolation. Compare it with AvailabilityType, ShareState, ContinuouslyAvailable, active SMB sessions, connections, and permissions.

For the next layer of SMB troubleshooting, you can also review our guides to SMB Share State, SMB Share Availability Type, SMB Continuous Availability, SMB QoS Flow Scope, SMB Concurrent User Limit, and SMB Share Permissions.