This section contains procedures for the tasks that are listed and described in the following table. Note that you cannot manage a Windows Deployment Services server running Windows Server 2008 from a Windows Deployment Services server running Windows Server 2003.

Note

To download the Windows Deployment Services documentation (including a getting started guide, deployment guide, and WDSUTIL command-line syntax), see http://go.microsoft.com/fwlink/?LinkId=89381.
Note

Help for WDSUTIL is available by typing WDSUTIL /? at a command prompt or online at http://go.microsoft.com/fwlink/?LinkId=112194.
Type Procedure

General Tasks

  • To configure Windows Deployment Services

  • To start or stop the server

  • To enable the server

  • To enable logging for the Windows Deployment Services client

  • To choose the port number for RPC

  • To specify the network interfaces for Windows Deployment Services to listen on

  • To configure how often the server refreshes its settings

  • To force the server to update files in the RemoteInstall folder

  • To configure the network profile for the server

  • To back up the server data

DHCP

  • To configure Windows Deployment Services to run on the same computer as Microsoft DHCP

  • To configure Windows Deployment Services to run on the same computer as non-Microsoft DHCP

  • To turn on the DHCP authorization requirement

  • To authorize the server in DHCP

Client Requests

  • To configure the server to answer clients

  • To set a delay in the server’s answers to PXE requests

  • To configure unknown clients to perform PXE boots without requiring F12

  • To configure clients who have booted without F12 to require a key press on subsequent boots

  • To configure the server to determine the architecture of booting clients

Client Boot Settings

  • To choose which boot images are displayed on x64-based computers

  • To choose the default network boot program for each architecture

  • To choose the default network boot program that does not require F12 for each architecture

  • To choose the default boot image for each architecture

Active Directory Domain Services

  • To specify a domain controller for Windows Deployment Services

  • To specify a global catalog server for Windows Deployment Services

  • To choose whether to search for computer accounts in the domain controller before searching the global catalog

  • To configure the server to prestage clients by using their MAC address instead of their GUID

  • To maintain a list of GUIDs that belong to multiple computers

  • To specify how to generate client computer names

  • To specify the domain and OU in which to create client computer accounts

  • To choose whether to join client computers to the domain

Unattend File

  • To choose a default unattend file for the Windows Deployment Services client

  • To specify whether an unattend file on the client computer overrides the default unattend file

General Tasks

To configure Windows Deployment Services

Using the MMC Using WDSUTIL
  1. Install Windows Deployment Services. For more information, see the Windows Deployment Services Getting Started Guide.

  2. Click Start, click Administrative  Tools, and then click Windows Deployment Services.

  3. In the left pane of the Windows Deployment Services snap-in, right-click the server and then click Configure Server.

  4. Follow the instructions in the wizard.
  1. Install Windows Deployment Services. For more information, see the Windows Deployment Services Getting Started Guide.

  2. Click Start, right-click Command Prompt, click Run as administrator, and then run WDSUTIL /Verbose /Progress /Initialize-Server /RemInst:<path>, where <path> is the path where you would like the RemoteInstall folder to be located.

The preceding procedure does the following:

  1. Creates the folder tree for RemoteInstall.

  2. Creates the RemoteInstall folder with the following default permissions: Authenticated Users = Read and Execute, System = Full Control, Administrators = Full Control, and WDSServer service = Full Control

  3. Installs the server files (boot files) from the \system32\reminst folder (as placed during component installation) to the new folder structure.

  4. Updates the service parameters.

  5. Sets the Trivial File Transfer Protocol (TFTP) root to point to the RemoteInstall folder root.

  6. Sets the WDSServer service startup type to Auto.

  7. Optionally authorizes the server in Dynamic Host Control Protocol (DHCP).

  8. Starts the services.

To start or stop the server

Using the MMC Using WDSUTIL
  1. Right-click the server, and then click All Tasks.

  2. Click Stop Server or Start Server.
  1. Click Start, right-click Command Prompt, and click Run as administrator.

  2. Run WDSUTIL /Start-Server or WDSUTIL /Stop-Server.

The preceding procedure starts or stops the WDSServer service.

