Start a Conversation

Unsolved

This post is more than 5 years old

P

6889

April 28th, 2019 11:00

problem pulling image from wyse 5070

I am trying to pull image from wyse 5070 with WMS, 1.3.. It has freshly installed Windows (Windows 10 IoT Enterprise Redstone 1 Unified Build 10.03.06.03.19.00 for Wyse 5070 thin client.) I can see pull request in client, but after restart it boot up to windows without booting up to merlin and sending image to WMS, then after windows load, it again show pull request and restart.. same procedure worked for WMS 1.3 and wyse 5020, but it doesn't work with 5070, does it require some other components? I am using: WDA_14.3.0.66_Unified.exe and boot agent 3.7.7 ,A00 Any sugestions?

Moderator

 • 

9.2K Posts

May 7th, 2019 11:00

Hi,

Does it show any errors in the logs? Page 156 https://topics-cdn.dell.com/pdf/wyse-wms_administrator-guide15_en-us.pdf

1 Rookie

 • 

5 Posts

May 7th, 2019 13:00

Hello

no errors,

it act like there is no Merlin, - it doesn't kick in after restart, and goes straight to windows (wms shows Merlin 377 on device) 

bcdedit /enum firmware doesn't list merlin

is there a way to add it manually in a proper and safe way? 

installation of Merlin always finish with success -run exe file locally or deply via WMS

Thank you in advance

Moderator

 • 

9.2K Posts

May 7th, 2019 14:00

Is the bios up to date?  Have you tried pushing the OS image again? I don’t see a way to manually add it to the boot menu.

1 Rookie

 • 

5 Posts

May 7th, 2019 21:00

bios was updated to latest version 

then imaged via usb tool to  Windows 10 IoT Enterprise Redstone 1 Unified Build 10.03.06.03.19.00 for Wyse 5070 thin client.

tried to pull image but it failed due to merlin not kick in after reboot,

so updated Merlin ..and WDA to latest version - still pulling doesn't work to WMS- while it work for any other wyse model

only problem i can see is with missing bcdedit entry.. (WMS detect proper version of Merlin and WDA, applying settings and all other functions works correct,, just pulling / pushing image has problem

maybe it is bug in windows release or bios?

not sure if it matter but i am using 64 gb ssd with pentium cpu wyse 5070 

any further suggestions?

1 Rookie

 • 

5 Posts

May 7th, 2019 21:00

also just in case did factory reset bios settings, and only changed allow to boot from usb to enable

Moderator

 • 

9.2K Posts

May 8th, 2019 09:00

Your best option probably to call into warranty support.

1 Rookie

 • 

56 Posts

September 4th, 2019 07:00

Based on the observations listed, it appears that the Boot Agent's partition is either missing from the boot order or has been erased from the SSD. I would recommend downloading the latest OS System image (http://downloads.dell.com/published/pages/wyse-5070-thin-client.html) for your client and the USB Imaging tool (http://downloads.dell.com/wyse/USBFT/). 

  1. Install the USB Imaging Tool on a Windows PC
  2. Configure a USB to push a copy of the OS Image
  3. Open BIOS Settings (F2, Default Password: Fireport) on the Thin Client. Set Secure Boot to Disabled and enable USB Boot Support. These items may be worded differently depending on the client. Plug in the configured USB Drive then save the BIOS settings to reboot. 
  4. Open the Boot Menu (F12) and select the USB device
  5. When the Merlin Boot Agent (from USB) loads, select to push the image to the client. Click Next on the following screen to start. This process will take some time to complete. When finished reboot the device to verify that the thin client is able to boot into the OS.
  6. For security, it is recommended to return to the BIOS Settings and re-enable Secure Boot and disable USB Boot Support.

This process will reset the client and restore all partitions (including Merlin and EFI). If this does not work or you are not able to perform this steps, it is recommended to contact support about initiating a RMA.

No Events found!

Top