I have setup the computer backups successfully and I have verified that the workstations are creating the client backups. The issue I have now is trying to setup the Client Restore Service. Initially, it said I was missing the ADK which was expected since it was a fresh install so I used the link and it downloaded the ADK for Windows 8.1.

Now when I try to setup the Client Restore Service in the wizard, after I click on Start it updates the status to "Customizing WinPE images..." and after 5 minutes, I get the following error:

Client Restore Service installation did not succeed.

Cannot customize the client restore image.

The specified image file did not contain a resource section.

-----

If I click on Start to begin the process again, and I browse to the C:\Windows\Temp folder, I can see the two mounted folders for the customizing process:

C:\Windows\Temp:

GenBmrWinPETempPath: 8096c353-79cb-4d74-ae8d-3c287fdb735c : which remains empty and removes after failure.

GenBmrWinPEMountPath: c32700c9-7391-4caf-9a7e-af420e96d327 : mounted WIM with directory structure but removes after failure when it unmounts.

During the process, I also see the boot.wim in the following folder, "C:\ProgramData\Microsoft\Windows Server\Data\ClientRestore\8.100.25984_8.100.25984_6.3.9600.16384\0409\sources", with a filesize of 172,644KB.

the GenBmrState.xml file contains the following information:

<?xml version="1.0" encoding="utf-8"?><GenBmrJobExecutionInfo xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><Status>Idle</Status><LastStage>CustomizeWinPE</LastStage><OemImagesExist>false</OemImagesExist><AdkReady>true</AdkReady><ImageReady>false</ImageReady><MediaReady>false</MediaReady><WdsImageDeployed>false</WdsImageDeployed><Results><GenBmrJobResultPair><Key>Wds</Key><Value><Failed>true</Failed><Reason>CustomizeImageFailed</Reason><AdditionalErrorCode>0</AdditionalErrorCode><AdditionalErrorMessage>The specified image file did not contain a resource section.
</AdditionalErrorMessage></Value></GenBmrJobResultPair></Results></GenBmrJobExecutionInfo>

Does anyone know how to fix the "The specified image file did not contain a resource section" error?

Hi,

Based on your description, I also set up Client Restore Service on a Windows Server 2012 R2 Essentials in my Lab environment. However, I cant reproduce this problem. The Client Restore Service seems to be set up as normal.

Please refer to following article and check if can help you.

Essentials 2012 R2 Client Restore

In addition, would you please let me confirm more details?

1. Is it Windows Server 2012 R2 Essentials or Windows Server 2012 R2 Standard (or Datacenter) with the Windows Server Essentials Experience role installed? Just a confirmation, thanks for your understanding.
2. If non-production environment, would you please restart the server? Then check if this issue still exists.
3. Please check if WinPE-Setup.cab exists. Follow the path: C:\Program Files(x86)\Windows Kits\8.1\Assessment and Deployment Kit\Windows Preinstallation Environment\Amd64\WinPE_OCs
4. Please navigate to C:\Programdata\Windows Server\Logs. Then check SharedServiceHost-ManagementServiceConfig log file if find relevant errors.

If any update, please feel free to let me know.

Hope this helps.

Best regards,

Justin Gu

Hi, I actually ran into the same issue with Essentials.

In my case the answers to your questions are:

1)  R2 Essentials

2)  Reboot did not fix it.

3)  File does exist (file size: 8,223 KB, date 8/22/2013

4)  Log entry shows an error with that specific cab file:

