Jump to content

MikeLee5309

Members
  • Posts

    2
  • Joined

  • Last visited

Everything posted by MikeLee5309

  1. Upon migrating our organization to a new MEDCOI network, many if not all of our customer have experienced an error when attempting to digitally sign any adobe document in Adobe Acrobat DC Pro. The popup states: An error occurred when attempting to sign Adobe Acrobat DC pro. There is no forward motion for the customer, and the signing process is over once they click Ok. The Solution: As a computer admin, sign-in as the local computer admin, login with admin credentials, and open the registry (regedit). Open Local Machine, then go into System, then currentcontrolset, then control, then Lsa, then FIPSAlgorithymPolicy. Set the value to 0 (was 1) and Ok. (local machine\syste\currentcontrolset\control\Lsa\FIPSAlgorithymPolicy value = 0. Ok) At this point, close out of the Registry, and sign-out and all users will be able to sign Adobe .pdf documents as expected. Unfortunately, we have had to do this with all of our newly migrated computers due to local/security policy. I hope that this helps. Regards
  2. Recently I was dispatched to a customer’s office for a prompting issue when just simply beginning to edit a Microsoft word document. It was a credential popup where the customer basically had to enter a user name and password to keep the ball rolling. Nothing worked, and ultimately the customer got to the point where the word document became frozen, and they had to bring up the task manager to close out of the application. So basically, the use of the Microsoft product was forcing my customer to enter credentials to continue to use it. The popup for her credentials was: Connecting to Proxy Server for omextemplates.content.office.net. And while we have credentials for logging into our computers, email, websites etc, there really seemed to be no need to login through any proxy server to use any Microsoft product including Word. I remembered a setting that I thought might prove to be the solution to the issue. I tested it on my own work computer and quickly went around the corner to implement on the customer’s computer. This is the fix (and it works in any office product document): So for this discussion, in Word: Click on the File tab, then click on Options. Next, Click on Trust Center Then on Trust Center Settings Click on Privacy UN-check the box labeled: Let Office Connect to online services from Microsoft to provide functionality that’s relevant to our usage and preferences. That’s it. Click Ok on the bottom then Ok again.
×
×
  • Create New...