HP t5740 (freeDOS) RDeploy freezes
Updated: 21 May 2010 | 21 comments
This issue has been solved. See solution.
Hi,
I am testing new thinclient t5740 (Atom processor) from HP with Altiris Deployment Solution 6.9 (build 375). I am using internal PXE server and FreeDOS boot image. When I want to create image from HP thinclient, it boots correctly from PXE, connects to Deployment server, but when Rdeploy.exe start the client freezes. On HP thinclient t5730 (Sempron processor) works it perfectly. Is there any fix for RDeploy or other solution?
discussion Filed Under:
Comments
try to use text mode (console
try to use text mode (console version) Rdeploy.exe if that helps
I am using text mode version.
I am using text mode version. I also tried to boot to DOS prompt and run RDeploy.exe manually with same result.
I have tried using Altiris
I have tried using Altiris and a DOS boot disk. The T5740 hangs on rdeploy and rdeployT from a DOS boot disk. Using altiris the TCP stack unloads after rdeploy tries to kick off. Have you gotten this to work?
I have had mixed success in
I have had mixed success in the past with FreeDOS. Have you considered rebuilding the bootdisk for MS-DOS?
Kind Regards,
Ian./
Ian Atkin, Senior Developer for the ICT Support Team, Oxford University, UK
Connect Etiquette: "Mark as Solution" those posts which resolve your problem, and give a thumbs up to useful comments, articles and downloads&
Hi I am also experiencing the
Hi
I am also experiencing the same issue with the HP Thin Client t5740 (while the t5630 worked).
I am using Altiris DS 6.8 with DOS Managed and Rdeploy hangs in both RDeploy and RDeploy (Text Mode).
I can switch to WinPE Managed, but fails to get a DHCP address once WinPE boots:
Validating IP Adress ...
Restarting DHCP Client Service Retry 1 ...
Restarting DHCP Client Service Retry 2 ...
Restarting DHCP Client Service Retry 3 ... etc...
WinPE Managed
I solved it with WinPE Managed too. You must insert into WinPE image right LAN Drivers, it helped in my case..
Stanky is correct -this DHCP
Stanky is correct -this DHCP problem is indicative of WinPE not having the correct NIC driver loaded. You'll need to add your NIC driver into your WinPE automation image.
With MS-DOS, you might also get some success using the UNDI driver, or an updated DOS driver for the NIC. I've seen imaging problems with early broadcom NICs which were nicely resolved by updating to more recent broadcom drivers.
Ian Atkin, Senior Developer for the ICT Support Team, Oxford University, UK
Connect Etiquette: "Mark as Solution" those posts which resolve your problem, and give a thumbs up to useful comments, articles and downloads&
We are having the same exact
We are having the same exact problem with the t5740 freezing when typing in rdeploy. I've tried DOS, Linux, and WinPE.
Ann
ACurler, Wow -its unusual
ACurler, Wow -its unusual for something to freeze all automation environments. So, I've got a bundle of questions for you,
Ian Atkin, Senior Developer for the ICT Support Team, Oxford University, UK
Connect Etiquette: "Mark as Solution" those posts which resolve your problem, and give a thumbs up to useful comments, articles and downloads&
ad1. Yes, on all. I've tested
ad1. Yes, on all. I've tested 3 pcs.
ad2. After boot to automation, when RDeploy attempts to start. I tryed to boot only DOS (FreeDos) and run RDeploy manually, when I typed "rdeploy" in command line it freezes.
ad3. Yes, t5740 becomes completely unresponsive.
Hi Stanky, Have you tried
Hi Stanky,
Have you tried MSDOS? It might be that RDeploy is crashing out as its trying to contact the disk controller.
Ian Atkin, Senior Developer for the ICT Support Team, Oxford University, UK
Connect Etiquette: "Mark as Solution" those posts which resolve your problem, and give a thumbs up to useful comments, articles and downloads&
No I didn't.
No I didn't.
I'd give MS-DOS a try. As
I'd give MS-DOS a try. As i've said many a time before i've experience issues with FreeDOS in the past, so much so that on my training courses I advise Altiris Admins to avoid it where possible.
Ian Atkin, Senior Developer for the ICT Support Team, Oxford University, UK
Connect Etiquette: "Mark as Solution" those posts which resolve your problem, and give a thumbs up to useful comments, articles and downloads&
Solution for t5740/t5745 from HP
Original text from HP
The HP t5740 and t5745 Thin Clients have an issue with DOS image capture and deploy using rdeploy and rdeployt. That symptom is a hang shortly after the rdeployt or rdeploy imaging engine starts to capture or deploy an image on the thin client.
Cause:The Dos Protected Mode Interrupt handler (DPMI) that is internally bundled with rdeployt and rdeploy is not compatible with the t5740 and t5745. The attached version of rdeployt was built with a DPMI handler that is compatible with the t5740/t5745.
Installation Instructions:
a. Note the above directory path may look a bit different under older DS versions.
a. Note the directory path may look a bit different under older DS versions.
b. Also note the directory structure does not explicitly include the word DOS, however the rdeployt.exe here is the same file used for DOS.
To use when imaging from a bootable device such as a USB flash drive:
Note:
The attached rdeployt was validated on HP t5740 and t5745 thin clients using Deployment Solutions 6.9 SP3. It has not been validated on other platforms or on other versions of Deployment Solutions. Customer wishing to use this modified version of rdeployt on other devices or other versions of deployment Solutions should first verify it meets their needs in a non-production environment.
Excellent
When you give this a try, could you report back to the forum and let us know the results?
Ian Atkin, Senior Developer for the ICT Support Team, Oxford University, UK
Connect Etiquette: "Mark as Solution" those posts which resolve your problem, and give a thumbs up to useful comments, articles and downloads&
My report will follow next
My report will follow next week. First I have to upgrade from version 6.8 to 6.9 SP3. I will first perform the test next week.
Just one, it's the only one
Just one, it's the only one in our environement right now. In MSDOS it freezes right after I press F2. In Linux it freezes at the # mark, and in WinPE is says Restarting DHCP client service. Retry 1 and so on. When it freezes the thin client becomes completely unresponsive.
We have the same problem
Analyzing the BootWork Partition. Please wait.....
I'm having this exact same
I'm having this exact same issue. It gets to "Analyzing the BootWork Partition. Please wait..." and then never goes anywhere. Did you ever figure out how to get past this?
If you decide to use WinPE
If you decide to use WinPE instead and you get the DHCP retry messages, it is a missing NIC driver. Here is a blog entry I wrote to troubleshoot this. First you have to determine what the device information is on this model, then you just need to add the right vista 32 or 64-bit NIC driver to to WinPE.
https://www-secure.symantec.com/connect/blogs/troubleshooting-driver-issues-your-winpe-bootdisk
Error when using winpe
I am trying to use Winpe but get an error when trying to distribute the software to the thin Clients.
Here is the error: "Error 112: Not Enough disk space for package ' (package path)'"
The package is 132M
The thin clients ram disk is set the max of 96 MB
If I change the system variables on the thin from z:\ to c:\ it works
I know its an issue of where the package is trying to download and run. By default its in the system temp which is Z:\temp (the ram disk) on a thin.
Am I missing something. In the past I have always used the DOS boot image.
Would you like to reply?
Login or Register to post your comment.