Forum Replies Created
-
Posts
-
Thinkthin,
Well done, you found the cause of the problem! 😀
It seems that the PXE imaging boot process cannot handle FQDN to download their images! Once changed to the physical IP address of the server it worked!.
Once again thankyou Thinkthin for your help and keep up the good work – it is a fantastic source of information!
Kindest Regards
DarronThinkThin,
The test connection was sucessfull.
The location was set to a FQDN so i changed this back to the IP address of the rapport server. I have just pushed a new config to the machine to test but am not at the office so am working blind. I will advise as soon as it comes back with anything.
The user password was set to never expire as per yet another great tip from this website – Keep up the good work ThinkThin!
Many Thanks,
DarronThinkthin,
Sorry, missed that off the last post. The logs are all clear – nothing of any use whatsoever.
Its weird as nothing has changed since it was installed? (except for the Microsoft critical updates)
Its certainly a weird one!
Darron
Thinkthin,
FYI the ammended script fixed the issue of not being able to select devices. Thanks.
I look forward to your response re the ‘Open Error’ message.
Regards
DarronThinkthin,
I applied the two hotfixes as requested, and have rebooted the server. All seems well however when i go to update the images, the devices are no longer listed in the ‘Select Device’ screen. The devices are listed in device manager (green icon) and are showing PXE boot = yes.
I will look into it and will post the solution, however please do advise if you know what the cause is.
Regards
DarronEDIT***
I have not yet been able to apply an image to my XPe terminals, however if i get an image from a device i have the same problem as first posted with ‘OPEN Failure’.It appears that the hot fixes did not resolve this issue and may have caused another one!
Asif, Annu,
The changes made on the DHCP server caused a terminal to not boot (invalid image i believe) – i am installing at a new site so am not going to look into it more – i simply undid those changes which cured the problem.
We do not use PXE beyond Rapport so it caused no other problems for us.
Again, i will look into the problem next week when back in the office.
Cheers
DarronThanks Thinkthin for the hotfixes and to Asif and Annu for the DHCP server suggestions.
I am not in the office until Monday so cannot test this until then. I will post a response on this as soon as i know.
thankyou for your help.
Cheers Thinkthin for the promt reply.
I am running on a windows 2003 box with SP1 (Rapport was installed pre SP1) and i have installed the Wyse hotfix.
I have checked the event logs and there are no errors listed.
I have checked the IIS logs also and they are of no use.
Cheers
DarronFirstly, if you have to make changes on the terminal but cannot go there directly, why dont you use the VNC client on the terminal? That way you can take control directly and make the changes yourself rather than talking somone through it blind.
Secondly, if all the terminal are identical and need to be set with the same config, you can set one up yourself first (i recommend imaging them to the latest version also – there were lots of improvements when i last did it) and them copying the image into Rapport. You can then send the image to all of the other devices with all configurations pre set!
*EDIT
One of the useful updates after installing the latest terminal image was the improved write filter. The version i now have allows it to commit changes at the next reboot allowing you make the changes without repeated reboots.
*EDIT***Note, dont try this over a WAN as the images are huge!
I hope this helps.
Darron
