Import-Module

Import-Module [-Assembly*] <Assembly[]> [-Alias <String[]>] [-ArgumentList <Object[]>] [-AsCustomObject] [-Cmdlet<String[]>] [-DisableNameChecking] [-Force] [-Function <String[]>] [-Global] [-NoClobber] [-PassThru] [-Prefix<String>] [-Scope {Local | Global}] [-Variable <String[]>] [<CommonParameters>]

Import-Module [-Name*] <String[]> [-Alias <String[]>] [-ArgumentList <Object[]>] [-AsCustomObject] [-CimNamespace<String>] [-CimResourceUri <Uri>] -CimSession* <CimSession> [-Cmdlet <String[]>] [-DisableNameChecking] [-Force][-Function <String[]>] [-Global] [-MaximumVersion <String>] [-MinimumVersion <Version>] [-NoClobber] [-PassThru][-Prefix <String>] [-RequiredVersion <Version>] [-Scope {Local | Global}] [-Variable <String[]>][<CommonParameters>]

Import-Module [-FullyQualifiedName*] <ModuleSpecification[]> [-Alias <String[]>] [-ArgumentList <Object[]>][-AsCustomObject] [-Cmdlet <String[]>] [-DisableNameChecking] [-Force] [-Function <String[]>] [-Global][-NoClobber] [-PassThru] [-Prefix <String>] [-Scope {Local | Global}] [-Variable <String[]>] [<CommonParameters>]

Import-Module [-FullyQualifiedName*] <ModuleSpecification[]> [-Alias <String[]>] [-ArgumentList <Object[]>][-AsCustomObject] [-Cmdlet <String[]>] [-DisableNameChecking] [-Force] [-Function <String[]>] [-Global][-NoClobber] -PSSession* <PSSession> [-PassThru] [-Prefix <String>] [-Scope {Local | Global}] [-Variable<String[]>] [<CommonParameters>]

Import-Module [-Name*] <String[]> [-Alias <String[]>] [-ArgumentList <Object[]>] [-AsCustomObject] [-Cmdlet<String[]>] [-DisableNameChecking] [-Force] [-Function <String[]>] [-Global] [-MaximumVersion <String>][-MinimumVersion <Version>] [-NoClobber] [-PassThru] [-Prefix <String>] [-RequiredVersion <Version>] [-Scope{Local | Global}] [-Variable <String[]>] [<CommonParameters>]

Import-Module [-Name*] <String[]> [-Alias <String[]>] [-ArgumentList <Object[]>] [-AsCustomObject] [-Cmdlet<String[]>] [-DisableNameChecking] [-Force] [-Function <String[]>] [-Global] [-MaximumVersion <String>][-MinimumVersion <Version>] [-NoClobber] -PSSession* <PSSession> [-PassThru] [-Prefix <String>] [-RequiredVersion<Version>] [-Scope {Local | Global}] [-Variable <String[]>] [<CommonParameters>]

Import-Module [-ModuleInfo*] <PSModuleInfo[]> [-Alias <String[]>] [-ArgumentList <Object[]>] [-AsCustomObject][-Cmdlet <String[]>] [-DisableNameChecking] [-Force] [-Function <String[]>] [-Global] [-NoClobber] [-PassThru][-Prefix <String>] [-Scope {Local | Global}] [-Variable <String[]>] [<CommonParameters>]

The Import-Module cmdlet adds one or more modules to the current session. The modules that you import must be installed on the local computer or a remote computer.

