We have a brand new look! Take a tour with us and explore the latest updates on Adobe Support Community.
I have 2 questions please. On my old laptop (Dell Vostro with Windows 7) I have Acrobat X Standard which I used to merge and digitally sign pdfs. I want to buy the most inexpensive software which will allow me to do the same on my new laptop (Dell Inspiron with Widows 10). So my questions are:
(1) Which Adobe software should I buy
(2) Where can I find and how can I transfer the signatures from the old to the new laptops. I had an image of my signature in cursive writing which I used alongside the digital signature.
Can I have help please with this query?
(1) Acrobat DC Standard
Thank you Bernd.
2) Go to Edit - Preferences - Signatures - Identities & Trusted Certificates, select your signature profiles and then click on Export.
Save them to a data file. Transfer that file to the other computer, and then go to the same location there, this time selecting Add ID - Existing digital ID - From a file. Select the file you created before and you're done.
I am transitioning to a new MacBook. I have saved the exported Digital ID in all 3 available formats (.cer .fdf and .p7c) but the Add ID process on the new Macbook will not recognize/select any of those formats. What am I missing?
You must use the files with .p12 or .pfx extension.
Adobe Reader DC won't export as .p12 or .pfx
It exports as .p7c
This is so frustrating. Why does adobe reader export in a different format to the import in DC?
You have exported the public key.
The answer marked as correct here only caused frustration, and I discovered it's easier to either find the correct file on your original laptop or just create a new signature.
As others noted, Adobe only lets you export in .cer, .fdf or .p7c formats, but you need .p12 or .pfx to send it to your new computer. If you originally created the signature as a PKCS#12 file, then it should be easy to find that .pfx file in this location on Windows:
Once that file is transferred, then use the Add ID function
In my case using Reader DC, the signature was originally created through the Windows Certificate Store, which left a file with no extension called "reader_fss_signature_initials" in the same location above. I could not figure out any way to export this file as a .pfx, even trying to reach it through the Windows certificate manager. After spending far too much time on this, it was easier to just create a new signature.