Failed Task _Capture Image

[Jamie_Peterson]

Working with Device Manager 4.6, using the template _Capture Image to capture an image from a t5740e Thin Client.

I completed the Image Name, Description, not using the advanced Options "Cached Imaging", completed the "Save result as template" then Save as ... to create the actual template used on the device.

I dragged the Template over to the t5740e Device and the following was the result:

2016-05-23 12:31:02 Successfully sent task to the Device Management Gateway

2016-05-23 12:31:04 Task has been retrieved by the Agent.

2016-05-23 12:31:07 Capture image to the Master Repository.

2016-05-23 12:31:07 NOT SUPPORT!

2016-05-23 12:31:07 Failed to execute common task.

2016-05-23 12:31:07 ErrorCode: 14000052, Error Detail: Unsupported task.

2016-05-23 12:31:07 Failed to execute common task.

2016-05-23 12:31:07 ErrorCode: 14000052, Error Detail: Unsupported task.

I checked from the t5740 Thin Client that I had access to the Shared folder on the Server where the Master Respository\Repsoitory is located, and I could create a folder and delete it.

When I was checking this it did require my credentials to login to that location.

I am running the HPDM 4.6 from the server where the repository is located as well.

I am not finding any documentation on "NOT SUPPORT! in this case means, what is not supported?

Thank you for your help

[Chen_HPDM]

Can you please confirm:

1. Is this MS windows7 or WES7E released by HP?

2. What's the HPDM Agent version on the Thin Client

3. Can you please try Cached mode to see the result?

[Jamie_Peterson]

Question (1) - I am using the WES7E released by HP

Question (2) - The Agent version on the Thin Client is 4.4.3660.12652,  the Agent version on the server I think if I am looking at the right folders is one of the following:

Computer > Local Disk > Inetpub > Ftproot > HPDM > Repository

HPCE > 4.6.3662.19313

HPThinPro > 4.6.3662.19313

HPThinPro4 > 4.6.3662.19313

HPThinProZero > 4.6.3667.19313

HPWE8_64 > 4.6.3669.19313

HPXPe > 4.6.3660.19313

Question (3) - I repeated the process using the _Capture Image, using the cached option checked this time, and got the same error results as above in the message and I located the MasterRepositoryController - log file and this is what was recorded the two times I have used this Template

This was the 23rd

2016-05-23 12:31:06 ERROR Failed to delete package:"HP-751 Image 5-23-2016".
2016-05-23 12:31:06 ERROR .\DeleteTask.cpp@77: Failed to delete local package.
.\DeleteTask.cpp@227: Failed to delete package:"HP-751 Image 5-23-2016".
.\common\util.cpp@269: The system cannot find the file specified.

This was the today

2016-05-24 09:59:25 ERROR Failed to delete package:"HP-751_Capture_Cached".
2016-05-24 09:59:25 ERROR .\DeleteTask.cpp@77: Failed to delete local package.
.\DeleteTask.cpp@227: Failed to delete package:"HP-751_Capture_Cached".
.\common\util.cpp@269: The system cannot find the file specified.

I just noticed something, it might be the HP Write Filter setting not "Disabled", disabled the filter same result

This was after the "Disabled - Write Filter

2016-05-24 10:48:54 ERROR Failed to delete package:"Capture_751_Cached".
2016-05-24 10:48:54 ERROR .\DeleteTask.cpp@77: Failed to delete local package.
.\DeleteTask.cpp@227: Failed to delete package:"Capture_751_Cached".
.\common\util.cpp@269: The system cannot find the file specified.

I don't know if this helps

Thank you for your help

[Chen_HPDM]

Then you may missed the step of update Agent to the latest version. 

You have to update the DM Agent from 4.4.3660.12652 to 4.6.3660.19313 before executing the imaging task with the DM Console.

[Jamie_Peterson]

Thank you for your help with this issue, I am following behind a previous employee responsible for this and learning HPDM application at the same time.  

Yesterday I installed one of the _Deploy Image's Task Templates that was created back on 5-5-2015, it completed successfully, and when I started the Thin Client, in HPDM it now shows an Agent Version of 4.5.3660.19746 which is newer than the one I started with, this might have the update agent turned on in the template.

I have a user base of about 53 users, most on Agent Version 4.4.3660.12652, a few on 4.4.3660.12990, one on system on 4.5.3660.19746, and one on 4.6.3660.19313.

