1

This is WSE 2016 with the Client Restore Service enabled.

We're getting persistent errors in our single DC's event log:

enter image description here

I found this related documentation:

https://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/cc726671(v=ws.10)

It provides some guidance, but it stops short of explaining what to do if the command output does NOT contain entries for each of our boot images.

We have this for two of our architectures:

C:\>bcdedit.exe /store C:\RemoteInstall\Boot\x64uefi\default.bcd /enum

Windows Boot Manager
--------------------
identifier              {bootmgr}
path                    \Boot\x64\bootmgfw.efi
fontpath                \boot\fonts
inherit                 {dbgsettings}
bootems                 Yes
timeout                 30

C:\>bcdedit.exe /store C:\RemoteInstall\Boot\x86uefi\default.bcd /enum

Windows Boot Manager
--------------------
identifier              {bootmgr}
path                    \Boot\x86\bootmgfw.efi
fontpath                \boot\fonts
inherit                 {dbgsettings}
bootems                 Yes
timeout                 30

But this for the other two:

C:\>bcdedit.exe /store C:\RemoteInstall\Boot\x64\default.bcd /enum

Windows Boot Manager
--------------------
identifier              {bootmgr}
fontpath                \boot\fonts
inherit                 {dbgsettings}
timeout                 30

C:\>bcdedit.exe /store C:\RemoteInstall\Boot\x86\default.bcd /enum

Windows Boot Manager
--------------------
identifier              {bootmgr}
fontpath                \boot\fonts
inherit                 {dbgsettings}
timeout                 30

As we can see, the second set contains no boot image entries. I believe this to be the source of our errors, but I'm not sure how to proceed.

What should I do to create these entries?

InteXX
  • 795

2 Answers2

1

It sounds like what you need to do is to recreate your RemoteInstall folder. This will regenerate the boot files and the required directories while providing a working default configuration.

How to rebuild the RemoteInstall folder:

You can rebuild the RemoteInstall folder by doing the following:

  1. Remove WDS role from the server.

Remove the WDS role Removed

  1. Remove the folder share on your current RemoteInstall folder.

Remove file share

If you do not unshare the folder, you will get the following error:

File share already exists

So, don't forget to remove the folder share before you configure the server!

  1. Rename (incase you need some of the images files still) or remove the folder.

Rename folder

  1. Install the WDS role back to the server.

Install WDS server role

Role installed

  1. Configure the server.

After the server configuration has completed you will have a new RemoteInstall folder. Here is the output of a server 2016 RemoteInstall folder right after the configuration of the WDS role on the Server.

Folder layout

Tl;Dr:

  • Remove the WDS role
  • Unshare the current RemoteInstall share.
  • Install WDS role back to server.
  • Configure the server.
  • Profit!

Links:

Elliot Huffman
  • 1,249
0

After the some time error fix itself in my case. Maybe need to wait two days the problem will repair itself

allstartoki
  • 1