-
×InformationNeed Windows 11 help?Check documents on compatibility, FAQs, upgrade information and available fixes.
Windows 11 Support Center. -
-
×InformationNeed 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
- HPDM Deploy Image Rule going in loop

Create an account on the HP Community to personalize your profile and ask a question
04-03-2023 04:41 PM
Using HPDM to manage t640 ThinClients running ThinPro 7.2
Was able to capture an image and deploy the template to ThinClients manually without issue.
Tried setting up a rule on First Contact to deploy the image.
Problem is the rule runs in First Contact with new ThinClients that are discovered, but it goes into a loop and keeps redeploying the image over and over again.
issue appears to be that First Contact in the description is for when first discovered (which is what we want) or if a Factory Reset is done.
best guess is after it deploys the image that is triggering the factory reset variable making it run again.
any ideas on how to prevent this?
desire is to discover new devices and have it automatically deploy the custom image and then it’s ready for the user.
04-13-2023 03:00 AM
Can you show some screenshots how the Rule is setup and how the template looks like?
Is there a script in the image to delete e.g. hostname that might trigger this?
You are correct that the Rule First Contact only applies to devices that HPDM found for the first time or after a factory reset.
A workaround would be to use a Start Up Rule that asks if a Program Record is in the image which you set so it will only image units with or without that Program Record.
You can find more info about Program Record in the HPDM Admin Guide.
04-13-2023 10:44 AM
Worked with HP and they recommended running the tasks within a Sequential Template instead of doing each task as its own rule.
This fixed the issue.
They believe what was happening was if either the Rename task was last or the Image Task was last it was triggering the First Contact parameter in the Rules to rerun.