Unsolved
This post is more than 5 years old
1 Rookie
•
10 Posts
0
4005
June 3rd, 2019 07:00
WDM to WMS Issue
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 never had 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!
DELL-Josh Cr
Moderator
•
9.3K Posts
0
June 5th, 2019 13:00
Hi,
Is Merlin and the firmware up to date?
mafischl
1 Rookie
•
56 Posts
0
June 6th, 2019 07:00
Are you currently using a wired or wireless connection? In many cases, Merlin has difficulty obtaining a IP address from a DHCP server running on a wireless connection and I recommend trying it on a wired connection. As mentioned in another reply, confirm you are using the latest release of the Merlin Boot Agent (was updated with the release of WMS 1.4).
mafischl
1 Rookie
•
56 Posts
0
June 6th, 2019 08:00
If possible, can you post the issues that you experienced with the Wyse 5070 - Windows 10 IoT clients and WDM 5.7.3 on the Wyse Device Manager board. There are a few of us running this setup and may be able to help.
swervie
1 Rookie
•
10 Posts
0
June 6th, 2019 12:00
Merlin and firmware are both up to date. the connection is over a wired network.
swervie
1 Rookie
•
10 Posts
0
June 6th, 2019 12:00
mafischl,
We don't have 5.7.3. We run the free license version that apparently only goes to 5.7.2.
thanks
DELL-Scott H
Moderator
•
892 Posts
0
June 7th, 2019 07:00
The device not getting an IP from DHCP in Merlin could be a variety of factors
1) Spanning tree. I have seen this happen where the device is connected to a switchport that does not have spanning tree disabled, spanning tree on a port sometimes takes 45-60 seconds to bring the port online and Merlin boots too fast and cannot get an IP. Try connecting the thin client to an older hub/switch that you know has spanning tree disabled.
2) DHCP server quarantine. Your DHCP server may have some form of NAC that is blocking Merlin from getting an IP. Try either connecting the thin client to an isolated network that gets DHCP from a different DHCP server, or statically assign the IP. The current versions of Merlin should honor static assignments.
swervie
1 Rookie
•
10 Posts
0
June 7th, 2019 09:00
Wouldn't these issues be present in WDM as well? My Win 7 thin clients are able to connect to our existing WDM server and I can push and pull images from them. This issue currently is only with WMS.
I attempted to pull an image on one of the 5070 clients after setting the IP static in Windows and had the same failure.
swervie
1 Rookie
•
10 Posts
0
June 13th, 2019 06:00
So I got it working.
It was the thin client I was using for testing. 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.