package push.

  • This topic is empty.
Viewing 8 posts - 1 through 8 (of 8 total)
  • Author
    Posts
  • #1092
    mikev
    Member
    • Total Post: 147
    • Legend in Own LunchBox
    • ★★★★★

    hi,

    in WDM, in the past when i use to push any image or package to any terminal, the “update now” screen use to pop up immediately on the device.

    now, when i try to push any package or image to any device, the “update now” screen does not pop-up but at the same time the installation is scheduled in the scheduled packages. And then, when i manually restart the unit the “update now” screen appears.

    can anyone please advise why the “update now” screen does not appear first time when i push the package?

    thanks.

    #12484
    Joe
    Member
    • Total Post: 96
    • Back Stage Pass
    • ★★★★

    Check the timezone on your database server and your WDM server. If these do not match, it can cause problems.

    You will also want to verify that the time is the same on both servers.

    As a test, push an image. If everything is working as you say, it will not deploy. Find the device in device manager and refresh it. Does the image deploy?

    Give ConfGen’s WDM faq a once over. There is some good stuff in it, as well as a section regarding jobs not executing.

    https://technicalhelp.de/index.htm

    #12517
    mikev
    Member
    • Total Post: 147
    • Legend in Own LunchBox
    • ★★★★★

    Thanks Joe.

    I am using local SQL server on my WDM and so my database and WDM server are the same.

    The time on the server and the client also match – so no issues here. when i try to push a package or image it works but i get the update now screen only after rebooting the wyse terminal.

    i also tried deleting the wyse device in WDM but result the same. any more ideas please?

    thanks

    #12530
    Joe
    Member
    • Total Post: 96
    • Back Stage Pass
    • ★★★★

    When I mentioned refreshing the device, I didn’t mean deleting it. Send it a job, and when you’re sure it’s not going to execute, right click on the thin client (in the device manager) and choose refresh — does the job execute?

    You can try clearing the system log. I’ve seen this cause problems like this in the past. You’ll have to get MDTools from wyse unless you’re familiar with SQL enough to go in and clear out the table. MDTools makes it easy to empty the table if it gets full.

    Do you happen to have your logging turned up too much? You should only have it set for errors, otherwise the log can get too full.

    Make sure you have no firewall (or proper rules created!) on your WDM server.

    And did you get a chance to look through that document on WDM support that I linked you before? Lots of good stuff in there that will probably fix your problem!

    #12591
    mikev
    Member
    • Total Post: 147
    • Legend in Own LunchBox
    • ★★★★★

    hi,

    i tried refreshing the unit in the WDM but the job still does not execute. it only executes when i reboot the device and then the “update now” screen immediately pops up. I have to restart the terminal everytime when i push the package.

    i tried cleaning the system log as well – no luck.

    the firewall on the server and client is already turned off.

    i also looked into the document following the link above. I tried steps like changing the time zone in WDM configuration to options like console and device – but nothing helped.

    also, this issue only started a few days back. everything was working normal a few back – some days before when i use to push the package, the “update now” screen use to popup immediately on the client and doesn’t happen now.

    all of a sudden this has changed – cant recollect of anything got changed on the server.

    any more ideas?

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

    Is the device in the same subnet? Can you check the event log and see if there are any error on the server? Is the Hagent matching the version on the WDM server?

    Cheers,
    -TT

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

    Oh, one more thing. I saw your post you are on WDM 4.5.2 – that version was a dud, use 4.5.3. Actually 4.5.1 with the hotfix roll-up was the most stable release of recent times,

    Cheers,
    -TT

    #12600
    mikev
    Member
    • Total Post: 147
    • Legend in Own LunchBox
    • ★★★★★

    Thanks TT.

    My Rapport server and the device on which i am trying to push the package on are at different physical locations – different subnets.

    My Hagent version also does match – 5.0.0.7.

    No specific event log on the server.

    Also, as you said i am definately looking at upgrading to v4.5.3 – may be it might fix most of the issues.

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