I tried to determine where this file was on the server, but only found the all of the ones listed above in the message on 4.6.3662.19313, 4.6.3667.19313, and 4.6.3669.19313.

Is the Agent updated on the server using HPDM from there?  

Then all of the Task Templates that deploy will use this Agent?  

Will the newer Agnet affect the current users on the older version of the Agent, or does it just set the Agent version going forward for any Task Templates created?

Or do you update the Agent Version on the Thin Client?

Thank you again for all of this help

[Chen_HPDM]

Once you have upgrade your DM server, the Agent files in the Repository will be replaced with the latest one.

The things I'm asking is to update the Agent on the Thin Client. Basically you need to drag the "update Agent" template to those devices with old Agent version, the task is mainly to download the latest Agent files from your Repository to the Thin Client and do the upgrade.

The newer Agent will provide new/enhanced functionality comparing with the old one, so please make sure the DM Agent on the Thin Client side is always up to date before sending other tasks.  

[Jamie_Peterson]

I understand the process a lot better now with your explanation, thank you for the explanation 

I tried running the _Update Agent Task Template on a Thin Client that is currently configured with Agent version 4.4.3660.12652 and I received the following errors:

2016-05-26 09:46:48 Map repository to: Master Repository

2016-05-26 09:46:48 Map repository to: Master Repository

2016-05-26 09:46:48 Successfully sent task to the Device Management Gateway

2016-05-26 09:46:52 Task has been retrieved by the Agent.

2016-05-26 09:46:53 Copy files using repository Master Repository.

2016-05-26 09:46:53 Failed to execute common task.

2016-05-26 09:46:53 ErrorCode: 14031012, Error Detail: Failed to log in to file repository.

2016-05-26 09:46:53 Failed to execute common task.

2016-05-26 09:46:53 ErrorCode: 14031012, Error Detail: Failed to log in to file repository.

2016-05-26 09:46:53 Failed to execute common task.

2016-05-26 09:46:53 ErrorCode: 14031012, Error Detail: Failed to log in to file repository.

Could it be that since the current version of the Agent on the Thin Client is lower 4.4.3660.12652, the server is 4.6.3660.19313, it will not update the agent version becuase of the mismatch, but this template should update the agent version, I also made sure the "Write Filter" was disabled?

Is the another way to update the Agent Version on the Thin Client?  By running a file to install the updated version?

Thank you again for the help

[Jamie_Peterson]

Another note this afternoon I used the ThinCapture Application form Control Panel, on a Thin Client with Agent Version 4.6.3660.19313, on a Thumb Drive.

Completed successfuly, then used the thumb drive on the thin clinet with Agent version 4.4.3660.112652.

That image completed successfuly, checked the Agent version, which was now updated to Agent version 4.6.3660.19313, which is what the Respository has for the current Agent version.

Next used a Deploy Image Template from the server with HPDM, when the image completed successfully the Agent version reverted to 4.5.3660.19746 on the thin client.

But I got the thin client that we have been working on the error to complete an image deploy, by imaging with a thumb drive image that had the Agent version that matched the server.

The _Update Agent is not updating, and I am not sure where the different Agent version is coming from unless the image on the server that I deployed last has that version in it.

I hope this makes sence, and thank you for your help 

[Chen_HPDM]

"Failed to login" usually indicate that your HPDM Repository configuration is not correct. To confirm this, I need a screenshot of your Master Repository Editor dialog and the Controller.conf in ..\HP Device Manager\MasterRepositoryController\Controller.conf.

ThinCapture Application is local imaging application different from HP Device Manager. It doesn't work with HPDM Agent.

Your guessing should be correct - 4.5 Agent should be from the image you deployed.

[Jamie_Peterson]

Here are the screen shots you asked for, first the Master Repository Editior screen, then the successful test, then the Controller.conf.

I am taking over this position from a previous admin no longer with the company, the settings for the Master Repsoitory Editor - Repository Name (no change), Server Address IP (No Change)  FTP Protocol Settings and Shared Folder Protocol Settings used the previous Admin's Active Directory Credentials.  A new credential was created that was not tied to an individual, which works for the Shared Folder Settings, but does not work for the FTP Protocol Settings.

I turned off the FTP Protocol in Protocols ... , our understanding is it will work wih just the Shared Folder Protocol settings, and we don't have to troubleshoot the FTP connection, right?

I checked this server and all of the FTP services are running when I was trying to troubleshoot the FTP Protocol Settings 

Thank you for your help