Update WinCE WDM Server via RSP

Viewing 9 posts - 1 through 9 (of 9 total)
  • Author
    Posts
  • February 15, 2016 at 9:35 am #42459
    elproducto
    Participant
    • Total Post: 94
    • Back Stage Pass
    • ★★★★

    I made the following RSP and registry key to update WDM server address on Win CE devices. Script is currently not working for all my devices. I tested on two device that are the same model. Tested good on one device, but next device reboots after deployment but continues to report into old server. I currently need to move a few inherited WinCE devices from old WDM server to new. I am new to CE devices, so I slapped this script together from what I noticed in past post to this forum and WDM manual. Did I miss something in my syntax?

    RSP File

    
[Version]
Number=A_WDMUPD
Description=Migrate WINCE 6.0 Clients
OS=CE6
Category=Device Configuration
[Script]
CO "CE6"
QU "2" "5"
LU
MR "\reg\WDMUPD.reg"
EL
RB

    Registry File

    
[HKEY_LOCAL_MACHINE\SOFTWARE\RAPPORT\HAGENT]
"ServerIP"="192.168.1.11"

[HKEY_LOCAL_MACHINE\SOFTWARE\WYSE\Dhcp\DhcpOptsData]
"wbt3FileServer"="192.168.1.11"
    February 15, 2016 at 12:26 pm #42461
    ConfGen
    Keymaster
    • Total Post: 10696
    • Jedi Master
    • ★★★★★★★

    Are both units running on the same firmware? Same WDM Agent version (HAgent)?

    CG

    February 15, 2016 at 6:28 pm #42463
    elproducto
    Participant
    • Total Post: 94
    • Back Stage Pass
    • ★★★★

    Yeah both units are running the same firmware and HAgent.

    UNIT A (New Console) – Platform – V30LE, HAgent Version 4.7.12.1, Firmware 666.0
    UNIT B (Old Console) – Platform – V30LE, HAgent Version – 4.7.12.1, Firmware 666.0

    February 15, 2016 at 7:32 pm #42464
    elproducto
    Participant
    • Total Post: 94
    • Back Stage Pass
    • ★★★★

    I think I may have found what is different. Subnets are different, and device seem to be on a subnet with Option Tags, I need to confirm with my coworker, who is not available until later. I have tested remapping the option tags in the registry and this did the trick so get device to talk to new console. Seems in this case option tags trump control panel setting. I have extra registry key in case, but probably not needed.

    Updated Reg File
    [HKEY_LOCAL_MACHINE\SOFTWARE\RAPPORT\HAGENT]
    “ServerPort”=dword:0
    “ServerIP”=”192.168.1.11”
    “UInterval”=dword:3C
    “DHCPLegacyPortTag”=”187”
    “sysLocation”=””
    “sysContact”=””
    “Location”=”\windows”
    “ImageNumber”=”674-eb7a786c”
    “CAValidation”=dword:0
    “FirmwareUpgradeTimeOut”=dword:60
    “DHCPPortTagHTTPs”=”207”
    “DHCPPortTag”=”207”
    “DHCPServerTag”=”207”
    “HServerResponseTimeout”=dword:258
    “HServerV99Timeout”=dword:2
    “NetConnRetryAttempts”=dword:C
    “NetConnRetryInterval”=dword:5
    “SpinCount”=dword:28
    “ServerPortHTTPs”=dword:1BB

    [HKEY_LOCAL_MACHINE\SOFTWARE\WYSE\Dhcp\DhcpOptsData]
    “wbt3FileServer”=”192.168.1.11”

    February 16, 2016 at 2:33 am #42465
    elproducto
    Participant
    • Total Post: 94
    • Back Stage Pass
    • ★★★★

    Quick Update: It seems WDM 5.5.1 does works well with Win CE devices. Packages deployed to these device via WDM 5.5.1 stay in the Scheduled Packages section of WDM and never get delivered to CE device in scope. Also real time command do not work well. Back to the drawing board or WDM 5.0.

    February 16, 2016 at 9:09 am #42467
    ConfGen
    Keymaster
    • Total Post: 10696
    • Jedi Master
    • ★★★★★★★

    The latest HAgent version for CE is 4.8.16
    Pretty sure that the client cannot communicate with WDM 5.5.1 is due to WDM using https per default and the older HAgents are not capable of doing that.
    Can you try to manually upgrade one client with latest HAgent via FTP?

    CG

    February 17, 2016 at 5:40 am #42471
    elproducto
    Participant
    • Total Post: 94
    • Back Stage Pass
    • ★★★★

    That is weird about 5.5.1, these devices seem to work fine to WDM 5.0. I also forced devices to stick to port 80 but I am still unable to push packages to the device from 5.5.1.

    On the HAgent Not sure if I did this right, but manual Hagent and firmware upgrade was unsuccessful. I receive the error message “The new hardware image is not valid for this terminal Hardware code:17060101”

    For Hagent I downloaded the latest Hagent for WinCE 6.0. Made a folder under another folder of the root of my FTP server, placed two files within folder params.ini and the WyHagentaddon.bin. I then remote into station in scope and enter FTP IP and folder to find Hagent Add-on. Error appears after a few prompts.

    For Firmware upgrade I placed three files on the root of the ftp server
    bootstrap212.exe, params.ini, & VL674_0_Wyse08.bin. Same action taken and outcome as Hagent upgrade.

    February 20, 2016 at 6:53 pm #42479
    elproducto
    Participant
    • Total Post: 94
    • Back Stage Pass
    • ★★★★

    ConfGen,

    Is there anything else you recommend I try?

    February 22, 2016 at 11:41 am #42482
    ConfGen
    Keymaster
    • Total Post: 10696
    • Jedi Master
    • ★★★★★★★

    I have installed HAgent build 117 on my V30LE. After entering the IP of my WDM server and doing a reboot, this unit is now checking in to WDM just fine.
    To install the HAgent addon I’ve simply copied the two files params.ini and WyHAgentaddon.bin to ftproot\hagent\ on my FTP server. On the V30LE I’ve opened the Control Panel-Addons applet and entered the IP of my FTP server and “hagent” as folder. That’s all.

    CG

  • Author
    Posts
Viewing 9 posts - 1 through 9 (of 9 total)
  • You must be logged in to reply to this topic.