HPDM 4.7, SP6, Error 34603008, Cannot Capture Image from t520

[IbisHotline]

hi,

i cannot pull images from my t520 thinclients using hpdm 4.7, sp6 anymore.

error number is 34603008, aborting ftp connection, exit code 8.

in the past i was able to capture and deploy images without a hassle.

hpdm 4.7 sp6

agent vers 4.7.3671.26470

windows server 2012r2

iis ftp on the same machine

thinclient t520 runing thinpro t7x61007

repository test for ftp, smb successfull

manual ftp control successful

firewall off

tried reinstalling hpdm without success.

[IbisHotline]

i figured out why capturing and deploying images per hpdm fails - it's the component manager.

capturing and deploying an image works fine until you remove components by using component manager.

we removed everything we don't need for our RDS farm (f.e. chinese language, citrix, and so on ...) leaving us with the following packages: firefox, thinstate, vnc, rdp, hpdm, smbclient, misc-connections.

with that configuration capturing an image per hpdm crashes while parsing the .ini file.

leaving the provided packages intact does not provide an error, imaging works fine.

looking forward to input in this matter: obviously we want our thinpro packages as small as possible ...

[Jeffxu · Accepted solution]

Congratulations. If only remove language and connection components, it will not affect HPDM function.

[RajDebashish]

HPDM 4.7, By default when HPDM is installing it installs at the C:\inetpub\FTProot and then HPDM folder. This HPDM folder will be shared and the FTProot will be given the security access with the particular username that was given while setting up FTP. Please check the Repository Settings and permissions for Shared Folder . Although I am an HP Employee, I am speaking for myself and not for HP.

[IbisHotline]

Hi,

thank you both for your input.

@Jeffxu i can confirm that removing language and connection components (citrix in my case) does not prodce an error.

@RajDebashish as you can see in my original posting this bug appears despite correctly configured repositories and shares.

i would appreciate a fix for this bug (maybe in sp8?).

thank you!