text stringlengths 0 4.23k |
|---|
wdsutil get-alldrivergroups command |
Displays information about all the driver groups on server. |
wdsutil get-drivergroup command |
Displays information about driver groups on a server. |
wdsutil get-alldriverpackages command |
Displays information about all the driver packages on a server that match the specified search criteria. |
wdsutil get-driverpackagefile command |
Displays information about a driver package, including the drivers and files it contains. |
wdsutil initialize-server |
Applies to: Windows Server 2022, Windows Server 2019, Windows Server 2016, Windows Server 2012 R2, Windows Server 2012 |
Configures a Windows Deployment Services server for initial use after the server role has been installed. After you run this command, you should use the wdsutil add-Image command command to add images to the server. |
Syntax |
wdsutil /Initialize-Server [/Server:<Server name>] /remInst:<Full path> [/Authorize] |
Parameters |
Parameter |
Description |
[/Server:<Server name>] |
Specifies the name of the server. This can be either the NetBIOS name or the fully qualified domain name (FQDN). If no server name is specified, the local server will be used. |
/remInst:<Full path> |
Specifies the full path and name of the remoteInstall folder. If the specified folder does not already exist, this option will create it when the command is run. You should always enter a local path, even in the case of a remote computer. For example: D:\remoteInstall. |
[/Authorize] |
Authorizes the server in Dynamic Host Control Protocol (DHCP). This option is necessary only if DHCP rogue detection is enabled, meaning that the Windows Deployment Services PXE server must be authorized in DHCP before client computers can be serviced. Note that DHCP rogue detection is disabled by default. |
Examples |
To initialize the server and set the remoteInstall shared folder to the F: drive, type. |
wdsutil /Initialize-Server /remInst:F:\remoteInstall |
To initialize the server and set the remoteInstall shared folder to the C: drive, type. |
wdsutil /verbose /Progress /Initialize-Server /Server:MyWDSServer /remInst:C:\remoteInstall |
new-CaptureImage |
Creates a new capture image from an existing boot image. Capture images are boot images that start the Windows Deployment Services capture utility instead of starting Setup. When you boot a reference computer (that has been prepared with Sysprep) into a capture image, a wizard creates an install image of the reference computer and saves it as a Windows Image (.wim) file. You can also add the image to media (such as a CD, DVD, or USB drive), and then boot a computer from that media. After you create the install image, you can add the image to the server for PXE boot deployment. For more information, see Creating Images (https://go.microsoft.com/fwlink/?LinkId=115311). |
Syntax |
wdsutil [Options] /New-CaptureImage [/Server:<Server name>] |
/Image:<Image name> |
/Architecture:{x86 | ia64 | x64} |
[/Filename:<File name>] |
/DestinationImage |
/FilePath:<File path and name> |
[/Name:<Name>] |
[/Description:<Description>] |
[/Overwrite:{Yes | No | Append}] |
[/UnattendFilePath:<File path>] |
Parameters |
Parameter |
Description |
[/Server:<Server name>] |
Specifies the name of the server. This can be either the NetBIOS name or the fully qualified domain name (FQDN). If no server name is specified, the local server will be used. |
/Image:<Image name> |
Specifies the name of the source boot image. |
/Architecture: {x86 |
ia64 |
[/Filename: <Filename>] |
If the image cannot be uniquely identified by name, you must use this option to specify the file name. |
/DestinationImage |
Specifies the settings for the destination image. You specify the settings using the following options:- /FilePath: <File path and name> Sets the full file path for the new capture image.- [/Name: <Name>] - Sets the display name of the image. If no display name is specified, the display name of the source image will be used.- [/Description: <Description>] - Sets the description of the image.- [/Overwrite: {Yes |
Examples |
To create a capture image and name it WinPECapture.wim, type: |
wdsutil /New-CaptureImage /Image:WinPE boot image /Architecture:x86 /DestinationImage /FilePath:C:\Temp\WinPECapture.wim |
To create a capture image and apply the specified settings, type: |
wdsutil /Verbose /Progress /New-CaptureImage /Server:MyWDSServer /Image:WinPE boot image /Architecture:x64 /Filename:boot.wim |
/DestinationImage /FilePath:\\Server\Share\WinPECapture.wim /Name:New WinPE image /Description:WinPE image with capture utility /Overwrite:No /UnattendFilePath:\\Server\Share\WDSCapture.inf |
new-DiscoverImage |
Creates a new discover image from an existing boot image. Discover images are boot images that force the Setup.exe program to start in Windows Deployment Services mode and then discover a Windows Deployment Services server. Typically these images are used to deploy images to computers that are not capable of booting to PXE. For more information, see Creating Images (https://go.microsoft.com/fwlink/?LinkId=115311). |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.