Steps to troubleshoot acrobat specific issues on a Windows setup

This video walks through the process of troubleshooting acrobat specific issues on a Windows setup for AEM Forms PDFG.

Hello, everyone. In this video, we will show you the steps to troubleshoot Acrobat-specific issues on a Windows setup. Various third-party softwares are required for running the PDFG on your system.
The first step would be check whether the current version of Microsoft Office, Acrobat Reader and Java is installed on your system. After verifying that the correct version of the Acrobat Reader is installed, also check that the dialogs and the update service in Acrobat is also disabled. Now run the pdfg_config.bat file inside the pdfg_config folder, using admin privileges in the Command Prompt, running it as administrator. Also check whether the user is added to the PDFG from the PDFG UI. The next step will be to grant the a process-level token privilege in Windows. To do so, open the Run folder and type in gpedit.msc, and hit Enter. Navigate to Local Computer Policy, Computer Configuration, Windows Settings, Security Settings, Local Policies, User Rights Assignment, and edit the Replace a process token policy. Add the user to the Replace a process level token entry. Next, make sure that the Log On user is enabled to the Local System account inside the Properties of the JBoss Server in Services. Also check whether the user has read and write permissions from the temp folder inside the Windows directory and the temp folder inside PDFG in Adobe_Experience_Manager_Forms. Now open the pdfg_srt folder from the Adobe_Experience_Manager_Forms, and then open the reports folder, and open the SystemReadinessTool.html file. Inside this HTML file, check that Java, Acrobat Reader, and MS Office is clear of all errors. -