Share via

Event ID 260 — TFTP Initialization

  • Article

Applies To: Windows Server 2008 R2

When the WDSServer service is started, the Trivial File Transfer Protocol (TFTP) server reads the configuration settings in the registry that apply to the TFTP server. Note that the TFTP server will not function correctly until it has initialized successfully.

Event Details

Product: Windows Operating System
ID: 260
Source: WDSTFTP
Version: 6.1
Symbolic Name: W_WDSTFTP_USING_REMINST_ROOT
Message: Windows Deployment TFTP server root folder is not configured. Using REMINST share as the root folder.

Resolve

Ensure that the permissions and registry settings are correct

You use the Trivial File Transfer Protocol (TFTP) server for Windows Deployment Services to download the files that are needed to do a network boot using the Pre-Boot Execution Environment (PXE). If the registry data is corrupt or the TFTP server does not have sufficient permissions, the TFTP server will not be able to download these files. To resolve this issue, do the following in the specified order:

  • Ensure that the registry data is correct.
  • Ensure that the registry permissions are correct. 

To perform these procedures, you must either be a member of the local Administrators group or have been delegated the appropriate authority.

Ensure that the registry data is correct

Caution: Incorrectly editing the registry might severely damage your system. Before making changes to the registry, you should back up any valued data.

To ensure that the registry data is not corrupt:  

  1. Open Registry Editor. (Click Start, type regedit in the Start Search box, and then press ENTER.)
  2. Ensure that the WDSTFTP registry key exists at the following location: HKLM\SYSTEM\CurrentControlSet\Services\WDSServer\Providers\WDSTFTP.
  3. If the WDSTFTP registry key is missing or corrupt, you will need to reinitialize the server. To do this, open the Command Prompt window and then run the wdsutil /uninitialize-server command. Next run wdsutil /initialize-server /reminst:<path>, where <path> is the path where you want the RemoteInstall folder to be located.

If the WDSTFTP registry key does not exist, use the procedure in the following section to ensure that the registry permissions are correct.

Ensure that the registry permissions are correct

To ensure that the TFTP server has the correct registry permissions and settings:

  1. Open Registry Editor.
  2. Right-click the HKLM\SYSTEM\CurrentControlSet\Services\WDSServer node, and then click Permissions.
  3. Click SYSTEM, and then make sure that Full Control is selected.
  4. Ensure that the RootFolder setting for the HKLM\SYSTEM\CurrentControlSet\Services\WDSServer\Providers\WDSTFTP registry key exists and that it is set to the correct path. For the Deployment Server, this should be set to the RemoteInstall folder (by default, the RemoteInstall folder is located on drive C). For the Transport Server, this should be set to the folder that contains the files you want to download over TFTP.
  5. Make sure that this folder exists (for example, RemoteInstall).
  6. Make sure that the SYSTEM account has the necessary permissions to read to this folder. To do this, right-click the folder name and then click Permissions. On the Security tab, click SYSTEM, and then make sure that Read is selected. 
  7. Restart the WDSServer service.

Verify

To verify that the TFTP server is working correctly:

  1. Open Event Viewer. (Click Start, type Event Viewer in the Start Search box, and then press ENTER.)
  2. In the left pane, expand Custom Views, expand Server Roles, and then click Windows Deployment Services.
  3. Click the Date and Time column heading to sort the events based on the date and time.
  4. Make sure that you received WDSTFTP event 256.
  5. Make sure that you received this event after any other WDSTFTP errors.

TFTP Initialization

Windows Deployment Services