cancel
Showing results for 
Search instead for 
Did you mean: 
Excedrin
Level 2
12 9 2 0
Message 1 of 5
1,634
Flag Post

Solved!

HPDM in separate VLAN from clients - how to capture/deploy images?

HP Recommended
HP Device Manager
Microsoft Windows Server 2008 (64-bit)

Recently, the network security guys made a policy of segregating servers like the HPDM server from clients, like our HP thin clients. Now, when I push settings changes and small stuff from the HPDM to the clients, that works fine, but doing anything like a capture or deploy results in the client rebooting into Windows PE mode, but then sitting there on the screen that says "Set Shared Folder" and then finally rebooting after 10 minutes of doing nothing.

 

The error on the HPDM when this happens reads as follows:

[Error Details]: Deploy image using repository Master Repository.
Failed to download t5740_2017-5_ff52.ibr from /Repository/Images/t5740_2017-5-ff52.
Failed to execute DeployImage task.
ErrorCode: 1083392, Error Info:  \Ndm\branches\Release_4.6.5\Source\Cpp\Agents\Core\Task\common\ImageTask.cpp@250:	Failed to connect the shared folder.
\Ndm\branches\Release_4.6.5\Source\Cpp\Agents\Core\Task\common\ImageTask.cpp@249:	The network path was not found.
\Ndm\branches\Release_4.6.5\Source\Cpp\Agents\Core\Task\common\ImageTask.cpp@250:	Failed to connect the shared folder.
\Ndm\branches\Release_4.6.5\Source\Cpp\Agents\Core\Task\common\ImageTask.cpp@249:	The network path was not found.

Can anyone tell if this is possible to do? What ports do I need to open between the two VLANs in order to allow this to work?

1 ACCEPTED SOLUTION

Accepted Solutions
Excedrin
Author
Level 2
12 9 2 0
Message 5 of 5
Flag Post
HP Recommended

Thank you for replying. I was able to fix the issue by adding a second, virtual NIC to the VM that hosts HPDM, giving that NIC a static IP in the second, new VLAN, and then changing the HP Device Gateway program's settings to use that new NIC. I did not need to change the repository information around; only the Gateway was required.

 

However, I believe that HP should make it more clear that the WinPE environment does use broadcasting to find the HPDM server. My network analyst looked at the traffic coming off the thin clients while in in the "connecting to Share Folder" mode, and it was all broadcast...which of course does not work between VLANs. It is a good thing that we were moving all the thin clients to the new VLAN, because if we had to keep some on the original subnet and some on the new, it would be impossible to image them all.

 

Look at this guy's post here from October of last year. He is in that boat.

View solution in original post

0 Kudos
4 REPLIES 4
Excedrin
Author
Level 2
12 9 2 0
Message 2 of 5
Flag Post
HP Recommended

The deploy is supposed to happen without PXE, of course - I know that PXE broadcasts will fail across VLANs. Is there any way to open up a log screen while in the WinPE deploy environment on the client, in order to see more details about the problem? Right now the client machines don't tell me anything at all; they just sit at a screen for 10 minutes and reboot. It'd be nice to see what they're seeing.

0 Kudos
Excedrin
Author
Level 2
12 9 2 0
Message 3 of 5
Flag Post
HP Recommended

What networking protocols are used for the multi-step process of capturing and/or deploying an image? The newest 4.7 HPDM shows HTTPS, SFTP, FTP/FTPS, and "Shared Folders" (which I assume is a way of saying SMB - although I wish they'd just #!$# say SMB then haha).

 

My clients all get stuck at the WinPE screen, "Set Up Share Folder" text on the screen, then reboot after ten minutes. There has to be some way to get client-side logs to see more of what is happening on the client. The server logs are the ones I posted in the original post.

0 Kudos
Chen_HPDM
Level 7
Level 7
504 502 51 84
Message 4 of 5
Flag Post
HP Recommended

Test the share folder connectivity on one of your failed unit using the command:

net use \\<RepositoryIP>\<ShareFolderName> <password> /User:<UserName>

 

HPDM uses standard port for Shared Folder: TCP 139, 445, UDP,137, 138

I am an HPI Employee.
My opinions are my own, and do not express those of HPI.
**Click the White Thumbs Up Button on the right to say Thanks**
Excedrin
Author
Level 2
12 9 2 0
Message 5 of 5
Flag Post
HP Recommended

Thank you for replying. I was able to fix the issue by adding a second, virtual NIC to the VM that hosts HPDM, giving that NIC a static IP in the second, new VLAN, and then changing the HP Device Gateway program's settings to use that new NIC. I did not need to change the repository information around; only the Gateway was required.

 

However, I believe that HP should make it more clear that the WinPE environment does use broadcasting to find the HPDM server. My network analyst looked at the traffic coming off the thin clients while in in the "connecting to Share Folder" mode, and it was all broadcast...which of course does not work between VLANs. It is a good thing that we were moving all the thin clients to the new VLAN, because if we had to keep some on the original subnet and some on the new, it would be impossible to image them all.

 

Look at this guy's post here from October of last year. He is in that boat.

View solution in original post

0 Kudos
Warning Be alert for scammers posting fake support phone numbers and/or email addresses on the community. If you think you have received a fake HP Support message, please report it to us by clicking on "Flag Post".
† The opinions expressed above are the personal opinions of the authors, not of HP. By using this site, you accept the Terms of Use and Rules of Participation