- This topic has 12 replies, 5 voices, and was last updated 4 years, 7 months ago by
.
-
Posts
-
Hi,
We recently spun up a new WMS 1.4 server to replace our WDM server since our newest 5070 W10 clients do not seem to work well with WDM, and since it is no longer being updated, it was time to move on to the latest and greatest.
Anyway, the issue we are having is that we are able to register 5070 W10 clients, send updates and software to them and pretty much manage them fine. The problem we are having is that any attempt to push or pull an image from any of the clients will fail. The client will boot into Merlin but will never get an IP address from our DHCP server. It will then error out of Merlin with a code 105 Cant find the repository.
We did not have this issue with WDM. I have added the WMS flags to our DHCP. WDM is also currently still running in the environment on an older 08R2 server if that has any bearing.
Thanks!
*Edit* Forgot to mention that I have installed the newest firmware, newest WDA and newest Merlin packages.
What’s the Merlin version you are using? I have 5070 W10 clients, I can test this out. I have been able to create images previously and just upgraded to 1.4 so maybe I can replicate.
Are you sure the client isn’t getting an IP address? When I have had problems with Merlin connecting in the past, it wasn’t from not getting an IP, it was because it was unable to resolve the name of the WMS server. By default, when you install WMS it introduces itself to clients using its Windows hostname and not its FQDN. When you’re in a Windows environment, this might be OK but Merlin won’t know what to do with it if the DNS suffix of the server doesn’t match the default suffix the client gets from the DHCP server.
The 5070s are running the Merlin Boot Agent Version 3.7.7 A00.
In Merlin when looking at its DHCP routine during boot up it attempts to get an IP address. It always shows the following messages up to the error:
Copying system system.conf
/etc/merlinpartition/merlinPartitionData.sh: line 327: chown: not found
/etc/merlinpartition/merlinPartitionData.sh: line 327: chown: not found
/etc/merlinpartition/merlinPartitionData.sh: line 327: chown: not found
dos2unix: converting file /tmp/system.conf to Unix format
ifconfig: SIOCGIFFLAGS: No such device
udhcpc (v1.20.2) Started
Setting IP address 0.0.0.0 on eth0
Sending discover…
Sending discover…
Sending discover…
Sending discover…
Sending discover…
No lease, failing
ifconfig: SIOCGIFFLAGS: No such device
ifconfig: SIOCGIFFLAGS: No such device
ifconfig: SIOCGIFFLAGS: No such device
ifconfig: SIOCGIFFLAGS: No such device
ifconfig: SIOCGIFFLAGS: No such device
ifconfig: eth2: error fetching interface information: Device not found
MAC
ifconfig: eth2: error fetching interface information: Device not found
ifconfig: eth2: error fetching interface information: Device not found
cat: /etc/resolv.conf: No such file or directory
cat: /etc/resolv.conf: No such file or directory
route: fscanf
Merlin Version Number 3.7.7
====================IMAGING FAILED=================
ERROR : WMS File Repository Server not found. (error code: 105)
ERROR STAGE : Repository validation
REASON : Could not connect to repository server
SOLUTION : Check the network connection/authentication
=================================================
You know what? This does sound familiar, now…
I think my experience with the first 5070 I got was that it ships with an image that is missing the partition with the necessary stuff to make Merlin work! We image all our clients by USB so I think I had to download a new image from DELL and load it via USB to make the image we used for all the other 5070s. Can’t believe DELL hasn’t cleaned that up, yet!
I just checked and the image on the 5070 is the most current March release. I am completely stumped with this. Seriously, Dell took something that worked great, WDM, and replaced it with this broken software that is far less user friendly.
OK I went back through my emails and I can see that this problem is different than what I had with the missing Merlin partition last year, sorry for sending you in the wrong direction.
I haven’t used WDM so I can speak for how it works but I don’t think this is an issue with WMS. I am pushing an image to a 5070 right now and I did not have the same problems you are experiencing. It seems exactly like you say, you’re not getting a DHCP address for your ethernet connection. My log looks like your up until the first “Sending discover…” line, then I get an IP assigned and everything flows.
Are you sure your network connection is good?
So I got it working.
It was definitely the thin client. Ended up blowing it away, and reinstalling the newest base image again. Connected it to WMS, upgraded the WDA and Merlin to the newest again, and now it will connect to the DHCP and pull the image properly. I wish I could say what it was that fixed it, but apparently the Merlin agent was corrupt and no matter what I did would not see the DHCP server.
Thanks everyone for the input.
We’re getting the same error when trying to apply ThinLinux OS updates to our WYSE 5070s. Our WMS file repository is operation as we can push other updates, i.e. VMware Horizon successfully.
NOTE: We tried to push ThinLinux 2.0, 2.1, and 2.2, no luck. We are using Dell’s USB Imaging Tool for the interim but now have 300 thin clients.
Has anyone discovered a fix for this? Dell Support isn’t helpful.
Have you updated all agents?
What base image are you running at the moment?CG
Spent all morning today with Dell Support. We upgraded the agent version to 3.4.6-05 and the platform utility to 2.4.6-05 using WMS and WMS File Repository. No issues, the updates applied successfully. However, receiving the same Error 105 when trying to push the ThinLinux 2.2.0.1 merlin image. The merlin version number is 4.0.2 if that matters.
Any ideas? Dell has escalated to L3.
Can someone tell me what is the process you guys take to prepar to pull an image. I know that I should be running sysprep for Windows 1o IoT, but when I push the image when the device boots up I’m asked to select the language, time zone, and keyboard layout. Later I’m asked to create a local account to get thru the intial setup. The admin and user accounts that come with the device originally image shipped by Dell is still there which is fine for me. But I think to go thru the initial process to set up every device and then to delete the account that I created is a lot of extra work. All I need is to have the admin and user account and configure auto login to the user account. I am not joining the device to the domain.
High-level description of how I prepare an image:
1. Download latest base image from DELL. Use the USB tool to put it on a stick and image a client.
2. Install/Uninstall/Configure all the crap I need in the image.
3. Strip out whatever I can to make the image as small as possible.
4. Turn on the write filter so WDA fires up and connects to WMS.
5. Schedule an image pull for the client. When this kicks off, it will turn off UWF and reboot the client. Log in as Admin
6. Open C:\Program Files\Wyse\WDA\Config\CCMProtocolConfig.xml and strip out the MAC Address, Owner ID, Wyse ID, Authentication Code and Group Key.
7. Run (as administrator) C:\Windows\Setup\BuildMaster.cmd. Pick your image preferences and let it do it’s thing. When it’s done, it will shut off. Turn it back on and it will upload the image to the WMS repository.
- You must be logged in to reply to this topic.