Starting in Windows PowerShell 3.0, installed modules are automatically imported to the session when you use any commands or providers in the module. However, you can still use the Import-Module command to import a module and you can enable and disable automatic module importing by using the $PSModuleAutoloadingPreference preference variable. For more information about modules, see about_Modules (http://go.microsoft.com/fwlink/?LinkID=144311). For more information about the $PSModuleAutoloadingPreference variable, see about_Preference_Variables (http://go.microsoft.com/fwlink/?LinkID=113248).

A module is a package that contains members that can be used in Windows PowerShell. Members include cmdlets, providers, scripts, functions, variables, and other tools and files. After a module is imported, you can use the module members in your session.

To import a module, use the Name , Assembly , ModuleInfo , MinimumVersion and RequiredVersion parameters to identify the module to import. By default, Import-Module imports all members that the module exports, but you can use the Alias , Function , Cmdlet , and Variable parameters to restrict the members that are imported. You can also use the NoClobber parameter to prevent Import-Module from importing members that have the same names as members in the current session. Import-Module imports a module only into the current session. To import the module into all sessions, add an Import-Module command to your Windows PowerShell profile. For more information about profiles, see about_Profiles (http://go.microsoft.com/fwlink/?LinkID=113729).

Starting in Windows PowerShell 3.0, you can use Import-Module to import Common Information Model (CIM) modules, in which the cmdlets are defined in Cmdlet Definition XML (CDXML) files. This feature allows you to use cmdlets that are implemented in non-managed code assemblies, such as those written in C++.

With these new features, Import-Module cmdlet becomes a primary tool for managing heterogeneous enterprises that include computers that run the Windows operating system and computers that are running other operating systems.

To manage remote computers that run the Windows operating system that have Windows PowerShell and Windows PowerShell remoting enabled, create a PSSession on the remote computer and then use the PSSession parameter of Get-Module to get the Windows PowerShell modules in the PSSession . When you import the modules, and then use the imported commands in the current session, the commands run implicitly in the PSSession on the remote computer. You can use this strategy to manage the remote computer.

You can use a similar strategy to manage computers that do not have Windows PowerShell remoting enabled, including computers that are not running the Windows operating system, and Windows computers that have Windows PowerShell, but do not have Windows PowerShell remoting enabled.

Start by creating a CIM session on the remote computer, which is a connection to Windows Management Instrumentation (WMI) on the remote computer. Then use the CIMSession parameter of Import-Module to import CIM modules from the remote computer. When you import a CIM module and then run the imported commands, the commands run implicitly on the remote computer. You can use this WMI and CIM strategy to manage the remote computer.

Parameters

-Alias <String[]>

Default value is None
Accepts pipeline input False

Specifies the aliases that this cmdlet imports from the module into the current session. Enter a comma-separated list of aliases. Wildcard characters are permitted.

Some modules automatically export selected aliases into your session when you import the module. This parameter lets you select from among the exported aliases.

-ArgumentList <Object[]>

Default value is None
Accepts pipeline input False

Specifies an array of arguments, or parameter values, that are passed to a script module during the Import-Module command. This parameter is valid only when you are importing a script module.

You can also refer to the ArgumentList parameter by its alias, args .

-AsCustomObject [<SwitchParameter>]

Default value is False
Accepts pipeline input False

Indicates that this cmdlet returns a custom object with members that represent the imported module members. This parameter is valid only for script modules.

When you use the AsCustomObject parameter, Import-Module imports the module members into the session and then returns a PSCustomObject object instead of a PSModuleInfo object. You can save the custom object in a variable and use dot notation to invoke the members.

-Assembly <Assembly[]>

This value is required
Default value is None
Accepts pipeline input ByValue

Specifies an array of assembly objects. This cmdlet imports the cmdlets and providers implemented in the specified assembly objects. Enter a variable that contains assembly objects or a command that creates assembly objects. You can also pipe an assembly object to Import-Module .

When you use this parameter, only the cmdlets and providers implemented by the specified assemblies are imported. If the module contains other files, they are not imported, and you might be missing important members of the module. Use this parameter for debugging and testing the module, or when you are instructed to use it by the module author.

-CimNamespace <String>

Default value is None
Accepts pipeline input False

Specifies the namespace of an alternate CIM provider that exposes CIM modules. The default value is the namespace of the Module Discovery WMI provider.

Use this parameter to import CIM modules from computers and devices that are not running a Windows operating system.

This parameter was introduced in Windows PowerShell 3.0.

-CimResourceUri <Uri>

Default value is None
Accepts pipeline input False

Specifies an alternate location for CIM modules. The default value is the resource URI of the Module Discovery WMI provider on the remote computer.

Use this parameter to import CIM modules from computers and devices that are not running a Windows operating system.

This parameter was introduced in Windows PowerShell 3.0.

-CimSession <CimSession>

This value is required
Default value is None
Accepts pipeline input False

Specifies a CIM session on the remote computer. Enter a variable that contains the CIM session or a command that gets the CIM session, such as a Get-CIMSessionhttp://go.microsoft.com/fwlink/?LinkId=227966 command. Import-Module uses the CIM session connection to import modules from the remote computer into the current session. When you use the commands from the imported module in the current session, the commands actually run on the remote computer.

You can use this parameter to import modules from computers and devices that are not running the Windows operating system, and Windows computers that have Windows PowerShell, but do not have Windows PowerShell remoting enabled.

This parameter was introduced in Windows PowerShell 3.0.

-Cmdlet <String[]>

Default value is None
Accepts pipeline input False

Specifies an array of cmdlets that this cmdlet imports from the module into the current session. Wildcard characters are permitted.

Some modules automatically export selected cmdlets into your session when you import the module. This parameter lets you select from among the exported cmdlets.

-DisableNameChecking [<SwitchParameter>]

Default value is False
Accepts pipeline input False

Indicates that this cmdlet suppresses the message that warns you when you import a cmdlet or function whose name includes an unapproved verb or a prohibited character.

By default, when a module that you import exports cmdlets or functions that have unapproved verbs in their names, Windows PowerShell displays the following warning message:

"WARNING: Some imported command names include unapproved verbs which might make them less discoverable. Use the Verbose parameter for more detail or type Get-Verb to see the list of approved verbs."

This message is only a warning. The complete module is still imported, including the non-conforming commands. Although the message is displayed to module users, the naming problem should be fixed by the module author.

-Force [<SwitchParameter>]

Default value is False
Accepts pipeline input False

Indicates that this cmdlet re-imports a module and its members, even if the module or its members have an access mode of read-only.

-FullyQualifiedName <ModuleSpecification[]>

This value is required
Default value is None
Accepts pipeline input ByValue

Specifies the fully qualified name of the module specification.

-Function <String[]>

Default value is None
Accepts pipeline input False

Specifies an array of functions that this cmdlet imports from the module into the current session. Wildcard characters are permitted.

Some modules automatically export selected functions into your session when you import the module. This parameter lets you select from among the exported functions.

-Global [<SwitchParameter>]

Default value is False
Accepts pipeline input False

Indicates that this cmdlet imports modules into the global session state so they are available to all commands in the session. By default, the commands in a module, including commands from nested modules, are imported into the caller's session state. To restrict the commands that a module exports, use an Export-ModuleMember command in the script module.

The Global parameter is equivalent to the Scope parameter with a value of Global.

-MaximumVersion <String>

Default value is None
Accepts pipeline input False

Specifies a maximum version. This cmdlet imports only a version of the module that is less than or equal to the specified value. If no version qualifies, Import-Module generates an error.

-MinimumVersion <Version>

Default value is None
Accepts pipeline input False

Specifies a minimum version. This cmdlet imports only a version of the module that is greater than or equal to the specified value. If no version qualifies, Import-Module generates an error.

By default, Import-Module imports the module without checking the version number.

Use the MinimumVersion parameter name or its alias, Version.

To specify an exact version, use the RequiredVersion parameter. You can also use the Module and Version parameters of the #Requires keyword to require a specific version of a module in a script.

This parameter was introduced in Windows PowerShell 3.0.

-ModuleInfo <PSModuleInfo[]>

This value is required
Default value is None
Accepts pipeline input ByValue

Specifies an array of module objects to import. Enter a variable that contains the module objects, or a command that gets the module objects, such as the following command: `Get-Module -ListAvailable`. You can also pipe module objects to Import-Module .

-Name <String[]>

This value is required
Default value is None
Accepts pipeline input ByValue

Specifies the names of the modules to import. Enter the name of the module or the name of a file in the module, such as a .psd1, .psm1, .dll, or ps1 file. File paths are optional. Wildcard characters are not permitted. You can also pipe module names and file names to Import-Module .

If you omit a path, Import-Module looks for the module in the paths saved in the PSModulePath environment variable ($env:PSModulePath).

Specify only the module name whenever possible. When you specify a file name, only the members that are implemented in that file are imported. If the module contains other files, they are not imported, and you might be missing important members of the module.

-NoClobber [<SwitchParameter>]

Default value is False
Accepts pipeline input False

Indicates that this cmdlet does not import commands that have the same names as existing commands in the current session. By default, Import-Module imports all exported module commands.

Commands that have the same names can hide or replace commands in the session. To avoid command name conflicts in a session, use the Prefix or NoClobber parameters.

This parameter was introduced in Windows PowerShell 3.0.

-PSSession <PSSession>

This value is required
Default value is None
Accepts pipeline input False

Specifies a Windows PowerShell user-managed session ( PSSession ) from which this cmdlet import modules into the current session. Enter a variable that contains a PSSession or a command that gets a PSSession , such as a Get-PSSession command.

When you import a module from a different session into the current session, you can use the cmdlets from the module in the current session, just as you would use cmdlets from a local module. Commands that use the remote cmdlets actually run in the remote session, but the remoting details are managed in the background by Windows PowerShell.

This parameter uses the Implicit Remoting feature of Windows PowerShell. It is equivalent to using the Import-PSSession cmdlet to import particular modules from a session. Import-Module cannot import Windows PowerShell Core modules from another session. The Windows PowerShell Core modules have names that begin with Microsoft.PowerShell.

This parameter was introduced in Windows PowerShell 3.0.

-PassThru [<SwitchParameter>]

Default value is False
Accepts pipeline input False

Returns an object representing the item with which you are working. By default, this cmdlet does not generate any output.

-Prefix <String>

Default value is None
Accepts pipeline input False

Specifies a prefix that this cmdlet adds to the nouns in the names of imported module members.

Use this parameter to avoid name conflicts that might occur when different members in the session have the same name. This parameter does not change the module, and it does not affect files that the module imports for its own use. These are known as nested modules. This cmdlet affects only the names of members in the current session.

For example, if you specify the prefix UTC and then import a Get-Date cmdlet, the cmdlet is known in the session as Get-UTCDate , and it is not confused with the original Get-Date cmdlet.

The value of this parameter takes precedence over the DefaultCommandPrefix property of the module, which specifies the default prefix.

-RequiredVersion <Version>

Default value is None
Accepts pipeline input False

Specifies a version of the module that this cmdlet imports. If the version is not installed, Import-Module generates an error.

By default, Import-Module imports the module without checking the version number.

To specify a minimum version, use the MinimumVersion parameter. You can also use the Module and Version parameters of the #Requires keyword to require a specific version of a module in a script.

This parameter was introduced in Windows PowerShell 3.0.

Scripts that use RequiredVersion to import modules that are included with existing releases of the Windows operating system do not automatically run in future releases of the Windows operating system. This is because Windows PowerShell module version numbers in future releases of the Windows operating system are higher than module version numbers in existing releases of the Windows operating system.

-Scope <String>

Default value is None
Accepts pipeline input False

Specifies a scope into which this cmdlet imports the module.

The acceptable values for this parameter are:

- Global . Available to all commands in the session. Equivalent to the Global parameter. - Local . Available only in the current scope.

By default, the module is imported into the current scope, which could be a script or module.

This parameter was introduced in Windows PowerShell 3.0.

-Variable <String[]>

Default value is None
Accepts pipeline input False

Specifies an array of variables that this cmdlet imports from the module into the current session. Enter a list of variables. Wildcard characters are permitted.

Some modules automatically export selected variables into your session when you import the module. This parameter lets you select from among the exported variables.

<CommonParameters>

This cmdlet supports the common parameters: Verbose, Debug,ErrorAction, ErrorVariable, WarningAction, WarningVariable,OutBuffer, PipelineVariable, and OutVariable.

Inputs

System.String, System.Management.Automation.PSModuleInfo, System.Reflection.Assembly

You can pipe a module name, module object, or assembly object to this cmldet.

Outputs

None, System.Management.Automation.PSModuleInfo, or System.Management.Automation.PSCustomObject

This cmdlet returns a PSModuleInfo or PSCustomObject . By default, Import-Module does not generate any output. If you specify the PassThru parameter, the cmldet generates a System.Management.Automation.PSModuleInfo object that represents the module. If you specify the AsCustomObject parameter, it generates a PSCustomObject object.

Examples

Import the members of a module into the current session:
```
PS C:\> Import-Module -Name BitsTransfer
```
This command imports the members of the BitsTransfer module into the current session.

The Name parameter name is optional and can be omitted.

By default, Import-Module does not generate any output when it imports a module. To request output, use the PassThru or AsCustomObject parameter, or the Verbose common parameter.
Import all modules specified by the module path:
```
PS C:\> Get-Module -ListAvailable | Import-Module
```
This command imports all available modules in the path specified by the PSModulePath environment variable ($env:PSModulePath) into the current session.
Import the members of several modules into the current session:
```
PS C:\> $m = Get-Module -ListAvailable BitsTransfer, ServerManager
PS C:\> Import-Module -ModuleInfo $m
```
These commands import the members of the BitsTransfer and ServerManager modules into the current session.

The first command uses the Get-Module cmdlet to get the BitsTransfer and ServerManager modules. It saves the objects in the $m variable. The ListAvailable parameter is required when you are getting modules that are not yet imported into the session.

The second command uses the ModuleInfo parameter of Import-Module to import the modules into the current session.

These commands are equivalent to using a pipeline operator (|) to send the output of a Get-Module command to Import-Module .
Import all modules specified by a path:
```
PS C:\> Import-Module -Name c:\ps-test\modules\test -Verbose
VERBOSE: Loading module from path 'C:\ps-test\modules\Test\Test.psm1'.
VERBOSE: Exporting function 'my-parm'.
VERBOSE: Exporting function 'Get-Parameter'.
VERBOSE: Exporting function 'Get-Specification'.
VERBOSE: Exporting function 'Get-SpecDetails'.
```
This command uses an explicit path to identify the module to import.

It also uses the Verbose common parameter to get a list of the items imported from the module. Without the Verbose , PassThru , or AsCustomObject parameter, Import-Module does not generate any output when it imports a module.

Restrict module members imported into a session:

PS C:\> Import-Module BitsTransfer -cmdlet Add-BitsTransferFile, Get-BitsTransfer
PS C:\> Get-Module BitsTransfer

   Name              : BitsTransfer
   Path              : C:\Windows\system32\WindowsPowerShell\v1.0\Modules\BitsTransfer\BitsTransfer.psd1
   Description       :
   Guid              : 8fa5064b-8479-4c5c-86ea-0d311fe48875
   Version           : 1.0.0.0
   ModuleBase        : C:\Windows\system32\WindowsPowerShell\v1.0\Modules\BitsTransfer
   ModuleType        : Manifest
   PrivateData       :
   AccessMode        : ReadWrite
   ExportedAliases   : {}
   ExportedCmdlets   : {[Add-BitsTransfer, Add-BitsTransfer], [Complete-BitsTransfer, Complete-BitsTransfer],
    [Get-BitsTransfer, Get-BitsTransfer], [Remove-BitsTransfer, Remove-BitsTransfer]...}
   ExportedFunctions : {}
   ExportedVariables : {}
   NestedModules     : {Microsoft.BackgroundIntelligentTransfer.Management}

PS C:\> Get-Command -Module BitsTransfer

   CommandType     Name                                               ModuleName
   -----------     ----                                               ----------
   Cmdlet          Add-BitsFile                                       bitstransfer
   Cmdlet          Complete-BitsTransfer                              bitstransfer
   Cmdlet          Get-BitsTransfer                                   bitstransfer
   Cmdlet          Remove-BitsTransfer                                bitstransfer
   Cmdlet          Resume-BitsTransfer                                bitstransfer
   Cmdlet          Set-BitsTransfer                                   bitstransfer
   Cmdlet          Start-BitsTransfer                                 bitstransfer
   Cmdlet          Suspend-BitsTransfer                               bitstransfer

This example shows how to restrict the module members that are imported into the session and the effect of this command on the session.

The first command imports only the Add-BitsTransfer and Get-BitsTransfer cmdlets from the BitsTransfer module. The command uses the Cmdlet parameter to restrict the cmdlets that the module imports. You can also use the Alias , Variable , and Function parameters to restrict other members that a module imports.

The second command uses the Get-Module cmdlet to get the object that represents the BitsTransfer module. The ExportedCmdlets property lists all of the cmdlets that the module exports, even when they were not all imported.

The third command uses the Module parameter of the Get-Command cmdlet to get the commands that were imported from the BitsTransfer module. The results confirm that only the Add-BitsTransfer and Get-BitsTransfer cmdlets were imported.

Import the members of a module and add a prefix:

PS C:\> Import-Module BitsTransfer -Prefix PS -PassThru

   ModuleType Name                                ExportedCommands
   ---------- ----                                ----------------
   Manifest   bitstransfer                        {Add-BitsFile, Complete-...

PS C:\> Get-Command -Module BitsTransfer

   CommandType     Name                                               ModuleName
   -----------     ----                                               ----------
   Cmdlet          Add-BitsFile                                       bitstransfer
   Cmdlet          Add-PSBitsFile                                     bitstransfer
   Cmdlet          Complete-BitsTransfer                              bitstransfer
   Cmdlet          Complete-PSBitsTransfer                            bitstransfer
   Cmdlet          Get-BitsTransfer                                   bitstransfer
   Cmdlet          Get-PSBitsTransfer                                 bitstransfer
   Cmdlet          Remove-BitsTransfer                                bitstransfer
   Cmdlet          Remove-PSBitsTransfer                              bitstransfer
   Cmdlet          Resume-BitsTransfer                                bitstransfer
   Cmdlet          Resume-PSBitsTransfer                              bitstransfer
   Cmdlet          Set-BitsTransfer                                   bitstransfer
   Cmdlet          Set-PSBitsTransfer                                 bitstransfer
   Cmdlet          Start-BitsTransfer                                 bitstransfer
   Cmdlet          Start-PSBitsTransfer                               bitstransfer
   Cmdlet          Suspend-BitsTransfer                               bitstransfer
   Cmdlet          Suspend-PSBitsTransfer                             bitstransfer

These commands import the BitsTransfer module into the current session, add a prefix to the member names, and then display the prefixed member names.

The first command uses the Import-Module cmdlet to import the BitsTransfer module. It uses the Prefix parameter to add the PS prefix to all members that are imported from the module and the PassThru parameter to return a module object that represents the imported module.

The second command uses the Get-Command cmdlet to get the members that have been imported from the module. It uses the Module parameter to specify the module. The output shows that the module members were correctly prefixed.

The prefix that you use applies only to the members in the current session. It does not change the module.

Get and use a custom object:
```
PS C:\> Get-Module -List | Format-Table -Property Name, ModuleType -AutoSize

   Name          ModuleType
   ----          ----------
   Show-Calendar     Script
   BitsTransfer    Manifest
   PSDiagnostics   Manifest
   TestCmdlets       Script

PS C:\> $a = Import-Module -Name Show-Calendar -AsCustomObject -Passthru


PS C:\> $a | Get-Member

       TypeName: System.Management.Automation.PSCustomObject
   Name          MemberType   Definition
   ----          ----------   ----------
   Equals        Method       bool Equals(System.Object obj)
   GetHashCode   Method       int GetHashCode()
   GetType       Method       type GetType()
   ToString      Method       string ToString()
   Show-Calendar ScriptMethod System.Object Show-Calendar();

PS C:\> $a."Show-Calendar"()
```
These commands demonstrate how to get and use the custom object that Import-Module returns.

Custom objects include synthetic members that represent each of the imported module members. For example, the cmdlets and functions in a module are converted to script methods of the custom object.

Custom objects are very useful in scripting. They are also useful when several imported objects have the same names. Using the script method of an object is equivalent to specifying the fully qualified name of an imported member, including its module name.

The AsCustomObject parameter can be used only when importing a script module, so the first task is to determine which of the available modules is a script module.

The first command uses the Get-Module cmdlet to get the available modules. The command uses a pipeline operator to pass the module objects to the Format-Table cmdlet, which lists the Name and ModuleType of each module in a table.

The second command uses the Import-Module cmdlet to import the PSDiagnostics script module. The command uses the AsCustomObject parameter to request a custom object and the PassThru parameter to return the object. The command saves the resulting custom object in the $a variable.

The third command uses a pipeline operator to send the $a variable to the Get-Member cmdlet, which gets the properties and methods of the PSCustomObject in $a. The output shows a Show-Calendar script method.

The last command uses the Show-Calendar script method. The method name must be enclosed in quotation marks, because it includes a hyphen.
Re-import a module into the same session:
```
PS C:\> Import-Module BitsTransfer
PS C:\> Import-Module BitsTransfer -Force -Prefix PS
```
This example shows how to use the Force parameter of Import-Module when you are re-importing a module into the same session.

The first command imports the BitsTransfer module. The second command imports the module again, this time using the Prefix parameter.

The second command also includes the Force parameter, which removes the module and then imports it again. Without this parameter, the session would include two copies of each BitsTransfer cmdlet, one with the standard name and one with the prefixed name.
Run commands that have been hidden by imported commands:
```
PS C:\> Get-Date
Thursday, March 15, 2012 6:47:04 PM


PS C:\> Import-Module TestModule


PS C:\> Get-Date
12075


PS C:\> Get-Command Get-Date -All | Format-Table -Property CommandType, Name, ModuleName -AutoSize

   CommandType     Name         ModuleName
   -----------     ----         ----------
   Function        Get-Date     TestModule
   Cmdlet          Get-Date     Microsoft.PowerShell.Utility

PS C:\> Microsoft.PowerShell.Utility\Get-Date
Saturday, September 12, 2009 6:33:23 PM
```
This example shows how to run commands that have been hidden by imported commands.

The first command run the Get-Date cmdlet. It returns a DateTime object with the current date.

The second command imports the TestModule module. This module includes a function named Get-Date that returns the year and day of the year.

The third command runs the Get-Date command again. Because functions take precedence over cmdlets, the Get-Date function from the TestModule module runs, instead of the Get-Date cmdlet.

The fourth command uses the All parameter of the Get-Command to get all of the Get-Date commands in the session. The results show that there are two Get-Date commands in the session, a function from the TestModule module and a cmdlet from the Microsoft.PowerShell.Utility module.

The fifth command runs the hidden cmdlet by qualifying the command name with the module name.

For more information about command precedence in Windows PowerShell, see about_Command_Precedence (http://go.microsoft.com/fwlink/?LinkID=113214).
Import a minimum version of a module:
```
PS C:\> Import-Module -Name PSWorkflow -MinimumVersion 3.0.0.0
```
This command imports the PSWorkflow module. It uses the MinimumVersion parameter of Import-Module to import only version 3.0.0.0 or greater of the module.

You can also use the RequiredVersion parameter to import a particular version of a module, or use the Module and Version parameters of the #Requires keyword to require a particular version of a module in a script.
Import a module from a remote computer:
1. The first command uses the New-PSSession cmdlet to create a remote session (**PSSession**) to the Server01 computer:
```
PS C:\> $s = New-PSSession -ComputerName Server01
```
  The command saves the **PSSession** in the $s variable.
2. The second command uses the *PSSession* parameter of the Get-Module cmdlet to get the **NetSecurity** module in the session in the $s variable.This command is equivalent to using the Invoke-Command cmdlet to run a **Get-Module** command in the session in $s ([CODE_Snippit]Invoke-Command $s {Get-Module -ListAvailable -Name NetSecurity[CODE_Snippit]).The output shows that the **NetSecurity** module is installed on the computer and is available to the session in the $s variable:
```
PS C:\> Get-Module -PSSession $s -ListAvailable -Name NetSecurity

   ModuleType Name                                ExportedCommands
   ---------- ----                                ----------------
   Manifest   NetSecurity                         {New-NetIPsecAuthProposal, New-NetIPsecMainModeCryptoProposal, 
   New-Ne...
```
3. The third command uses the *PSSession* parameter of the **Import-Module** cmdlet to import the **NetSecurity** module from the session in the $s variable into the current session:
```
PS C:\> Import-Module -PSSession $s -Name NetSecurity
```
4. The fourth command uses the **Get-Command** cmdlet to get commands that begin with "Get" and include "Firewall" from the Net-Security module.The output gets the commands and confirms that the module and its cmdlets were imported into the current session:
```
PS C:\> Get-Command -Module NetSecurity -Name Get-*Firewall*

   CommandType     Name                                               ModuleName
   -----------     ----                                               ----------
   Function        Get-NetFirewallAddressFilter                       NetSecurity
   Function        Get-NetFirewallApplicationFilter                   NetSecurity
   Function        Get-NetFirewallInterfaceFilter                     NetSecurity
   Function        Get-NetFirewallInterfaceTypeFilter                 NetSecurity
   Function        Get-NetFirewallPortFilter                          NetSecurity
   Function        Get-NetFirewallProfile                             NetSecurity
   Function        Get-NetFirewallRule                                NetSecurity
   Function        Get-NetFirewallSecurityFilter                      NetSecurity
   Function        Get-NetFirewallServiceFilter                       NetSecurity
   Function        Get-NetFirewallSetting                             NetSecurity
```
5. The fifth command uses the **Get-NetFirewallRule** cmdlet to get Windows Remote Management firewall rules on the Server01 computer:
```
PS C:\> Get-NetFirewallRule -DisplayName "Windows Remote Management*" | Format-Table -Property DisplayName, Name -AutoSize

   DisplayName                                              Name
   -----------                                              ----
   Windows Remote Management (HTTP-In)                      WINRM-HTTP-In-TCP
   Windows Remote Management (HTTP-In)                      WINRM-HTTP-In-TCP-PUBLIC
   Windows Remote Management - Compatibility Mode (HTTP-In) WINRM-HTTP-Compat-In-TCP
```
  This command is equivalent to using the Invoke-Command cmdlet to run a **Get-NetFirewallRule** command on the session in the $s variable ([CODE_Snippit]Invoke-Command -Session $s {Get-NetFirewallRule -DisplayName "Windows Remote Management*"[CODE_Snippit]}).This example shows how to use the Import-Module cmdlet to import a module from a remote computer. This command uses the Implicit Remoting feature of Windows PowerShell.
  
  When you import modules from another session, you can use the cmdlets in the current session. However, commands that use the cmdlets actually run in the remote session.
Manage storage on a remote computer without the Windows operating system:
1. The first command uses the **New-CimSession** cmdlet to create a session on the RSDGF03 remote computer:
```
PS C:\> $cs = New-CimSession -ComputerName RSDGF03
```
  The session connects to WMI on the remote computer. The command saves the CIM session in the $cs variable.
2. The second command uses the CIM session in the $cs variable to run an **Import-Module** command on the RSDGF03 computer:
```
PS C:\> Import-Module -CimSession $cs -Name Storage
```
  The command uses the *Name* parameter to specify the **Storage** CIM module.
3. The third command runs the **Get-Command** command on the **Get-Disk** command in the **Storage** module.When you import a CIM module into the local session, Windows PowerShell converts the CDXML files for each command into Windows PowerShell scripts, which appear as functions in the local session:
```
PS C:\> Get-Command Get-Disk

   CommandType     Name                  ModuleName
   -----------     ----                  ----------
   Function        Get-Disk              Storage
```
4. The fourth command runs the **Get-Disk** command:
```
PS C:\> Get-Disk

   Number Friendly Name              OperationalStatus          Total Size Partition Style
   ------ -------------              -----------------          ---------- ---------------
   0      Virtual HD ATA Device      Online                          40 GB MBR
```
  Although the command is typed in the local session, it runs implicitly on the remote computer from which it was imported.The command gets objects from the remote computer and returns them to the local session.The commands in this example enable you to manage the storage systems of a remote computer that is not running the Windows operating system. In this example, because the administrator of the computer has installed the Module Discovery WMI provider, the CIM commands can use the default values, which are designed for the provider.

Additional Notes

 * Before you can import a module, the module must be installed on the local computer. That is, the module 
 directory must be copied to a directory that is accessible to your local computer. For more information, see 
 about_Modules (http://go.microsoft.com/fwlink/?LinkID=144311).

 You can also use the PSSession and CIMSession parameters to import modules that are installed on remote 
 computers. However, commands that use the cmdlets in these modules actually run in the remote session on the 
 remote computer.

 * If you import members with the same name and the same type into your session, Windows PowerShell uses the 
 member imported last by default. Variables and aliases are replaced, and the originals are not accessible. 
 Functions, cmdlets and providers are merely shadowed by the new members. They can be accessed by qualifying 
 the command name with the name of its snap-in, module, or function path. To update the formatting data for 
 commands that have been imported from a module, use the Update-FormatData cmdlet. Update-FormatData also 
 updates the formatting data for commands in the session that were imported from modules. If the formatting 
 file for a module changes, you can run an Update-FormatData * command to update the formatting data for 
 imported commands. You do not need to import the module again. Starting in Windows PowerShell 3.0, the core 
 commands that are installed with Windows PowerShell are packaged in modules. In Windows PowerShell 2.0, and in 
 host programs that create older-style sessions in later versions of Windows PowerShell, the core commands are 
 packaged in snap-ins ( PSSnapins ). The exception is Microsoft.PowerShell.Core *, which is always a snap-in. 
 Also, remote sessions, such as those started by the New-PSSession cmdlet, are older-style sessions that 
 include core snap-ins.

 For information about the CreateDefault2 method that creates newer-style sessions with core modules, see 
 "CreateDefault2 Methodhttp://msdn.microsoft.com/en-us/library/windows/desktop/system.management.automation.runs
 paces.initialsessionstate.createdefault2(v=VS.85).aspx (http://msdn.microsoft.com/en-us/library/windows/desktop
 /system.management.automation.runspaces.initialsessionstate.createdefault2(v=VS.85).aspx) in the Microsoft 
 Developer Network (MSDN) library.  Import-Module * cannot import Windows PowerShell Core modules from another 
 session. The Windows PowerShell Core modules have names that begin with Microsoft.PowerShell. In Windows 
 PowerShell 2.0, some of the property values of the module object, such as the ExportedCmdlets and 
 NestedModules property values, were not populated until the module was imported and were not available on the 
 module object that the PassThru* parameter returns. In Windows PowerShell 3.0, all module property values are 
 populated. If you attempt to import a module that contains mixed-mode assemblies that are not compatible with 
 Windows PowerShell 3.0, Import-Module * returns an error message like the following one.

 `Import-Module : Mixed mode assembly is built against version 'v2.0.50727' of the runtime and cannot be loaded 
 in the 4.0 runtime without additional configuration information.`

 This error occurs when a module that is designed for Windows PowerShell 2.0 contains at least one mixed-module 
 assembly, that is, an assembly that includes both managed and non-managed code, such as C++ and C#.

 To import a module that contains mixed-mode assemblies, start Windows PowerShell 2.0 by using the following 
 command, and then try the Import-Module command again.

 `PowerShell.exe -Version 2.0`

 * To use the CIM session feature, the remote computer must have WS-Management remoting and Windows Management 
 Instrumentation (WMI), which is the Microsoft implementation of the Common Information Model (CIM) standard. 
 The computer must also have the Module Discovery WMI provider or an alternate CIM provider that has the same 
 basic features.

 You can use the CIM session feature on computers that are not running a Windows operating system and on 
 Windows computers that have Windows PowerShell, but do not have Windows PowerShell remoting enabled.

 You can also use the CIM parameters to get CIM modules from computers that have Windows PowerShell remoting 
 enabled, including the local computer. When you create a CIM session on the local computer, Windows PowerShell 
 uses DCOM, instead of WMI, to create the session.

This work is licensed under a Creative Commons Attribution 4.0 International. It is attributed to Microsoft Corporation and can be found here.

PowerShell Commands