[7976] 140704.171211.7708: GenBmr: Applying "C:\Program Files (x86)\Windows Kits\8.1\Assessment and Deployment Kit\Windows Preinstallation Environment\Amd64\WinPE_OCs\WinPE-Setup.cab".
[7976] 140704.171215.0862: GenBmr: Customize WinPE failed: System.Management.Automation.CmdletInvocationException: The specified image file did not contain a resource section.
 ---> System.Runtime.InteropServices.COMException: The specified image file did not contain a resource section.

   at System.Management.Automation.MshCommandRuntime.ThrowTerminatingError(ErrorRecord errorRecord)
   --- End of inner exception stack trace ---
   at System.Management.Automation.Runspaces.PipelineBase.Invoke(IEnumerable input)
   at Microsoft.WindowsServerSolutions.PowerShell.PSRuntime.ExecuteCommandPrivate(String command, PSParameterList parameterList)
   at Microsoft.WindowsServerSolutions.PowerShell.PSRuntime.ExecuteCommand(String command, PSParameterList parameterList)
   at Microsoft.WindowsServerSolutions.DataProtection.PCBackup.BackupUtil.GenBmr.Tasks.CustomizeWinPETask.ApplyCabsInternal(IEnumerable`1 cabsToApply, FilePathSubstituter substituter, String mountPath, PSRuntime psRunTime, Boolean multiLang)
   at Microsoft.WindowsServerSolutions.DataProtection.PCBackup.BackupUtil.GenBmr.Tasks.CustomizeWinPETask.ApplyCabs(String mountPath, ImageKind imageKind, IEnumerable`1 serverLanguages)
   at Microsoft.WindowsServerSolutions.DataProtection.PCBackup.BackupUtil.GenBmr.Tasks.CustomizeWinPETask.CustomizeImage(ImageKind imageKind)

Thank you for your reply! Hopefully answering your questions will provide further input! I did look over the article you linked but that is the same procedure I followed except I receive the error after the ADK is installed and I click on the Start button which says it is "Customizing WinPE Images..."

1. This is a Windows Server 2012 R2 Essentials installation from the Essentials media. It is not a role added to another edition of Windows Server 2012 R2.

2. Yes, I have rebooted many times and the problem still persists.

3. Yes, the WinPE-Setup.cab file does exist!

4. I am copying an excerpt from the log that pretains to the error!

Log:

[13336] 140705.213958.2249: GenBmr: Copying "C:\Windows\system32\en-US\dmdskres.dll.mui" to "C:\Windows\TEMP\c32700c9-7391-4caf-9a7e-af420e96d327\Windows\System32\en-US\dmdskres.dll.mui".
[13336] 140705.213958.2249: GenBmr: Copying "C:\Windows\system32\en-US\dmdskres2.dll.mui" to "C:\Windows\TEMP\c32700c9-7391-4caf-9a7e-af420e96d327\Windows\System32\en-US\dmdskres2.dll.mui".
[13336] 140705.213958.2249: GenBmr: Copying "C:\Windows\system32\en-US\dmocx.dll.mui" to "C:\Windows\TEMP\c32700c9-7391-4caf-9a7e-af420e96d327\Windows\System32\en-US\dmocx.dll.mui".
[13336] 140705.213958.2249: GenBmr: Copying "C:\Windows\system32\en-US\dmutil.dll.mui" to "C:\Windows\TEMP\c32700c9-7391-4caf-9a7e-af420e96d327\Windows\System32\en-US\mmc.dll.mui".
[13336] 140705.213958.2249: GenBmr: Copying "C:\Windows\system32\en-US\dmutil.dll.mui" to "C:\Windows\TEMP\c32700c9-7391-4caf-9a7e-af420e96d327\Windows\System32\en-US\mmc.dll.mui".
[13336] 140705.213958.2249: GenBmr: Copying "C:\Windows\en-US\hh.exe.mui" to "C:\Windows\TEMP\c32700c9-7391-4caf-9a7e-af420e96d327\Windows\System32\en-US\hh.exe.mui".
[13336] 140705.213958.2249: GenBmr: Copying "C:\Windows\system32\en-US\iepeers.dll.mui" to "C:\Windows\TEMP\c32700c9-7391-4caf-9a7e-af420e96d327\Windows\System32\en-US\iepeers.dll.mui".
[13336] 140705.213958.2249: GenBmr: Copying "C:\Windows\system32\en-US\dwwin.exe.mui" to "C:\Windows\TEMP\c32700c9-7391-4caf-9a7e-af420e96d327\Windows\System32\en-US\dwwin.exe.mui".
[13336] 140705.213958.2249: GenBmr: Copying "C:\Windows\system32\en-US\diskmgmt.msc" to "C:\Windows\TEMP\c32700c9-7391-4caf-9a7e-af420e96d327\Windows\System32\en-US\diskmgmt.msc".
[13336] 140705.213958.2405: GenBmr: Copying "C:\Program Files\Windows Server\Bin\ClientRestore\en-US\RestoreWizardResources.dll.mui" to "C:\Windows\TEMP\c32700c9-7391-4caf-9a7e-af420e96d327\Windows\System32\en-US\RestoreWizardResources.dll.mui".
[13336] 140705.213958.2405: GenBmr: Copying "C:\Program Files\Windows Server\Bin\ClientRestore\en-US\WSSDriverSetupResources.dll.mui" to "C:\Windows\TEMP\c32700c9-7391-4caf-9a7e-af420e96d327\Windows\System32\en-US\WSSDriverSetupResources.dll.mui".
[13336] 140705.213958.2405: GenBmr: Applying cabs.
[13336] 140705.213958.3499: GenBmr: Applying "C:\Program Files (x86)\Windows Kits\8.1\Assessment and Deployment Kit\Windows Preinstallation Environment\Amd64\WinPE_OCs\WinPE-Setup.cab".
[13336] 140705.213959.9281: GenBmr: Customize WinPE failed: System.Management.Automation.CmdletInvocationException: The specified image file did not contain a resource section.
 ---> System.Runtime.InteropServices.COMException: The specified image file did not contain a resource section.

   at System.Management.Automation.MshCommandRuntime.ThrowTerminatingError(ErrorRecord errorRecord)
   --- End of inner exception stack trace ---
   at System.Management.Automation.Runspaces.PipelineBase.Invoke(IEnumerable input)
   at Microsoft.WindowsServerSolutions.PowerShell.PSRuntime.ExecuteCommandPrivate(String command, PSParameterList parameterList)
   at Microsoft.WindowsServerSolutions.PowerShell.PSRuntime.ExecuteCommand(String command, PSParameterList parameterList)
   at Microsoft.WindowsServerSolutions.DataProtection.PCBackup.BackupUtil.GenBmr.Tasks.CustomizeWinPETask.ApplyCabsInternal(IEnumerable`1 cabsToApply, FilePathSubstituter substituter, String mountPath, PSRuntime psRunTime, Boolean multiLang)
   at Microsoft.WindowsServerSolutions.DataProtection.PCBackup.BackupUtil.GenBmr.Tasks.CustomizeWinPETask.ApplyCabs(String mountPath, ImageKind imageKind, IEnumerable`1 serverLanguages)
   at Microsoft.WindowsServerSolutions.DataProtection.PCBackup.BackupUtil.GenBmr.Tasks.CustomizeWinPETask.CustomizeImage(ImageKind imageKind)
