Export (0) Print
Expand All

Import-WdsDriverPackage

Windows Server 2012 R2 and Windows 8.1

Updated: October 17, 2013

Applies To: Windows 8.1, Windows PowerShell 4.0, Windows Server 2012 R2

Import-WdsDriverPackage

Imports a driver package into the Windows Deployment Services driver store.

Syntax

Parameter Set: Import0
Import-WdsDriverPackage -Path <String> [-Architecture <Architecture> ] [-AsJob] [-CimSession <CimSession[]> ] [-DisplayName <String> ] [-GroupName <String> ] [-ThrottleLimit <Int32> ] [ <CommonParameters>]




Detailed Description

The Import-WdsDriverPackage cmdlet imports a driver package into the Windows Deployment Services driver store. Specify the .inf file for the driver package to import.

You can specify a display name for the driver package. You can assign it to a driver group. If you want to assign a driver package to a group at a later time, use the Add-WdsDriverPackage cmdlet. A client must have access to at least one group that a driver package belongs to in order to install it.

If the package contains drivers for multiple architectures, you can specify a single architecture. If you do not specify an architecture, the cmdlet adds all the architectures.

Parameters

-Architecture<Architecture>

Specifies an architecture. This is the architecture of the driver package to add to the server. If you do not specify this parameter, the cmdlet includes all the architectures it finds. The acceptable values for this parameter are: 

-- Arm
-- Ia64
-- X64
-- X86


Aliases

none

Required?

false

Position?

named

Default Value

none

Accept Pipeline Input?

false

Accept Wildcard Characters?

false

-AsJob

Runs the cmdlet as a background job. Use this parameter to run commands that take a long time to complete. The cmdlet immediately returns an object that represents the job and then displays the command prompt. You can continue to work in the session while the job completes. To manage the job, use the *-Job cmdlets. To get the job results, use the Receive-Job cmdlet. For more information about Windows PowerShell® background jobs, see about_Jobs.


Aliases

none

Required?

false

Position?

named

Default Value

none

Accept Pipeline Input?

false

Accept Wildcard Characters?

false

-CimSession<CimSession[]>

Runs the cmdlet in a remote session or on a remote computer. Enter a computer name or a session object, such as the output of a New-CimSession or Get-CimSession cmdlet. The default is the current session on the local computer.


Aliases

Session

Required?

false

Position?

named

Default Value

none

Accept Pipeline Input?

false

Accept Wildcard Characters?

false

-DisplayName<String>

Specifies a display name for the driver package. If you do not supply a display name, the cmdlet creates one based on the driver name and architecture.


Aliases

none

Required?

false

Position?

named

Default Value

none

Accept Pipeline Input?

false

Accept Wildcard Characters?

false

-GroupName<String>

Specifies the name of a driver group. The cmdlet adds the driver package to this group.


Aliases

none

Required?

false

Position?

named

Default Value

none

Accept Pipeline Input?

false

Accept Wildcard Characters?

false

-Path<String>

Specifies an absolute path. This is the path an .inf file. The cmdlet imports the driver package from this file.


Aliases

none

Required?

true

Position?

named

Default Value

none

Accept Pipeline Input?

True (ByValue)

Accept Wildcard Characters?

false

-ThrottleLimit<Int32>

Specifies the maximum number of concurrent operations that can be established to run the cmdlet. If this parameter is omitted or a value of 0 is entered, then Windows PowerShell® calculates an optimum throttle limit for the cmdlet based on the number of CIM cmdlets that are running on the computer. The throttle limit applies only to the current cmdlet, not to the session or to the computer.


Aliases

none

Required?

false

Position?

named

Default Value

none

Accept Pipeline Input?

false

Accept Wildcard Characters?

false

<CommonParameters>

This cmdlet supports the common parameters: -Verbose, -Debug, -ErrorAction, -ErrorVariable, -OutBuffer, and -OutVariable. For more information, see    about_CommonParameters.

Inputs

The input type is the type of the objects that you can pipe to the cmdlet.

Outputs

The output type is the type of the objects that the cmdlet emits.

  • Microsoft.Management.Infrastructure.CimInstance#MSFT_WdsDriverPackage

Examples

Example 1: Import a driver package for the x64 architecture

This command imports a driver package for the x64 architecture into the Windows Deployment Services driver store from the specified .inf file. The command specifies a display name for the driver package and assigns the package to the Drivers for Fabrikam Devices group.


PS C:\> Import-WdsDriverPackage -Path "D:\Drivers\Fabrikam.inf" -Architecture X64 -DisplayName "Fabrikam Device Driver (x64)" -GroupName "Drivers for Fabrikam Devices"

Related topics

Was this page helpful?
(1500 characters remaining)
Thank you for your feedback
Show:
© 2014 Microsoft