To enable the server

Using the MMC Using WDSUTIL

N/A
  1. Click Start, right-click Command Prompt, and click Run as administrator.

  2. Run WDSUTIL /Enable-Server.

The preceding procedure starts or stops the WDSServer service.

To enable logging for the Windows Deployment Services client

Using the MMC Using WDSUTIL

N/A
  1. Click Start, right-click Command Prompt, and click Run as administrator.

  2. To turn on client logging, run WDSUTIL /Set-Server /WDSClientLogging /Enabled:Yes.

  3. To change which events are logged, run WDSUTIL /Set-Server /WDSClientLogging /LoggingLevel:{None|Errors|Warnings|Info} (each category includes all events from the previous categories).

The preceding procedure sets HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WDSServer\Providers\WdsImgSrv\ClientLogging\Enabled to 1.

The level is stored at HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WDSServer\Providers\WdsImgSrv\ClientLogging\LogLevel, where 0 is None; 1 is Errors only; 2 is Errors and Warnings; and 3 is Errors, Warnings, and Information.

To choose the port number for RPCs

Using the MMC Using WDSUTIL

N/A
  1. Click Start, right-click Command Prompt, and click Run as administrator.

  2. Run WDSUTIL /Set-Server /RPCPort:X, where X is the RPC port number you want to use.

  3. You must restart the service before the changes will take effect. To do this, run wdsutil /stop-server and then run wdsutil /start-server.

The preceding procedure sets HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WDSServer\Parameters\RpcPort to the specified value.

Note

If this remote procedure call (RPC) port is changed from the default value, you must add a firewall exception for the new RPC port.

To specify the network interfaces for Windows Deployment Services to listen on

Using the MMC Using WDSUTIL

N/A
  1. Click Start, right-click Command Prompt, and click Run as administrator.

  2. Do one of the following:

    • To add an interface to the list, run WDSUTIL /Set-Server /BindPolicy /Add /Address:<IP or MAC address> /AddressType:{IP|MAC}.

    • To bind to only the interfaces on the list, run WDSUTIL /Set-Server /BindPolicy /Policy:Include.

    • To bind to all interfaces other than those on the list, run WDSUTIL /Set-Server /BindPolicy /Policy:Exclude.

The preceding procedure sets HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\WDSServer\Providers\WDSPXE\BindPolicy to 0 to exclude the list, and sets it to 1 to include the list (and excludes all other interfaces).

The list is stored in the following key: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\WDSServer\Providers\WDSPXE\BindInterfaces (addresses are stored as MAC=XXXXXXXXXXXX or IP=10.10.2.2)

To configure how often the server refreshes its settings

Using the MMC Using WDSUTIL

N/A
  1. Click Start, right-click Command Prompt, and click Run as administrator.

  2. Run WDSUTIL /Set-Server /RefreshPeriod:<time in seconds>.

The preceding procedure sets HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WDSServer\Parameters\UpdateTime to the specified value.

To force the server to update files in the RemoteInstall folder

Using the MMC Using WDSUTIL

N/A
  1. Click Start, right-click Command Prompt, and click Run as administrator.

  2. Run WDSUTIL /Update-ServerFiles.

To configure the network profile for the server

Using the MMC Using WDSUTIL
  1. Right-click the server, and then click Properties.

  2. On the Network Settings tab under Network Profile, select the option that specifies the network speed of your organization.
  1. Click Start, right-click Command Prompt, and click Run as administrator.

  2. Run WDSUTIL /Set-Server [/Server:<name>] /Transport /Profile:{10Mbps|100Mbps|1Gbps|Custom}.

Select Custom if you want to customize the settings yourself by editing the following registry key:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WDSServer\Providers\Multicast\Profiles\Custom

Important

You should not modify the other profiles that are provided. Instead, you should create a custom profile even if you want to change only one setting.

To back up the server data