[13336] 140705.213959.9281: Task: In Task CustomizeWinPE: 


[13336] 140705.213959.9281: TaskManagement: In TaskScheduler.ReportStatus(): Task("CustomizeWinPE") requested the engine stop processing Tasks!  Completed=True, Success=False


[13336] 140705.213959.9281: GenBmr: Unmounting the image discarding changes.

I have the exact same issue...did you get this resolved?  If so could you share your fix.

Unfortunately this hasn't been resolved for me yet! I have tried uninstalling and reinstalling the ADK to see if it makes a difference but it doesn't! The same error appears on the screen and in the log files! Hopefully someone else knows how to fix it! It sure would be nice to see all green checks on that fancy dashboard!

Are you guys pre 2919355 or post 2919355 as there's a different ADK that needs to be downloaded.

This was a new install and 2919355 was installed as part of the update process.  Could you let me know what ADK I should install?

I installed the Windows 2012 R2 Essentials in Mid June 2014 so I would say it is post 2919355 since I immediately applied all available patches from Windows Update as soon as the server was online. After everything was updated via WU, I started going through the dashboard options for Essentials server which instructed me to install the ADK via a specific link during the Client Restore Services setup process. It was the ADK for Windows 8.1. I'll try to get the specifics when I have physical access to my server later tonight. Is there a specific update to the Windows 8.1 ADK that needs to be applied, and if so, would you have a link to it? The 8.1 ADK was taken directly from the link that the setup wizard provided.

Updated Information:

The ADK version is: 8.100.26629

I did find the update KB2919355 installed as an update under Programs and Features.

• Edited by TaintedScar Thursday, July 10, 2014 3:02 AM Added the ADK version

I installed the Windows 2012 R2 Essentials in Mid June 2014 so I would say it is post 2919355 since I immediately applied all available patches from Windows Update as soon as the server was online. After everything was updated via WU, I started going through the dashboard options for Essentials server which instructed me to install the ADK via a specific link during the Client Restore Services setup process. It was the ADK for Windows 8.1. I'll try to get the specifics when I have physical access to my server later tonight. Is there a specific update to the Windows 8.1 ADK that needs to be applied, and if so, would you have a link to it? The 8.1 ADK was taken directly from the link that the setup wizard provided.

