WDM 4.5.1

Viewing 11 posts - 1 through 11 (of 11 total)
  • Author
    Posts
  • #262
    TomFrank
    Member
    • Total Post: 13
    • Regular Joe
    • ★★

    I now have v4.5.1 i will let you know what i think about it and which issues it resolves.

    Thanks

    #9100
    TomFrank
    Member
    • Total Post: 13
    • Regular Joe
    • ★★

    Using version 4.5.1 now and have discovered an issue already which has been logged with wyse.

    If you try to manually add a device in a device view then you get a database error and it doent add to the database properly resulting in not being able to push an image to the device.

    There is a workaround for this by adding the device in the view all devices view. strange but works.

    Seems like version 4.5.1 has sorted the service crashing issue of 4.5 which is good.

    I will post anymore findings.

    #9108
    TomFrank
    Member
    • Total Post: 13
    • Regular Joe
    • ★★

    Is anyone having a problem with PXE boot with v4.5.1 and V90’s or is it just me?

    It seems that when i either drop an image on a terminal or try to pull an image from one the device gets the ‘update now’ dialog box which i click on. It reboots then fails to PXE boot and just boots back up!? Then sometimes if i manually reboot the device after this it manages to PXE boot and pull/push the image!?

    Any ideas or similar experiences??

    #9113
    _Dave
    Member
    • Total Post: 2
    • Newbie

    Recently, I’ve updated our Rapport 4.4.1 to 4.5.1 and have noticed the PXE problem you mentioned along with a few other issues. I have to do a manual reboot as well for PXE to kick in but it very seldom happens.

    Some other issue’s I’ve noticed are:

    – I usually don’t get the “Update Nowâ€￾ screen until I manually reboot.
    – The XPHagentW update blue screens a number of our V90 clients.
    – Scheduling a package to install after the next boot doesn’t seem to work

    Sorry I couldn’t help you, just added more to your list if anything 😯

    #9114
    thinkthin
    Member
    • Total Post: 1649
    • Jacked into The Matrix
    • ★★★★★★

    This is great,

    Keep posting the issues guys so we can collect a list. It was posted in the XP forum but I have a few people seeing issues with the new V90 duel video models not working correctly with 4.5.1.

    I have seen the Blue Screen trying to upgrade S90’s, the stop says error is caused by the EWF however the unit works OK with a manual re-boot. This was a timing issue a while ago on older XP agents and it looks like its back. It does not break the unit but its annoying as it requires user intervention.

    #9447
    MrVirtual
    Member
    • Total Post: 19
    • Regular Joe
    • ★★

    Hi,

    Any news on the BSOD on the S90’s as described by TT?

    I have a large number of S90’s distributed across many sites that would cause me pain if WDM required user intervention on each or even half of them for an update.

    #9450
    thinkthin
    Member
    • Total Post: 1649
    • Jacked into The Matrix
    • ★★★★★★

    Are you seeing this issue?

    I solved it by upgrading the Rapport agent on the clients before I upgraded the server to 4.5.1.

    Put 4.5.1 in a lab (isolated) and discover a few units and see if you have the issue,

    Cheers,
    -TT

    #9497
    MrVirtual
    Member
    • Total Post: 19
    • Regular Joe
    • ★★

    Hi TT,

    I have the latest HAgent 4.0.5.5 deployed.

    Still running Rapport 4.4.1 BSOD on EWF mostly when trying to change the location information in Rapport.

    Also BSOD whth a package update 🙁

    I do not think that 4.5.1 will help this issue as it seems to be a HAgent/EWF issue.

    #9498
    thinkthin
    Member
    • Total Post: 1649
    • Jacked into The Matrix
    • ★★★★★★

    Hi,

    I had the same issue and I is a timing issue where the EWF has not finished flushing the cache before the shut down starts and you get a BSOD. It does not harm the unit as its a memory error but you are left with a unit in the field that can not be managed.

    I got an updated Hagent to deploy however I altered the script to manually turn off the EWF from the command line and then deploy the updated Hagent. After this I could go back and push packages normally.

    Let me locate the files I used and I will post,

    Cheers,
    -TT

    #9499
    thinkthin
    Member
    • Total Post: 1649
    • Jacked into The Matrix
    • ★★★★★★

    Here is the source file:

    http://www.freewysemonkeys.com/site/modules.php?name=Downloads&d_op=viewdownloaddetails&lid=92&ttitle=XPe_HAgent_4232.exe

    You will need to alter the script if it will not push to manually turn off the EWF from the command line. You can use the ewfmrg /? on a terminal to see the switches from memory. Enter these and remove the QU and LU in the script. Don’t forget to remove the LU at the end and manually turn the filter on again!

    #9526
    MrVirtual
    Member
    • Total Post: 19
    • Regular Joe
    • ★★

    Thanks TT for the HAgent

    I have it and am now testing.

    I did look for an update on the Wyse site, why do Wyse not release this via their web as the S90’s still only show HAgent 4055.

    My rant any way..

    Many thanks to you and freewysemonkeys! this site saves my bacon! 😛

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