To completely back up your server, you must back up the following two sets of data:

  • Images stored in the \RemoteInstall folder. To back up images, you must perform regular backups of the \RemoteInstall folder. You can restore the content from these backups without any special qualifications. The exception to this is if your server contains Remote Installation Services (RIS) images that have been groveled by Single Instance Storage (SIS). For more information about how to restore a volume that is managed by SIS, see article 263027 in the Microsoft Knowledge Base (http://go.microsoft.com/fwlink/?LinkId=81026).

  • Settings generally stored in the server’s registry. To back up these settings, we recommend that you perform regular backups by using the Microsoft Volume Shadow Copy Service (http://go.microsoft.com/fwlink/?LinkId=105509). As an alternative, you can regularly archive the server's configuration settings by running the command WDSUTIL /get-server /show:config. However, if you must restore the settings, you must manually reconfigure the settings by using WDSUTIL.

DHCP

To configure Windows Deployment Services to run on the same computer as Microsoft DHCP

Using the MMC Using WDSUTIL
  1. Right-click the server, and then click Properties.

  2. On the DHCP tab, select Do not listen on port 67 and Configure DHCP Option #60 Tag to PXEClient.
  1. Click Start, right-click Command Prompt, and click Run as administrator.

  2. Run WDSUTIL /Set-Server /UseDHCPPorts:No /DHCPOption60:Yes.

The preceding procedure does the following:

  • Sets HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WDSServer\Parameters\UseDhcpPorts to 0.

  • Adds the option 60 PXEClient tag to all of your DHCP scopes.

To configure Windows Deployment Services to run on the same computer as non-Microsoft DHCP

Using the MMC Using WDSUTIL
  1. Right-click the server, and then click Properties.

  2. On the DHCP tab, select Do not listen on port 67.

  3. Use your DHCP server tools to set the option 60 tag to PXEClient.
  1. Click Start, right-click Command Prompt, and click Run as administrator.

  2. Run WDSUTIL /Set-Server /UseDHCPPorts:No.

  3. Use your DHCP server tools to set the option 60 tag to PXEClient.

The preceding procedure sets HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WDSServer\Parameters\UseDhcpPorts to 0.

To turn on the DHCP authorization requirement

Using the MMC Using WDSUTIL

N/A
  1. Click Start, right-click Command Prompt, and click Run as administrator.

  2. Run WDSUTIL /Set-Server /RogueDetection:Yes.

The preceding procedure sets HKEY_LOCAL_MACHINE\System\CurrentControlSet\WDSServer\Providers\WDSPXE\DisableRogueDetection to 0.

To authorize the server in DHCP

Using the MMC Using WDSUTIL
  1. Ensure that you are a domain administrator in the root domain of the forest or an enterprise administrator. For information about delegating permissions, see “Authorizing a Server” in the Configuring DHCP topic.

  2. Right-click the server, and then click Properties.

  3. On the Advanced tab, select Authorize the Windows Deployment Server in DHCP.
  1. Ensure that you are a domain administrator in the root domain of the forest or an enterprise administrator. For information about delegating permissions, see “Authorizing a Server” in the Configuring DHCP topic.

  2. Click Start, right-click Command Prompt, and click Run as administrator.

  3. Run WDSUTIL /Set-Server /Authorize:Yes.

The preceding procedure creates an entry for DHCP authorization under the CN-NetServices, CN=Services, CN=Configuration, DC=Domain, DC=com object in AD DS.

Client Requests

To configure the server to answer clients

Using the MMC Using WDSUTIL
  1. Right-click the server, and then click Properties.

  2. On the PXE Response Settings tab, do one of the following:

    • To respond to all client PXE requests, select Respond to all (known and unknown) client computers.

    • To respond only to prestaged client PXE requests, select Respond only to the known client computers.

    • To not answer any client PXE requests, select Do not respond to any client computer. Note that this option will only work if Windows Deployment Services and DHCP are running on different servers. This is because although Windows Deployment Services will not respond, DHCP will. You can try to work around this issue by disabling DHCP Option 60 on the DHCP tab.
  1. Click Start, right-click Command Prompt, and click Run as administrator.

  2. Do one of the following:

    • To respond to all clients’ PXE requests, run WDSUTIL /Set-Server /AnswerClients:All.

    • To respond only to prestaged clients’ PXE requests, run WDSUTIL /Set-Server /AnswerClients:Known.

    • To not answer any clients’ PXE requests, run WDSUTIL /Set-Server /AnswerClients:None.

The preceding procedure does the following:

  • When the Respond to all (known and unknown) client computers check box is selected, the netbootAnswerRequests DS attribute is set to TRUE and the netbootAnswerOnlyValidClients DS attribute is set to FALSE.

  • When the Respond only to the known client computers check box is selected, both attributes are set to TRUE.

  • When the Do not respond to any client computer check box is selected, both attributes are set to FALSE.

To set a delay in the server’s answers to PXE requests

Using the MMC Using WDSUTIL
  1. Right-click the server, and then click Properties.

  2. On the PXE Response Settings tab, set the PXE Response delay in the control.
  1. Click Start, right-click Command Prompt, and click Run as administrator.

  2. Run WDSUTIL /Set-Server /ResponseDelay:X, where X is the amount of time (in seconds) you want the server to wait before responding to clients.

The preceding procedure sets the value of HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\WDSServer\Providers\WDSPXE\Providers\BINLSVC\ResponseDelay to the specified time.

To configure unknown clients to perform PXE boots without requiring F12

Using the MMC Using WDSUTIL

N/A
  1. Click Start, right-click Command Prompt, and click Run as administrator.

  2. Run WDSUTIL /Set-Server /AllowN12ForNewClients:Yes.

The preceding procedure sets the value of HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\WDSServer\Providers\WDSPXE\Providers\BINLSVC\AllowN12ForNewClients to 1.

To configure clients who have booted without F12 to require a key press on subsequent boots

Using the MMC Using WDSUTIL

N/A
  1. Click Start, right-click Command Prompt, and click Run as administrator.

  2. Run WDSUTIL /Set-Server /ResetBootProgram:Yes.

The preceding procedure sets the value of HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\WDSServer\Providers\WDSPXE\Providers\BINLSVC\ResetBootProgram to 1.

To configure the server to determine the architecture of booting clients

Using the MMC Using WDSUTIL

N/A
  1. Click Start, right-click Command Prompt, and click Run as administrator.

  2. Run WDSUTIL /Set-Server /ArchitectureDiscovery:Yes.

The preceding procedure sets the value of HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WDSServer\Providers\WDSPXE\Providers\BINLSVC\DisableArchDisc to 0.

Client Boot Settings

To choose which boot images are displayed on x64-based computers

Using the MMC Using WDSUTIL

N/A
  1. Click Start, right-click Command Prompt, and click Run as administrator.

  2. Run WDSUTIL /Set-Server /DefaultX86X64ImageType:<x86|x64|both>.

The preceding procedure sets HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WDSServer\Providers\WDSPXE\Providers\BINLSVC\x86x64DefaultImageType to 1 for x86-based computers only, 2 for x64-based computers only, and 0 for both types of computers.

To choose the default network boot program for each architecture

Using the MMC Using WDSUTIL
  1. Right-click the server, and then click Properties.

  2. On the Boot tab, insert the path to the boot file you want to use for each architecture. For a list of network boot programs, see Managing Network Boot Programs.
  1. Click Start, right-click Command Prompt, and click Run as administrator.

  2. Run WDSUTIL /Set-Server /BootProgram:<path> /Architecture:{x86|x64|ia64}, where <path> is relative to the RemoteInstall folder.

The preceding procedure sets HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WDSServer\Providers\WDSPXE\Providers\BINLSVC\BootPrograms\<arch>\Default to the specified path.

To choose the default network boot program that does not require F12 for each architecture

Using the MMC Using WDSUTIL

N/A
  1. Click Start, right-click Command Prompt, and click Run as administrator.

  2. Run WDSUTIL /Set-Server /N12BootProgram:<path> /Architecture:{x86|x64|ia64}, where <path> is relative to the RemoteInstall folder.

The preceding procedure sets HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WDSServer\Providers\WDSPXE\Providers\BINLSVC\BootPrograms\<arch>\N12 to the specified path.

To choose the default boot image for each architecture

Using the MMC Using WDSUTIL
  1. Right-click the server, and then click Properties.

  2. On the Boot tab, insert the path to the boot image you want to use for each architecture. In most cases, you should use the standard boot image that is included on the Windows Server 2008 media (located at \Sources\boot.wim) without modification. Do not use the Boot.wim from the Windows Vista media unless your version of Windows Vista has SP1 integrated into the DVD.
  1. Click Start, right-click Command Prompt, and click Run as administrator.

  2. Run WDSUTIL /Set-Server /BootImage:<path> /Architecture:{x86|x64|ia64}, where <path> is relative to the RemoteInstall folder.

The preceding procedure sets HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WDSServer\Providers\WDSPXE\Providers\BINLSVC\BootImages\<arch>\BootImagePath to the specified path.

Active Directory Domain Services

To specify a domain controller for Windows Deployment Services

Using the MMC Using WDSUTIL
  1. Right-click the server, and then click Properties.

  2. On the Advanced tab, click Let Windows Deployment Services use only the specified servers, and then enter the domain controller name.
  1. Click Start, right-click Command Prompt, and click Run as administrator.

  2. Run WDSUTIL /Set-Server /PreferredDC:<name>, where <name> is a NetBIOS name or fully qualified domain name (FQDN).

The preceding procedure sets HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WDSServer\Providers\WDSPXE\Providers\BINLSVC\DefaultServer to the specified name.

To specify a global catalog server for Windows Deployment Services

Using the MMC Using WDSUTIL
  1. Right-click the server, and then click Properties.

  2. On the Advanced tab, click Let Windows Deployment Services use only the specified servers and then enter the Domain controller name.
  1. Click Start, right-click Command Prompt, and click Run as administrator.

  2. Run WDSUTIL /Set-Server /PreferredGC:<name>, where <name> is a NetBIOS name or FQDN.

The preceding procedure sets HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WDSServer\Providers\WDSPXE\Providers\BINLSVC\DefaultGCServer to the specified name.

To choose whether to search for computer accounts in the domain controller before searching the global catalog

Using the MMC Using WDSUTIL

N/A
  1. Click Start, right-click Command Prompt, and click Run as administrator.

  2. Do one of the following:

    • To search in the domain controller before searching the Global Catalog server, run WDSUTIL /Set-Server /DomainSearchOrder:DCFirst

    • To search only in the Global Catalog server, run WDSUTIL /Set-Server /DomainSearchOrder:GCOnly

In the preceding procedure:

  • DCFirst sets HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WDSServer\Providers\WDSPXE\Providers\BINLSVC\ADSearchOrder to 1

  • GCOnly sets it to 0.

To configure the server to prestage clients by using their MAC address instead of their GUID

Using the MMC Using WDSUTIL

N/A
  1. Click Start, right-click Command Prompt, and click Run as administrator.

  2. Run WDSUTIL /Set-Server /PrestageUsingMAC:Yes.

The preceding procedure sets HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WDSServer\Providers\WDSPXE\Providers\BINLSVC\ClientIdUse to 1.

To maintain a list of GUIDs that belong to multiple computers

Using the MMC Using WDSUTIL

N/A
  1. Click Start, right-click Command Prompt, and click Run as administrator.

  2. Do one of the following:

    • To add a GUID to the list, run WDSUTIL /Set-Server /BannedGUIDPolicy /Add /GUID:<GUID>.

    • To remove a GUID from the list, run WDSUTIL /Set-Server /BannedGUIDPolicy /Remove /GUID:<GUID>.

      Note

      The GUID string should be specified without brackets or dashes (as seen during a PXE boot).

The list of banned GUIDs list will be stored at HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WDSServer\Providers\WDSPXE.

To specify how to generate computer names

Using the MMC Using WDSUTIL
  1. Right-click the server, and then click Properties.

  2. On the Directory Services tab, enter the naming policy string in the indicated field (see below for details).
  1. Click Start, right-click Command Prompt, and click Run as administrator.

  2. Run WDSUTIL /Set-Server /NewMachineNamingPolicy:<Policy> where <policy> is the naming policy string (see below for details).

The policy string works as follows:

  • %First: the first name of the user.

  • %Last: the last name of the user.

  • %Username: the user name of the user.

  • %MAC: the MAC address of the computer.

  • %n#: an incremental n-digit number. For example, %2# will add a number to the computer name in the following order: 1,2,3,…99.

  • %0n#: an incremental n-digit number, with zeros added before the digit. For example, %02# will add a number to the computer name in the following order: 01,02,03,…99.

These can be combined in any order. A number before a tag string (such as %3First or %5Username) will crop the string to that length. For example:

  • %61Username%# equals JohnSmi12

  • %2first.%last equals Jo.Smith

The preceding procedure sets the netbootNewMachineNamingPolicy DS attribute to the specified policy.

To specify the domain and OU in which to create computer accounts

Using the MMC Using WDSUTIL
  1. Right-click the server, and then click Properties.

  2. On the Directory Services tab, click Default Directory Service location or specify the domain and organizational unit (OU)
  1. Click Start, right-click Command Prompt, and click Run as administrator.

  2. Do one of the following:

    • To create new accounts in the default computer OU in the domain the Windows Deployment Services server is in, run WDSUTIL /Set-Server /NewMachineOU /Type:ServerDomain.

    • To create new accounts in the default computer OU in the domain the specified user account is in, run WDSUTIL /Set-Server /NewMachineOU /Type:UserDomain.

    • To create new accounts in the same OU as the specified user account, run WDSUTIL /Set-Server /NewMachineOU /Type:UserOU.

    • To create new accounts in a different OU, run WDSUTIL /Set-Server /NewMachineOU /Type:Custom /OU:<name of OU>.

The preceding procedure does the following:

  • Sets the netbootNewMachineOU attribute on the Service Control Point (SCP) for the Windows Deployment Services server to the distinguished name of the server

  • Sets the NewMachineOUType registry key to 1

  • Sets the NewMachineOUType registry key to 0

  • Sets the netbootNewMachineOU attribute on the SCP for the Windows Deployment Services server to the specified distinguished name

To choose whether to join client computers to the domain

Using the MMC Using WDSUTIL
  1. Right-click the server, and then click Properties.

  2. On the Client tab, clear the Do not create account in Active Directory after running the WDS Client check box to join computers to the domain.
  1. Click Start, right-click Command Prompt, and click Run as administrator.

  2. To join new computers to the domain, run WDSUTIL /Set-Server /NewMachineDomainJoin:Yes.

The preceding procedure sets HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WDSServer\Providers\WDSPXE\Providers\BINLSVC\NewMachineDomainJoin to 1.

Unattend File

To choose a default unattend file for the Windows Deployment Services client

Using the MMC Using WDSUTIL
  1. Right-click the server, and then click Properties.

  2. On the Client tab, select the Enable client unattend check box and then choose an unattend file for the relevant architecture.
  1. Click Start, right-click Command Prompt, and click Run as administrator.

  2. To turn on unattended installation and specify the unattend file, run WDSUTIL /Set-Server /WDSUnattend /Policy:Enabled /File:<path> /Architecture:{x86|x64|ia64}.

The preceding procedure sets HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WDSServer\Providers\WdsImgSrv\Unattend\Enabled to 1 and HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WDSServer\Providers\WdsImgSrv\Unattend\<arch>\FilePath to the specified path.

To specify whether an unattend file on the client computer will override a default unattend file

Using the MMC Using WDSUTIL

N/A
  1. Click Start, right-click Command Prompt, and click Run as administrator.

  2. Do one of the following:

    • To allow an unattend file on the client computer to override the unattend file sent from the server for the Windows Deployment Services client, run WDSUTIL /Set-Server /WDSUnattend /CommandLinePrecedence:Yes.

    • To force the unattend file sent from the server to be used for the Windows Deployment Services client, run WDSUTIL /Set-server /WDSUnattend /CommandLinePrecedence:No.

The preceding procedure sets HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WDSServer\Providers\WdsImgSrv\Unattend\CommandLineUnattendPrecedence to 1 or 0.