Updated Information:

The ADK version is: 8.100.26629

I did find the update KB2919355 installed as an update under Programs and Features.

• Edited by TaintedScar Thursday, July 10, 2014 3:02 AM Added the ADK version

Hi Justin,

There is another thread on this issue that someone posted a few files from their working environment but the language pack was not English.  Any chance you could grab these files in English and post them?

The poster was Wei

http://social.technet.microsoft.com/Forums/windowsserver/en-US/dd9cec0c-7b42-440d-9d19-4861d123ca27/unable-to-restart-client-restore-service-after-updating-windows-adk-for-81-update?forum=winserveressentials

Sorry, some steps were missing. They should be:

1. Download boot.wim and boot_x86.wim from https://onedrive.live.com/redir?resid=9D8E090A257F6E0B!4364&authkey=!AEunbMVWjgqxsIQ&ithint=folder%2c

2. Place boot.wim and boot_x86.wim under C:\ProgramData\Microsoft\Windows Server\Data\ClientRestore\8.100.25984_8.100.25984_6.3.9600.16384\040C\sources

3. Download GenBmrState.xml and GenBmrState.xml.bak from https://onedrive.live.com/redir?resid=9D8E090A257F6E0B!4364&authkey=!AEunbMVWjgqxsIQ&ithint=folder%2c

4. Replace GenBmrState.xml and GenBmrState.xml.bak under C:\ProgramData\Microsoft\Windows Server\Data\ClientRestore with the downloaded ones.

5. Restart the WseMgmtSvc service and Dashboard

6. Restart the Client Restore Service

<input id="cf0ef438-3030-4844-b823-707166140798_attachments" type="hidden" value="" />                

• Edited by                             Wei Ran<abbr class="affil">Microsoft employee</abbr>                         Tuesday, May 06, 2014 4:17 AM

• Edited by drummer1 Thursday, July 10, 2014 7:48 PM

Hi Justin,

There is another thread on this issue that someone posted a few files from their working environment but the language pack was not English.  Any chance you could grab these files in English and post them?

The poster was Wei

http://social.technet.microsoft.com/Forums/windowsserver/en-US/dd9cec0c-7b42-440d-9d19-4861d123ca27/unable-to-restart-client-restore-service-after-updating-windows-adk-for-81-update?forum=winserveressentials

Sorry, some steps were missing. They should be:

1. Download boot.wim and boot_x86.wim from https://onedrive.live.com/redir?resid=9D8E090A257F6E0B!4364&authkey=!AEunbMVWjgqxsIQ&ithint=folder%2c

2. Place boot.wim and boot_x86.wim under C:\ProgramData\Microsoft\Windows Server\Data\ClientRestore\8.100.25984_8.100.25984_6.3.9600.16384\040C\sources

3. Download GenBmrState.xml and GenBmrState.xml.bak from https://onedrive.live.com/redir?resid=9D8E090A257F6E0B!4364&authkey=!AEunbMVWjgqxsIQ&ithint=folder%2c

4. Replace GenBmrState.xml and GenBmrState.xml.bak under C:\ProgramData\Microsoft\Windows Server\Data\ClientRestore with the downloaded ones.

5. Restart the WseMgmtSvc service and Dashboard

6. Restart the Client Restore Service

<input id="cf0ef438-3030-4844-b823-707166140798_attachments" type="hidden" value="" />                

• Edited by                             Wei Ran<abbr class="affil">Microsoft employee</abbr>                         Tuesday, May 06, 2014 4:17 AM

• Edited by drummer1 Thursday, July 10, 2014 7:48 PM

Good catch drummer1! I found that article in the past and the files were in another language so I didn't pursue it any further. We would probably need the copies of his files before the Client Restore Services modifies them during the setup/configuration process and puts them in the %APPDATA%\......\ClientRestore directory. Maybe running a checksum against his ADK installation directory and ours may show something is different?

• Edited by TaintedScar Thursday, July 10, 2014 8:56 PM Fixed question

Good catch drummer1! I found that article in the past and the files were in another language so I didn't pursue it any further. We would probably need the copies of his files before the Client Restore Services modifies them during the setup/configuration process and puts them in the %APPDATA%\......\ClientRestore directory. Maybe running a checksum against his ADK installation directory and ours may show something is different?

