-
×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
- Disable sleep mode HP Thin Client T430
Create an account on the HP Community to personalize your profile and ask a question
06-30-2022 08:54 AM
Hell Taner,
There might be no direct way this might work on Win10 IoT for thin client. you would need to make changes on GPO for this.
You may need to modify the below GPO Settings:
Computer Configuration> Administrator Templates>System>Power Management
Specify an Active Power Plan - ENABLED and set to High Performance
Sleep Settings / Allow Standby States (S1-S3) when Sleeping: DISABLED (this shuts off the "Sleep" and "Hibernate" button).
I am not sure if Hibernate is enabled by default, however if you want to ensure to disable it, use the command :
powercfg.exe /hibernate off
below links from Microsoft should help you:
https://docs.microsoft.com/en-us/windows-hardware/customize/power-settings/sleep-settings
Make it easier for other people to find solutions by marking a Reply 'Accept as Solution' if it solves your problem.
08-11-2022 01:04 PM
Hi, I resolved my issue.
Thank you for your post.
It was conflict between 3 thin clients.
2 thin clients tried to manage one thin client with Information display trough. Net application.
When two device try to manage 1 then the screen of this thin client go to sleeping and don't work as expected.
I catched the issue with netstat.
Then I just disabled one of two devices and issue has been resolved.
Now thin client with information display is controlled only by one thin client and display turn on and off is successfully controlled by only one thin client without any issues.
It was configuration issue.
Didn't find what you were looking for? Ask the community