- This topic is empty.
-
Posts
-
Hi,
We have between 150 and 200 Wyse X90M7 laptops that we have used Wyse USB firmware tool. (We also have about 100 s10/c10LE that uses ftp)
I have now installed WDM 4.9 and have problems with pulling and pushing images. The reason I choosed to download 4.9 instead of 4.9.1 is because the release notes said that you needed newer hagent than was installed on the X90M7. Is this a problem or could I have installed 4.9.1 and upgraded the hagent afterwords?
We have several offices on different /24 subnets but all subnets can communicate and there are no firewalls between.
Because there are many subnets and routers I would love to be able to Push and pull images using http and not pxe.
But when I try to push the image (non-pxe) the computer reboots and:
Gets an error that it can’t find eth 0.
then it says eth0 is UP and Running
Then it changes to
“Determine IP address via DHCP on interface eth0 …
MAC
usage: sys get …and a bunch of get set commands.
“Then I have to manually enter the client ip, subnet mask, default gatway and wdm server name or ip. choose http and port 80
(This should not be needed, should it?)
Then it tries to
“Starting DHCP option tag search”
“No Domain name set”
“No ethernet device not found”Trying again…
Then the screen goes black and in red letters this error occures:
“[Repository_validation_stage][socket_error_or_could_not_connect_to_wdm_server[Authentication_failed]:Exc=100”
And the boots up normally.
The eth0 works with no problems when you are logged in to windows.
Do you have any clue on what is wrong? There seem to be some problems with the eth0 but I have never had any problems with eth0 before and it works in Windows.
The DHCP server has been set up with option 186 and 192.
Tried to be as detailed as needed but if you would like more details please don’t hesitate to ask and I will try to take som pictures of the different messages and link up.
Thanks in advance.
Øistein
I have been digging some more since we got some new x90m7 today.
I am able to pull image of the new machine. I have also no problem with pushing the original image(I just pulled) to the new machines. But as soon as i push one of our “old” images with the companies configuration on to the x90m7 this works but then I am not able to push more images to it.
So it seems to be some problems with the old images. I checked the package script i WDM and sees that the new image uses merlin 2.6.1 but the image we have done configuration on is using merlin version 2.5.0.
Could this be the issue?
If this is the problem, is there a possibility to upgrade Merlin in the old image? Either from the physical Wyse X90M7 or run a upgrade on merlin from the WDM? Or is the only solution to build up a new image from start from one of my new Wyse laptops?
Inside of WDM – Package Manager – Images you will find latest Bott Agents (Merlin). Use those to update.
CG
Hey, I am experiencing the same issue. I was able to push out my custom image to 12 brand new terminals successfully, 2 weeks ago. BUT when I attempted to push out the same image last week to 2 brand new terminals from the same shipment of the first 12. I got the same problem you have. It asked for the Client IP, Subnet, WDM Server IP etc… and even though I entered in the correct info…. It would error out and reboot to the original OS partition…
**** I worked with a WYSE Technician for 3 hours on Friday to resolve this issue but came up no answers/results.
What was the solution for you? What was causing the issue?
I am able to push out the default boot agent & WES7HAgent with no issues but when I push my OWN custom image I get the same error, please update.
Thanks!
Are you using DHCP option tags and/or DNS alias to point to your WDM server?
CG
ConfGen,
Yes I have all of that setup, I did it with the Wyse Tech. But I did not have it originally when I first pushed out my image to the 12 terminals successfully.
Do you have any other suggestions?
Thanks!
Excuse my lack of knowledge on this subject. But how do I insure it is really working etc..???
Again thank you for you help!
Hi,
I have exactly the same issue with WDM 4.9.1 when I try to push the last build downloaded from Wyse website.
The Merlin agent available in WDM “bootagentupgradeWES7” is in version 2.6.1 and the one on the Z90 device is 2.2.4.
I’ve tried to push the new agent but nothing happens.
Do you think that the best solution is to deploy the last build through USB key, configure the device then pull the image in WDM to deploy the rest of devices ?
Thanks for help
- You must be logged in to reply to this topic.