• Edited by TaintedScar Thursday, July 10, 2014 8:56 PM Fixed question

Hi drummer1,

 Have you had any luck with this? I'm still stuck!

Hi,

No luck... doesn't look like anyone is jumping in with any help.

I fixed the problem on my server.

I installed 2012 R2 on another machine and turned off automatic updates.  I installed the 8.1 Update ADK and started Client Restore Services.  Once Client restore services started (green check) I copied all the contents from the C:\ProgramData\Microsoft\Windows Server\Data\ClientRestore folder to a USB stick.

On the effected server I uninstalled the previous ADK kit and installed the 8.1 Update.  I deleted the contents from the ClientRestore folder and added the them back from the USB copy.  I restarted the Server and Started the Client Restore Service.  All green checks now.

• Proposed as answer by drummer1 Sunday, July 20, 2014 4:22 PM
• Edited by drummer1 Monday, July 21, 2014 12:49 AM
• Marked as answer by TaintedScar Tuesday, July 22, 2014 5:04 AM

I fixed the problem on my server.

I installed 2012 R2 on another machine and turned off automatic updates.  I installed the 8.1 Update ADK and started Client Restore Services.  Once Client restore services started (green check) I copied all the contents from the C:\ProgramData\Microsoft\Windows Server\Data\ClientRestore folder to a USB stick.

On the effected server I uninstalled the previous ADK kit and installed the 8.1 Update.  I deleted the contents from the ClientRestore folder and added the them back from the USB copy.  I restarted the Server and Started the Client Restore Service.  All green checks now.

• Proposed as answer by drummer1 Sunday, July 20, 2014 4:22 PM
• Edited by drummer1 Monday, July 21, 2014 12:49 AM
• Marked as answer by TaintedScar Tuesday, July 22, 2014 5:04 AM

Okay, so I tried to do what you recommended.

1. Installed a fresh 2012 R2 Essentials server and turned off automatic updates and went directly to the "Set up Client Restore Service" option.

2. After it installed successfully, I copied the entire C:\ProgramData\Microsoft\Windows Server\Data\ClientRestore folder to the desktop of the server that is having the issue.

3. On the "bad" server, I uninstalled the ADK, rebooted, and clicked on the "Set up Client Restore Service" dashboard option, and it gave me the link to download the ADK, just like I did on the temporary server. I deleted the original ClientRestore folder that was empty and copied the folder that was successfully completed on the temporary server. I restarted the server and clicked on "Set up Client Restore Service" and it threw the same error:

[13304] 140721.194029.4181: GenBmr: Copying "C:\Program Files\Windows Server\Bin\ClientRestore\en-US\RestoreWizardResources.dll.mui" to "C:\Windows\TEMP\c32700c9-7391-4caf-9a7e-af420e96d327\Windows\System32\en-US\RestoreWizardResources.dll.mui".
[13304] 140721.194029.4181: GenBmr: Copying "C:\Program Files\Windows Server\Bin\ClientRestore\en-US\WSSDriverSetupResources.dll.mui" to "C:\Windows\TEMP\c32700c9-7391-4caf-9a7e-af420e96d327\Windows\System32\en-US\WSSDriverSetupResources.dll.mui".
[13304] 140721.194029.4181: GenBmr: Applying cabs.
[13304] 140721.194029.5431: GenBmr: Applying "C:\Program Files (x86)\Windows Kits\8.1\Assessment and Deployment Kit\Windows Preinstallation Environment\Amd64\WinPE_OCs\WinPE-Setup.cab".
[13304] 140721.194030.7618: GenBmr: Customize WinPE failed: System.Management.Automation.CmdletInvocationException: The specified image file did not contain a resource section.
 ---> System.Runtime.InteropServices.COMException: The specified image file did not contain a resource section.

   at System.Management.Automation.MshCommandRuntime.ThrowTerminatingError(ErrorRecord errorRecord)
   --- End of inner exception stack trace ---
   at System.Management.Automation.Runspaces.PipelineBase.Invoke(IEnumerable input)
   at Microsoft.WindowsServerSolutions.PowerShell.PSRuntime.ExecuteCommandPrivate(String command, PSParameterList parameterList)
   at Microsoft.WindowsServerSolutions.PowerShell.PSRuntime.ExecuteCommand(String command, PSParameterList parameterList)
   at Microsoft.WindowsServerSolutions.DataProtection.PCBackup.BackupUtil.GenBmr.Tasks.CustomizeWinPETask.ApplyCabsInternal(IEnumerable`1 cabsToApply, FilePathSubstituter substituter, String mountPath, PSRuntime psRunTime, Boolean multiLang)
   at Microsoft.WindowsServerSolutions.DataProtection.PCBackup.BackupUtil.GenBmr.Tasks.CustomizeWinPETask.ApplyCabs(String mountPath, ImageKind imageKind, IEnumerable`1 serverLanguages)
   at Microsoft.WindowsServerSolutions.DataProtection.PCBackup.BackupUtil.GenBmr.Tasks.CustomizeWinPETask.CustomizeImage(ImageKind imageKind)
