S90 issue

  • This topic is empty.
Viewing 7 posts - 1 through 7 (of 7 total)
  • Author
    Posts
  • #501
    Avatarbazman
    Member
    • Total Post: 10
    • Regular Joe
    • ★★

    Hi Again,

    I have setup my Wyse S90 how i want it to be with background etc.. now i want to create an image from my first wyse s90 and then copy it to the others.

    I have selected package manager and selected the S90 from the device list and it says successfully registered package.

    The the S90 restarts to begin the process and on the black screen it says ‘client is not authorised to operate in this environment’

    once fully loaded, the scheduled update manager then says error next to the update service.

    How can i get round this?

    Thanks

    Barrie

    #9837
    Avatarthinkthin
    Member
    • Total Post: 1707
    • Jacked into The Matrix
    • ★★★★★★

    Hi Barrie,

    If you look at the S90 in the WDM console does it say “imageable” “yes”?

    To image right click on the S90 icon in device manager and select “Get Device Image (requires PXE)” and see what happens,

    Cheers,
    -TT

    #9840
    Avatarbazman
    Member
    • Total Post: 10
    • Regular Joe
    • ★★

    Hi TT,

    It says PXE Capable = YES

    When i select the device for imaging, the unit reboots and then i get a black screen with white text (similar to ms-dos style), it assigns itself a dhcp ip address and is connect to the WDM server.

    Halfway through the scans (while still on the ms-dos style screen) i see a message that says This Client is Unauthorised to Operate in this environment. then the unit restarts and i get an error in WDM to say image failed.

    Any ideas?

    Thanks

    Barrie

    #9841
    Avatarbazman
    Member
    • Total Post: 10
    • Regular Joe
    • ★★

    I have looked at the Error Description in WDM and it says

    ‘No return status from an in-progress update. update moved to error’

    Do this ring any bells?

    Thanks

    Barrie

    #10776
    AvatarHarry20
    Member
    • Total Post: 20
    • Regular Joe
    • ★★

    Hi, I also get this error, I’ve just reinstalled the WDM with hotfixes and still get the error.

    I also get Alone.i2c missing from TFTP root in the logs, but the files doesn’t exist anywhere.

    Any help greatly appreciated.

    #10779
    ConfGenConfGen
    Keymaster
    • Total Post: 9890
    • Jedi Master
    • ★★★★★★★

    Hi,

    would it be possible for you to do a network trace while the unit starts. No scheduled jobs, nothing – only normal boot.
    You should find a package that looks like this:
    PUT /hserver.dll?&V01|&IMAC=008064615722|OS=5|VI=1|AL=windows|AV=4.0.9.0|P1=27|TZ=Pacific.Standard.Time|TZO=-480|MD=2007-09|CN=WBT008064615722|DM=reading.cartech.com|ED=1|SM=255.255.255.0|IP=10.104.11.172|GW=10.104.11.1|DS=204.88.178.5|SN=10.104.11.255|CS=2|FS=128|0D=1|1D=204.88.172.213|2D=204.88.178.5|0W=1|1W=204.88.178.5|2W=204.88.172.213|IM=563.13|CP=.unknown.processor.|CPS=550|NS=0|B1=|PD2=VIA.Unichrome.Pro.IGP.Graphic.adapter|PD1=Audio.AC97.Controller|FSIMP=|RM=131072|SN#=6M30G915282|CO=|LO=|C1=|C2=|C3=|AP0=VIA_DisablePXE||1.0|AP1=VIAWlan||1.44|AP2=Atheros||.Atheros|AP3=ELOTOUCHUSB||2.0|AP4=SLOCKICAVC||2.0|AP5=PPPoE||1.0|AP6=SCRLOCK||1.0|AP7=CERTIFICATES||1.00|AP8=Rapport||4.0.9.0|AP9=ERICOM||8.1.0|AP10=RSHADOW||2.0|AP11=MS

    Find this and post it here.
    Maybe we can see if the client is reporting itself as something else than S90.

    Cheers
    ConfGen

    #10783
    AvatarHarry20
    Member
    • Total Post: 20
    • Regular Joe
    • ★★

    Hi, I think I’ve resolved it:

    Uninstall, remove all DB etc etc, reinstall, reboot and go into DB after 6 hotfixes, then it worked ok…..

    Will test further tomorrow…

    Client doesn’t seem to finish and reboot cleanly? Needed a manual reboot?

    Thx for the response anyway…I guess I’ll be back again!

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