We are working with several different types of thin Clients that are using different type of connections (some use Citrix and others use VMware). We set up a schedule that will push out the correct connection setting to the machines (depending on what group they are set to) at startup. The problems beings when the connection setting is sent. It will restart the machine, which will start a never ending reboot, send, reboot, send...... Is there a way to keep HPDM from rebooting the machine after it pushes the connection settings?
I'm running into the same issue. Has someone found a solution (or a work-around) for this yet?
Actually I want one of two things:
1. Push a connection on startup, without rebooting the client
2. Push a connection on startup, if a client does not have that connection (yet)
For the first option, I would need a setting of some sort to prevent rebooting after running the Push Connection task (maybe on the rule itself?).
For the second option, I would need a Device Filter that gives me devices that should have that connection, but don't have it yet.
So it would consist of two parts:
- Is hostname like [prefix_connectionname] // To determine it needs this connection - Is [current connection] (or maybe [Extended Property]?) NOT [desired connection] // To determine it doesn't have it yet