Device Managemeny Gateway failed to pass the authentication

[URMyOnlyHP]

Hello, 

We are upgrading from HPDM 4.6 to 4.7 and the server's keystore file was deleted in the process. As a result we get this log message every time we try to send a task to one of our machines:

"Agent refused the task because the Device Management Gateway failed to pass the authentication."

I deleted the two key files in C:\Windows\xpeagent on one of the machines and that seems to have resolved the issue -- for that machine. Repeating this process for ALL of our machines would be a daunting task.

Is there another way to resync these devices with the server or are we out of luck?

If we do have to touch each machine individually, does anyone have any tips or scripts for speeding up the process?

Thanks in advance for any advice you can offer!

[Chen_HPDM]

Well, if you still remember the key, you can use Tools -> Authentication Management -> Key Management-> Update Current Key to set the original key.

If you don't remember the key, probably you have to stop the DM Gateway and wait until key expires - if the expiration date was not set too long.

BTW, the key value was stored in DB instead of your file system, If you happen to backup the old DB, you can simply copy the string to new DB. Find the key in the dm_key table.

If you're out of luck with above options but have big number of units, you can try contacting the support team in your region for key decrytion.  key1.key on your unit is required and usually this takes time for processing.

[URMyOnlyHP]

Thanks for your reply! I have tried updating the key but that just appears to create a new key. I still get the same "gateway failed to pass the authentication" message when I try to send a task. 

The key was set by a previous employee so we don't know the keystore password nor the expiration date. We reached out to him to see if he remembered the password but he did not have it. 

Where is the database stored? I believe we were backing up our templates and images but that's it (well along with the original ks file). We use the Postgre database rather than SQL server. 

[Chen_HPDM]

The DB file of Postgre locate in  ..\HP Device Manager\Server\pgsql\data

If you were using the native Backup & Restore Tool of HPDM, the entire folder should have been backed up .

Also you need to know the default postgreSQL password(check your priviate messge box in Forum) if you never changed it.

[URMyOnlyHP]

Thank you so much for your help. It looks like we do have the old database but I'm not sure how to load it in to a new postgeSQL database. I'll look in to that. In the meantime we are going to manually delete the key files from our machines. 

[Chen_HPDM]

A short message might help you look into the postgre data

1. Download the management Console from postgresql.org

2. Install the mangement Console

3. Connect to the database with the same credential you created it

4. Find the specific table

5. Copy the key/value from the old DB to new one.

[URMyOnlyHP · Accepted solution]

I can't figure out how to import the database in to the current version of the postgre server client and I've spent a lot of time on this project already. I don't have the password to the orginal database so I'd probably just be stuck again, anyway. We're going to go with renaming the key files on our client machines for the time being.  Thanks for your help!