March 20, 2017 at 5:14 pm #44059
Hopefully someone can offer some insight.
We have 6x D90D7’s currently on the bench for testing. I have installed WDM 5.7, everything running fine. All repo’s up and green.
Started out discovering the devices, that went smoothly. Then, due to my lack of knowledge i attempted to push out a configuration i had created in Configuration Manager and managed to upload to WDM, however that failed.
Did some research and found that i needed to update the Boot Agent, HAgent and WCM Agent. Boot and HAgent updated with no problems. Tried to register WCM Agent 188.8.131.52 using PkgRegister.exe but that failed. Registered ok using the wizard on locally installed WDM and was showing up in Other Packages.
Attempted to push that out and file was copied to the ThinClient (C:\Temp) but nothing else happened, i had to run the app manually. Afterwards WCM was up to version 184.108.40.206.
Tried to push out the configuration i had created, again, with no success.
Found an updated WES7 image from the dell site, BDB0_0895_16GB.exe.
Tried registering this using Web UI and the local Device Manager console and while they show that the process completed, nothing ever appears in either Web or local app. I can see the folder gets created in C:\inetpub\ftproot\rapport\ but nothing ever appears in there, so there is nothing to push out.
I have also tried extracting that file is it comes in the form of a 7zip executable, but running this on Server 2012 errors, stating incorrect OS.
The clients are obviously connecting to the WDM server otherwise the initial updates of HAgent and BootAgent wouldn’t have gone through.
What am i missing? Documentation is extremely scarce and the standard guides do not deviate from a perfect scenario.
I’m sure there is a lot of detail i have neglected to include, but please ask, i’ll be happy to provide it.
Thanks in advanceMarch 22, 2017 at 5:04 pm #44070
Is it WDM 5.7 or 5.7.1 you are running?
CGMarch 23, 2017 at 1:41 pm #44091
I’ll download and install 5.7.1 now. Once done i’ll push out any updated agents and try again.
Will report back asap.March 23, 2017 at 5:25 pm #44097
That doesn’t seem to have fixed the issue. Still getting the same error appearing in the logs after attempting to register the latest WES7 image using PkgRegister.exe.
03-23-2017 16:01:24 --->BDB0_0895_16GB.exe.part_7308.7309 size=1420267 (Chunk=7308/7309) - (File=1/1) 03-23-2017 16:01:24 [+]THE-RESPONSE|OK 03-23-2017 16:01:24 --->BDB0_0895_16GB.exe.part_7309.7309 size=279519 (Chunk=7309/7309) - (File=1/1) 03-23-2017 16:01:39 RspUploadChunkUsingStream-Last chunk had an unknown exception. Let it go (2). A task was canceled. (-2146233029) 03-23-2017 16:01:39 ~*~ RspUploadChunkUsingStream-Last chunk was handled in a special manner. 03-23-2017 16:01:39 Sending chunks are all done. 03-23-2017 16:01:39 Done processing: C:\Wyse Stuff\WES7 Image\BDB0_0895_16GB.exe 03-23-2017 16:01:39 No issues or errors found. 03-23-2017 16:01:39 WaitEstimate for Total Chunk count 7309
Having run a search for the file name (BDB0_0895_16GB.exe) i found one in C:\inetpub\wwwroot\HApi\App_Data\5F0B73DD22532F7ABC5136DCE860539376C2633D_BDB0_0895_16GB
Also, following updating to 5.7.1, even though i’m logged in as Administrator, when i try to open up the devices list on the WebUI it throws me out, apparently i don’t have the permission to view that page. I can view devices on the local application.
Any ideas on whats causing the problem with the Package Registration?
I’ll reboot following the update, and try again. I’ll also check to see if i then have permissions to view the Devices page on the WebUI.
Report back shortly.March 23, 2017 at 6:06 pm #44099
Rebooting didnt resolve the issue of not having permissions to view the device page…
I treid registering the WES7 package through the local app and it came up with an error about not being able to write to the HTTP server, cant remember exactly what it said.
If you need the exact error let me know and i’ll run it again.
ThanksMarch 24, 2017 at 9:57 am #44105
Sounds like WebDav is not running correctly.
CGMarch 24, 2017 at 12:05 pm #44108
Your input is always appreciated. Any ideas on how to fix that? To be honest that isnt the main issue i’m having….
With me getting the HTTP write error when registering the latest WES7 image i decided to disable the HTTP repo. After attempting to register the package again through the local app it succeeded. Bonus.
However, i have since tried to push the image out and while the file is copied to the thin client i’m still getting an error, see below:
Try 1:CreateProcess Failed:193 Line#: 12 Cmd:EX C:\Temp\BDB0 0895 16GB.exe +
Looks as though it’s having trouble executing the installation.
Any ideas on this?
ThanksMarch 24, 2017 at 1:07 pm #44110
Quick update, managed to get access to the Devices page on the WebUI by using localhost instead of the server name in the URL.
Trying to push the latest WES7 image again as i type.
If it doesn’t execute automatically i’ll try running it manually and see what happens.
Will report back.March 28, 2017 at 1:08 pm #44121
Sorry for the delayed update.
I have attempted to install the image by running the executable from the Temp folder however it errors stating it’s not a valid win32 application.
I’m at a loss with this now.
I’m going to try updating using the USB method, just to see if it works. I’d rather not have to do it manually for each device though.
Any input on pushing updated images out through WDM would be greatly apprciated.
Many thanksMarch 28, 2017 at 2:12 pm #44122
OK…. think i figured it out, and for anyone else having trouble with this, although it doesn’t seem like there is…
All you need to do is download and install 7Zip, then extract the image files using the 7Zip application, not the self extracting executable.
From there go ahead and register the package using the rsp file, then push out the update.
Pretty simple really. Only found the solution because i went back to the Wyse downloads page and there has been some text added at the top in red.
Hopefully this helps someone.
Thanks for your assistance CG!March 28, 2017 at 10:53 pm #44132
Hahaha, sounds like a RTFM error 🙂
- You must be logged in to reply to this topic.