[13304] 140721.194030.7618: Task: In Task CustomizeWinPE: 


[13304] 140721.194030.7618: TaskManagement: In TaskScheduler.ReportStatus(): Task("CustomizeWinPE") requested the engine stop processing Tasks!  Completed=True, Success=False


[13304] 140721.194030.7618: GenBmr: Unmounting the image discarding changes.
[12564] 140721.194049.2775: Backup: Client backup folder property DriveFreeSpace changed 
[13304] 140721.194057.8087: Task: In Task CustomizeWinPE: 


[13304] 140721.194057.8087: TaskManagement: In TaskScheduler.ReportStatus(): Task("CustomizeWinPE") requested the engine stop processing Tasks!  Completed=True, Success=False


[13304] 140721.194057.8087: Task: Task ("CustomizeWinPE") execution complete.
[13304] 140721.194057.8087: TaskManagement: Previous Task required us to stop processing Tasks for a restart, failure, or cancel.
[13304] 140721.194057.8087: GenBmr: Job completed.

dummer1, Thanks for the suggestion but it looks like I'm still unlucky!

So I gave it another go with the installation and successful set up on another server and then copied the files over to the server that just wouldn't set up the Client Restore Service.

Instead of restarting the server this time, I replaced the C:\ProgramData\Microsoft\Windows Server\Data\ClientRestore folder with the good copy and then I went to Services and restarted the "Windows Server Essentials Management Service". After that, I launched the Essentials dashboard and clicked on Set up Client Restore Service and it had a green check. so I clicked on restart and told it to re-setup the service and it went through without any issues!

Hopefully this "hodge podge" method will work when I actually need to use the restore feature! I mounted the boot.wim and saw that it has some files dated from the temporary server install so hopefully that will not render the service useless from my other server!

• Marked as answer by TaintedScar Tuesday, July 22, 2014 5:04 AM

So I gave it another go with the installation and successful set up on another server and then copied the files over to the server that just wouldn't set up the Client Restore Service.

Instead of restarting the server this time, I replaced the C:\ProgramData\Microsoft\Windows Server\Data\ClientRestore folder with the good copy and then I went to Services and restarted the "Windows Server Essentials Management Service". After that, I launched the Essentials dashboard and clicked on Set up Client Restore Service and it had a green check. so I clicked on restart and told it to re-setup the service and it went through without any issues!

Hopefully this "hodge podge" method will work when I actually need to use the restore feature! I mounted the boot.wim and saw that it has some files dated from the temporary server install so hopefully that will not render the service useless from my other server!

• Marked as answer by TaintedScar Tuesday, July 22, 2014 5:04 AM

Glad it worked for you.  I tested Bare Metal restore on a few Clients and everything work as it should.

I am having the same issue. But also now I appear to be stuck with the French version, due to fact that I following this post without really reading it in detail;

http://social.technet.microsoft.com/Forums/windowsserver/en-US/dd9cec0c-7b42-440d-9d19-4861d123ca27/unable-to-restart-client-restore-service-after-updating-windows-adk-for-81-update?forum=winserveressentials

Next I tried drummer1 solution and it works to a degree - but the client still comes up in French. How do I correct that?

I am having the same issue. But also now I appear to be stuck with the French version, due to fact that I following this post without really reading it in detail;

http://social.technet.microsoft.com/Forums/windowsserver/en-US/dd9cec0c-7b42-440d-9d19-4861d123ca27/unable-to-restart-client-restore-service-after-updating-windows-adk-for-81-update?forum=winserveressentials

Next I tried drummer1 solution and it works to a degree - but the client still comes up in French. How do I correct that?

