-
×InformationWindows update impacting certain printer icons and names. Microsoft is working on a solution.
Click here to learn moreInformationNeed Windows 11 help?Check documents on compatibility, FAQs, upgrade information and available fixes.
Windows 11 Support Center.
-
×InformationWindows update impacting certain printer icons and names. Microsoft is working on a solution.
Click here to learn moreInformationNeed Windows 11 help?Check documents on compatibility, FAQs, upgrade information and available fixes.
Windows 11 Support Center.
- HP Community
- Desktops
- Business PCs, Workstations and Point of Sale Systems
- Re: T620 thin-client not accepting any remote command via HP...
Create an account on the HP Community to personalize your profile and ask a question
05-07-2018 05:13 PM
There is a typo in your first template "Set Bios Config",
The script should be:
BiosConfigUtility64.exe /set:"c:\temp\set_T620_BiosConfig.txt"
Could you please double check on this?
My opinions are my own, and do not express those of HPI.
**Click the White Thumbs Up Button on the right to say Thanks**
05-16-2018 08:21 AM
Hey Chem,
Thanks for your help on previous issue.
I am struggling with new issue with few t620 clients, while sending task via HP Device Manager, its not accepting the task even the TC's are pinging. In the log its only showing "Successfully sent task to the device management gateway".
Actually I was applied new Win10Iot image on them, but my mistake i forgot to mention Execution time and by default after 30 minutes, task suspended because of timeout. Now when i am applying any task it shows following :
I also tried to execute _Update Agent task but same result "Successfully sent task to the device management gateway" after that nothing happen.
Now while re-discovering the above TC devices are not visible but i can connect to the thin clinet via Remote Desktop Connection and old OS is present and everyhting is look good.
HPDMPortCheck from the HPDM server, below is the output of same HPDM server IP :
C:\Program Files (x86)\HP\HP Device Manager\Console\bin\HPDMPortCheck>HPDMPortCh eck.exe 172.16.254.103 -gsm HPDM Gateway port 40003 SUCCESS. HPDM Server port 1099 SUCCESS. HPDM Server port 40002 SUCCESS. HPDM Server port 40005 SUCCESS. HPDM MRC port 40012 SUCCESS. C:\Program Files (x86)\HP\HP Device Manager\Console\bin\HPDMPortCheck>HPDMPortCh eck.exe 172.16.254.103 HPDM Gateway port 40003 SUCCESS. HPDM Server port 1099 SUCCESS. HPDM Server port 40002 SUCCESS. HPDM Server port 40005 SUCCESS. HPDM MRC port 40012 SUCCESS. VNC SSL Proxy port 40004 FAILURE, 10061, No connection could be made bec ause the target machine actively refused it. HPDM Agent port 40001 FAILURE, 10061, No connection could be made bec ause the target machine actively refused it.
HPDMPortCheck from HPDM server to IP of not discoverable TC :
C:\Program Files (x86)\HP\HP Device Manager\Console\bin\HPDMPortCheck>HPDMPortCh eck.exe 10.190.86.101 VNC SSL Proxy port 40004 SUCCESS. HPDM Agent port 40001 TIMEOUT. HPDM Gateway port 40003 TIMEOUT. HPDM Server port 1099 TIMEOUT. HPDM Server port 40002 TIMEOUT. HPDM Server port 40005 TIMEOUT. HPDM MRC port 40012 TIMEOUT. C:\Program Files (x86)\HP\HP Device Manager\Console\bin\HPDMPortCheck>HPDMPortCh eck.exe 10.190.86.101 -a HPDM Agent port 40001 TIMEOUT. C:\Program Files (x86)\HP\HP Device Manager\Console\bin\HPDMPortCheck>
TC which latest image is installed : Agent Verison: 4.7.3669.27086
TC need to be updated not accepting remote command: Agent Verison: 4.7.3669.23482
Problem is from the cetralized management server, these TCs are discoverable but remote task is not accepting as above mentioned same "Successfully sent task to the device management gateway" and from local server/child server not discovering the TCs.
Waiting for your positive reply!
05-16-2018 08:31 AM
I forgot to mention, even i have deployed new image to TCs via central server not from local server, i dont know firstly i was applied by local server because its local and fast deployment but its taking too much time and after timeout, so other one which has been deployed successfully is deployed by central server. Central server is the one server that we can manage any TCs of any sites apert from this we have seperate physical server as a local server for seperate each site.
05-16-2018 05:54 PM
What is the status of the task - Win10 image deployment? Timeout instead of succeed?
Based on the output of PortCheckTool, it seems that the DM Agent service is not running on the Client site.
Can you please check the DM Agent service status?
Try cancel all the tasks, start the DM Agent service and resend simply task like update agent again to see if everything back to normal.
My opinions are my own, and do not express those of HPI.
**Click the White Thumbs Up Button on the right to say Thanks**
05-17-2018 06:34 AM
Hey Chem,
Thanks for your reply back!
As you mention in last reply, actually i was unable to start DM Agent because the following error pops up:
Then go to Xpeagent folder and see the executable file name is _HPEAgent.exe then i removed this _ and now its HPEAgent.exe. Then go to Services and start the DM Agent now its running and even i tested with HPDMPortCheck tool and its working HPDM Agent port 40001 SUCCESS.
Again discover in DM server now all are back avaialble, then applied first task _Update Agent and it was successfull.
After that if i apply any other task its not working, like i have applied _ Write Filter Settings didn't worrk same log "Successfully sent task to the Device Management Gateway" and after that applied Win10 image same result as follows:
But task is not retrieving by the agent.
Here is logs from TC :
Agent.log
2018-05-17 10:26:50 INFO Unified Write Fitler present. 2018-05-17 10:27:00 INFO Agent starts. 2018-05-17 10:27:00 INFO Checking for configuration data in Imaging Persistant Store. 2018-05-17 10:27:00 INFO Imaging Persistant Store restored the following agent configuration: 2018-05-17 10:27:00 INFO Gateway: 10.190.86.2 2018-05-17 10:27:00 INFO Backup Gateway: 2018-05-17 10:27:00 INFO Interval: 1440 2018-05-17 10:27:00 INFO LogLevel: 0 2018-05-17 10:27:00 INFO Delay Scope: 0 2018-05-17 10:27:00 INFO GetGroupsFromDHCP: 1 2018-05-17 10:27:00 INFO PreAssignGroups: 2018-05-17 10:27:00 INFO SaveConfigReg(), Gateway=10.190.86.2 2018-05-17 10:27:00 INFO Read persistent data successfully. 2018-05-17 10:27:00 INFO HM Code is valid. 2018-05-17 10:27:00 INFO XWFManager: already initialized 2018-05-17 10:27:00 INFO GetUWFStatusAndFilter start. 2018-05-17 10:27:00 INFO GetUWFStatusAndFilter end. 2018-05-17 10:27:00 INFO strGatewayWF=10.190.86.2 2018-05-17 10:27:00 INFO strVal=10.190.86.2, Gateway=10.190.86.2 2018-05-17 10:27:00 INFO SaveConfigReg(), Gateway=10.190.86.2 2018-05-17 10:27:28 ERROR Try to get basic network information.
Child.log :
2018-05-17 11:33:45 INFO Unified Write Fitler present. 2018-05-17 11:33:45 INFO Child Agent starts. 2018-05-17 11:33:45 INFO Read settings. 2018-05-17 11:33:45 INFO Read persistent data successfully. 2018-05-17 11:33:45 INFO HM Code is valid. 2018-05-17 11:33:45 INFO strGatewayWF=10.190.86.2 2018-05-17 11:33:45 INFO strVal=10.190.86.2, Gateway=10.190.86.2 2018-05-17 11:33:45 INFO SaveConfigReg(), Gateway=10.190.86.2 2018-05-17 11:33:45 INFO Set log level to 0.
discovery.log:
018-05-17 10:27:30 INFO ---------- Locate gateway start ---------- 2018-05-17 10:27:30 INFO ---------- Locate gateway start ---------- 2018-05-17 10:27:30 INFO Attempting to locate the Current gateway. 2018-05-17 10:27:30 INFO Attempting to locate the Current gateway. 2018-05-17 10:27:30 INFO The Current gateway is set to [10.190.86.2]. 2018-05-17 10:27:30 INFO The Current gateway is set to [10.190.86.2]. 2018-05-17 10:27:31 INFO ---------- Locate gateway start ---------- 2018-05-17 10:27:31 INFO Attempting to locate the Current gateway. 2018-05-17 10:27:31 INFO The Current gateway is set to [10.190.86.2]. 2018-05-17 10:27:31 INFO Located the Current gateway [10.190.86.2]. 2018-05-17 10:27:31 INFO ---------- Locate gateway end ---------- 2018-05-17 10:27:33 INFO Located the Current gateway [10.190.86.2]. 2018-05-17 10:27:33 INFO ---------- Locate gateway end ---------- 2018-05-17 10:27:34 INFO Located the Current gateway [10.190.86.2]. 2018-05-17 10:27:34 INFO ---------- Locate gateway end ---------- 2018-05-17 10:27:35 INFO ---------- Locate gateway start ---------- 2018-05-17 10:27:35 INFO Attempting to locate the Current gateway. 2018-05-17 10:27:35 INFO The Current gateway is set to [10.190.86.2]. 2018-05-17 10:27:38 INFO Located the Current gateway [10.190.86.2]. 2018-05-17 10:27:38 INFO ---------- Locate gateway end ----------
Now when i am going to check DM Agent is running or not but there is not DM Agent service is the list.
When going to C:\Windows\xpeagent>HPDMAgent.exe enter
I dont know what's going on, please help me out !
05-18-2018 12:26 AM
More info of above post:
After applying _Update Agent task, i have seen HPDMAgent.exe file is copied in the location : C:/windows/temp folder.
Currently i have five clients with have this issue, Is there any way to install HPDM Agent completey fresh or from the scratch. Even i tried to copy complete folder "xpeagent" from any working TC and delete this folder from non-working TC and paste working "xpeagent" folder but this time when ruuning HPDMAgent.exe its run without any error but when i go to services then no service with HPDMAgent shows there. Now HPDMAgent .exe file is running but service is not there in the list but i dont no really how to add service or any other ways to to it easily.
Please have a look on my above describes problem.
Thnaking you!
05-18-2018 01:33 AM
To install HPDM Agent service from stratch you have to
- Disable Write Filter
- copy the HPDMAgent.exe from MasterRepository: ..\Repository\Agents\HPWE8_64 to the Thin Client
- Double click HPDMAgent.exe to start the installation
- After process ends check the service, enable Writer FIlter if everything back to normal.
Where did you get the Win10IoT image? Based on the information you provided - _HPDMAgent.exe in the xpeagent folder. The image file should either be from HP Web site or Capture by Thin Update. For some reasons the the DM Agent service doesn't back to normal after the image deployment.
What's the original image on the Thin Client? Have you update the DM Agent to the latest version before applying the Win10IoT image?
My opinions are my own, and do not express those of HPI.
**Click the White Thumbs Up Button on the right to say Thanks**
05-18-2018 02:18 AM
Thanks for your reply!
Win10Iot image is dwonloaded from Thinupdate, rest of all TCs are working i alreday told you some five clinets failed to download image and having this Agent problem only to failed image one.
I haven't done prior any Agent update after applying new WIn10Iot image the agent automatically get updated.
OLD Image:
Image Version: 14WWFTBJ601#SABB#DABB
Agent Version: 4.7.3669.23482
After updating to new image.
NEW Image:
Operating System: Windows 10 Enterprise 2016 LTSB
Image Version: 14WWFTDJ601#SABA#DAus
Agent Version: 4.7.3669.27086
05-18-2018 02:23 AM
Okay, since this is an intermitant issue, please first try the steps in my previous post to install HPDM Agent from stratch.
I will report the failure to the team to see if they could do something to enhance the deployment process.
My opinions are my own, and do not express those of HPI.
**Click the White Thumbs Up Button on the right to say Thanks**
Didn't find what you were looking for? Ask the community