So here's the issue I'm running into. I have HP Device Manager 4.5 and the repository set up on a Windows Server 2008 box. I have the repository and gateway properly configured and I have two test systems, HP T610s running W7E. I created a base image that I would like to deploy to about 20 other Thin Clients, so I've created the image and used the Capture Image template in Device Manager to create the image. I was able to capture the image and it created the appropriate Deploy Image template.
Now here's where it gets tricky. The goal is to be able to push these images out regardless of where they're located - it's a multi-site network. Most sites are hooked up on the corporate VPN, but there are a few stragglers that aren't connected in any way. These are the ones I'm focusing on right now.
So my second Thin Client is located outside of the office. I have all the ports open for HP Device Manager, I specified the gateway in the Device Manager Agent. It sees it, I'm able to give it most commands, but when I go to deploy the base image I run into trouble. It downloads all the necessary files, it grabs the base image, and then it just sits and sits and sits. When it finally decides to do something, it simply grabs all the files again and then sits some more.
My Thin Client that is in the office doesn't have this issue. My thinking is that since it's on the same network as the DM gateway, commands are being pushed as opposed to the agent pulling them down so it's behaving the way it should. I would like to be able to do these deployments remotely, so it's rather critical I get this behaving!
That said, any insight into this that anyone could provide would be greatly greatly appreciated.