I can't guarantee this will fix it but maybe consider the following:

Do you have the ability to perform another installation inside of a Virtual Machine or physical hardware? If so, you can install the OS, don't let it update, and immediately install the ADK. After that, go through the setup process for the Client Restore function. After it finishes, copy the "C:\ProgramData\Microsoft\Windows Server\Data\ClientRestore" folder to a USB key and then replace the files on your server that has the French version of the files. You may be good at this point but if not, go to Services and restart the "Windows Server Essentials Management" Service. After that, launch the Essentials dashboard and click on Set up Client Restore Service and it should have a green check. If it does, restart the server and then re-setup the Client Restore Service.

• Edited by TaintedScar Saturday, August 09, 2014 2:00 AM grammer correction

I am having the same issue. But also now I appear to be stuck with the French version, due to fact that I following this post without really reading it in detail;

http://social.technet.microsoft.com/Forums/windowsserver/en-US/dd9cec0c-7b42-440d-9d19-4861d123ca27/unable-to-restart-client-restore-service-after-updating-windows-adk-for-81-update?forum=winserveressentials

Next I tried drummer1 solution and it works to a degree - but the client still comes up in French. How do I correct that?

I can't guarantee this will fix it but maybe consider the following:

Do you have the ability to perform another installation inside of a Virtual Machine or physical hardware? If so, you can install the OS, don't let it update, and immediately install the ADK. After that, go through the setup process for the Client Restore function. After it finishes, copy the "C:\ProgramData\Microsoft\Windows Server\Data\ClientRestore" folder to a USB key and then replace the files on your server that has the French version of the files. You may be good at this point but if not, go to Services and restart the "Windows Server Essentials Management" Service. After that, launch the Essentials dashboard and click on Set up Client Restore Service and it should have a green check. If it does, restart the server and then re-setup the Client Restore Service.

• Edited by TaintedScar Saturday, August 09, 2014 2:00 AM grammer correction

I am having the same issue. But also now I appear to be stuck with the French version, due to fact that I following this post without really reading it in detail;

http://social.technet.microsoft.com/Forums/windowsserver/en-US/dd9cec0c-7b42-440d-9d19-4861d123ca27/unable-to-restart-client-restore-service-after-updating-windows-adk-for-81-update?forum=winserveressentials

Next I tried drummer1 solution and it works to a degree - but the client still comes up in French. How do I correct that?

I can't guarantee this will fix it but maybe consider the following:

Do you have the ability to perform another installation inside of a Virtual Machine or physical hardware? If so, you can install the OS, don't let it update, and immediately install the ADK. After that, go through the setup process for the Client Restore function. After it finishes, copy the "C:\ProgramData\Microsoft\Windows Server\Data\ClientRestore" folder to a USB key and then replace the files on your server that has the French version of the files. You may be good at this point but if not, go to Services and restart the "Windows Server Essentials Management" Service. After that, launch the Essentials dashboard and click on Set up Client Restore Service and it should have a green check. If it does, restart the server and then re-setup the Client Restore Service.

Actually I figured it out. I am also using WDS for new installs, I just needed to go in and delete the "Full System Restore" for x86 and x64 from the Boot Images folder in the WDS MMC. Then restart the Client Restore Service and let it recreate them. I am now able to start doing my bare metal restores.

I don't have the ability to create another server and am getting the same error, any other pointers on how to resolve this?

R       Rename the ClientRestore folder ClientRestore.old

C:\ProgramData\Microsoft\Windows Server\Data\ClientRestore

Then click start in the dashboard for the client restore service.  If you already have the adk installed, it will properly recreate the ClientRestore "stuff".  If you do not have the ADK installed, it will start from there giving you the link to get it, and then do it's thing.

Also note (future readers <grin>) if you have the restore service up and running, there is no need to "update" the ADK (AFAIK) but if you really want to you can.

Copied from Grey

Thanks Susan, unfortunately I tried that with the same issue.  Using a spare disk I did create a fresh installation and successfully created the ClientRestore folder (and a bootable restore key) and copied that over the one on the original server however that still did not allow the Client Restore Service to start with the same error as I saw previously.  Interesting when I created the fresh ClientRestore folder inside it is a folder with a long string of numbers and inside that is another folder called 0409, the  original server was trying to create one called "0409-0809" not sure if that is because I'm using the US version of Essentials with English (UK) language and that's why it's getting confused.  I did try changing the language but that didn't resolve the issue.

