Forum Replies Created
-
Posts
-
How did you go with this?
Ours dont seem to pass through the authentication details (so you get a normal windows logon prompt) and they also seem to cause the server to die a slow death when you logon using one.
We are running XA6 on R2.
A
I had a similar issue – turned out it was a Cisco switch hammering the TFTP server which it got from the TFTP server setting in DHCP, causing it to flake out. For a while we had to restart the Rapport4 service between each image and every image process. Obviously WDM takes great offence to frequest bad requests and just dies.
Switch on the debug logging in WDM and restart the service, then double click on the system tray icon. If this is happening, you will see it in the logs.
A
In WDM, set the logging options to Debug and then double click the icon in the system tray. It may give you more clues.
Or you can just make the changed manually to each key in HKU – one of whicy will be the key for the user.
Specifically:
HKEY_USERSxxxControl PanelDesktopWallpaper – just put in the path to your background/logo.A
I found that if the terminal was booting for the first time, the w32tm command was not reliable. I tweaked it to add a 10 second delay before executing the command. I can only assume it was because the network wasnt ready or something….
A
We had this same issue.
Ended up ditching Neutron and the NTP thing all together.
I made some alterations to allow w32time to be able to set to the correct date/time when the current date/time is way out – then I copied w32tm from another PC onto the terminal and then used the command ‘w32tm /resync /nowait’ in HKLM/bla/bla/Run to kick it off at logon.Job done.
Yep – thats exactly what I did – except that article does not mention adding specific options for the new Vendor.
If/when you create a new vendor, you need to create the options for it – otherwise there aren’t any there.
Its not working at all!
I tried the two angles to see if it was specific to the terminals.
Got this pearler as well when trying to image to another S90-L – but I have a feeling that there is something else going on with this particular terminal that isnt quite right.
Try 1:WISard-FAILURE-Environment-Security-Key-Failure
We have a number of S90’s doing the same thing and have opened a ticket with Wyse about it.
This almost worked!
It got the the PXE screen but then got a READ error when it tried to load up the imaging software…………
Also, I have noticed in the Log (which I have turned up to debug) that when that S90 tries to boot, WDM reports:
[DHCP] – Device 00806469A63D is a RTI Agent.What does this mean?
It does not seem to do it for any of the other terminals which are OK.Aaron
