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 returns an error.
Specifies a minimum version. This cmdlet imports only a version of the module that is greater than or equal to the specified value. Use the MinimumVersion parameter name or its alias, Version. If no version qualifies, Import-Module generates an error. 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.
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.
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. File paths are optional. Wildcard characters aren't permitted. You can also pipe module names and filenames to Import-Module. Specify only the module name whenever possible. When you specify a file name, only the members that are implemented in that file are imported.
While it is possible to import a script. Importing a script file does not guarantee that it is usable as a module. Prevents importing 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.
Returns an object representing the item with which you're working. By default, this cmdlet does not generate any output. 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.
The value of this parameter takes precedence over the DefaultCommandPrefix property of the module, which specifies the default prefix. Specifies a PowerShell user-managed session PSSession from which this cmdlet imports modules into the current session.
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 run in the remote session, but the remoting details are managed in the background by PowerShell. This parameter uses the Implicit Remoting feature of PowerShell. It is equivalent to using the Import-PSSession cmdlet to import particular modules from a session.
Import-Module cannot import core PowerShell modules from another session. The core PowerShell modules have names that begin with Microsoft. Specifies a version of the module that this cmdlet imports. If the version is not installed, Import-Module generates an error.
To specify a minimum version, use the MinimumVersion parameter. Scripts that use RequiredVersion to import modules that are included with existing releases of the Windows operating system don't automatically run in future releases of the Windows operating system. This is because 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.
You can use the -Scope Local parameter to import module content into the script or scriptblock scope. When invoked from another module, Import-Module cmdlet imports the commands in a module, including commands from nested modules, into the caller's session state. Specifying -Scope Global or -Global indicates that this cmdlet imports modules into the global session state so they are available to all commands in the session.
When importing a module from another path, this switch does nothing, since the check is not performed. On Linux and macOS, this switch does nothing.
Import-Module -SkipEditionCheck is still likely to fail to import a module. Even if it does succeed, invoking a command from the module may later fail when it tries to use an incompatible API. Loads module using Windows PowerShell Compatibility functionality. Specifies an array of variables that this cmdlet imports from the module into the current session.
Enter a list of variables. Some modules automatically export selected variables into your session when you import the module. This parameter lets you select from among the exported variables.
String, System. PSModuleInfo, System. None, System. PSModuleInfo, or System. By default, Import-Module does not generate any output. If you specify the PassThru parameter, the cmdlet generates a System. PSModuleInfo object that represents the module. 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. However, commands that use the cmdlets in these modules run in the remote session on the remote computer.
If you import members with the same name and the same type into your session, PowerShell uses the member imported last by default. Variables and aliases are replaced, and the originals aren't 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 don't need to import the module again. In Windows PowerShell 2. The exception is Microsoft. 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 the CreateDefault2 Method.
If you attempt to import a module that contains mixed-mode assemblies that aren't compatible with Windows PowerShell 3. Import-Module : Mixed mode assembly is built against version 'v2.
This error occurs when a module that is designed for Windows PowerShell 2. To import a module that contains mixed-mode assemblies, start Windows PowerShell 2. You can use the CIM session feature on computers that aren't running a Windows operating system and on Windows computers that have PowerShell, but don't have PowerShell remoting enabled. By default, Import-Module imports modules in the global scope even when called from a descendant scope.
The top-level scope and all descendant scopes have access to the module's exported elements. In a descendant scope, -Scope Local limits the import to that scope and all its descendant scopes. Parent scopes then do not see the imported members.
Get-Module shows all modules loaded in the current session. This includes modules loaded locally in a descendant scope. Use Get-Command -Module modulename to see which members are loaded in the current scope. Import-Module does not load class and enum definitions in the module. Use the using module statement at the beginning of your script. This imports the module, including the class and enum definitions.
Skip to main content. This browser is no longer supported. Download Microsoft Edge More info. Contents Exit focus mode. Import-Module Reference Is this page helpful? Please rate your experience Yes No. Any additional feedback? Module: Microsoft. This parameter was introduced in Windows PowerShell 3. By default, when a module that you import exports cmdlets or functions that have unapproved verbs in their names, PowerShell displays the following warning message: WARNING: Some imported command names include unapproved verbs which might make them less discoverable.
This parameter causes a module to be loaded, or reloaded, over top of the current one. ModuleName - Required Specifies the module name. It's also Required to specify one of the three below keys. These keys can't be used together. ModuleVersion - Specifies a minimum acceptable version of the module. RequiredVersion - Specifies an exact, required version of the module. MaximumVersion - Specifies the maximum acceptable version of the module. Tip You should avoid calling Import-Module from within a module.
Note While it is possible to import a script. Specifies a prefix that this cmdlet adds to the nouns in the names of imported module members. By default, Import-Module imports the module without checking the version number.
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. Available only in the current scope. Skips the check on the CompatiblePSEditions field. Note Get-Module shows all modules loaded in the current session. Submit and view feedback for This product This page. View all page feedback.
In this article. String [ ]. In the end there was a problem something, possibly chocolatey? Stack Overflow for Teams — Collaborate and share knowledge with a private group. Create a free Team What is Teams? Collectives on Stack Overflow. Learn more. Asked 5 years, 6 months ago. Active 4 months ago. Viewed 32k times. I have IIS 7. Improve this question. Richard 6, 5 5 gold badges 41 41 silver badges 58 58 bronze badges. Klee Klee 1, 3 3 gold badges 21 21 silver badges 32 32 bronze badges.
Add a comment. Active Oldest Votes. Improve this answer. Community Bot 1 1 1 silver badge. Richard Richard 6, 5 5 gold badges 41 41 silver badges 58 58 bronze badges. Thanks for your response Richard. I can even use it from the shell. Just when I run the script it can't be imported. Any idea on that? Klee I have updated my question with some things you could try.
The first answer would have likely worked. The other two I had already tried. In the end there was a problem, possibly with chocolatey? Digweed Digweed 41 2 2 bronze badges. This should be the accepted answer — Kennet Celeste. Have a look at Richard's answer for some other good suggestions.
0コメント