It does seem fairly obvious that one of the updates is causing the Client Restore issue.

However at least I do have a USB restore key now even if the service to create it isn't working on the server.

ferrrar1s,

Can you tell me how you got to where it was when it was broke? the 409 stuff is language.  You said it worked on the fresh install but not yours? Were they both the same language setup?  It never worked on the "main" server, or you had it working and then updated the adk?

If you still feel like messing with it, could you uninstall the adk and rename the client restore folder and give it another go?

Thanks for your help in troubleshooting this.

Grey

Hi Grey,

This is what I did : I installed the adk then went into the dashboard and clicked start under the Client Restore Service tab.  It then says "Customising WinPE Images" for about 20 seconds before changing to 

"Client Restore Service installation did not succeed.

Cannot customize the client restore image
The specified image file did not contain a resource section."

I'm pretty sure they were both the same language set-up, the version of Essentials I have is EN-US as the setup screen only allows me to choose English US at the language but lets me choose a UK date/currency and keyboard.

It has never worked on the main server.  As reported in the other thread when I came to start the restore service first time it said WinPE could not be found so I downloaded that.  Initially it reported winhelp.dll.mui was missing from system32\en-GB but I found that in EN-US and copied it over and renaming the old Client Restore folder so a new one was created as you suggested did not help either as I still get the resource section missing error.

I uninstalled the adk and tried to start the service again (having removed the previous Clientresotre folder) but still get the error message above about the resource section.

Thanks.

Let me try it.  So the install that never worked was English with a uk keyboard?  And did your originally try this before April of this year as in with the 8.1 standard adk or was every attempt "recently"

But if I had to guess Robert has done installs with the uk keyboard..

Both installs are of the English US version (I don't have any other language options) but with UK date/time and keyboard (these are the 3 dropdowns you get at the beginning of the install process if I remember correctly).

This is is recent ie. in the past week.

I suspect Robert may have used the UK language version with UK keyboard which is different to what I have.

Simon

Sorry to be so dense, but in order to try to duplicate, I need to duplicate LOL

So both installs were recent and both were US with UK on the other 2 dropdowns.  The one that worked had no updates applied and the only diff with the one that failed was no updates were applied?

So the one that failed is actually 2012R2 dot 1 or with the "update" and the one that failed is 2012R2 without the update?

I am not sure how you got the diff file structure on the 2 installs  the 409 vs the 409-809

Both installs were with an iso that includes the update however the one that worked was without subsequent Windows Update updates!

S

Thanks, I'm trying :)  Installing updates now.  Will do the adk soon, but it takes forever to download.  See what happens tomorrow

Hip Hip Hooray !!  I got it to fail LOL..

I did an install selecting UK in the 2nd and 3rd drop down applied all updates  (2012R2 Essentials with update iso)  Started client restore service. Said ADK was not installed and gave me the link.  IE enhanced mode off, download, next, next.  Start again and it configured the client restore process properly in 409.

Went to languages and installed the UK language update offered and also installed the us keyboard.  Started the restore service again, said yes when it said it was running.  This time it created the 409-809 folder and failed.  The 64$ question now is can I fix it ?

Well done, good to hear!

At this point i copied the missing file from the en-us folder to get me past this problem. 

S

yes, and then it said wow64 same file.  So 2 drag and drops and it is working for me  I never got the error mentioned in the other French thread though.  So I suppose you can try downloading my 409-809 and the 2 xml files if you want

https://www.dropbox.com/sh/z0jp8wui4sxhz89/AACvXOuq7laBo544DkmpYanra?dl=0

Thanks, I don't recall the wow64 error but I copied your files over and it works.

Appreciate your help.

Yea !! :)

Thanks - that worked for me (using files downloaded from Grey).

Pete. do you have a Thecus unit and or could you tell us how you think it went wrong?

PS:  Glad it works now :)

If it is a brand new Thecus you probably need to download the updated image from Thecus.  Many of the first units shipped with a buggy build.  Client restore was one and the other was the product will not activate.

I saw a similar issue on my brand new Thecus W4000+ unit. I get an error that I am missing "system32\ar-SA\apphelp.dll.mui." Copying it from the "en-US" folder fixed the issue and lets the service start. I have everything configured for the default US-english (as far as I know).