PowerShell Start-Process Print Not Working on Windows Server 2019

[IntenseDeveloper]

I'm working on an automation job using UC4 (Automic) to print PDFs from a directory.

The automation tool logs into the Windows Server 2019 virtual machine with a local admin level service account and feeds the PowerShell script to the remote server for execution.

I am trying to figure why the 'Start-proces '.\path_to_files.pdf' -Verb Print' cmdlet does not work when executed via automation tool, but works when I execute the cmdlet as a local admin user on the server?  When executing with the automation tool, the print job does not get added to the printer spooler queue.

Could it be due to the "Enhanced Security" feature? I am reading that Acrobat does not allow "remote printing" if this feature is enabled--is this how it works?

[Bernd Alheit]

At what user does you use this?

[IntenseDeveloper]

The automation tool has its own service account.  Using that account, I am able to execute the cmdlet manually via PowerShell, but the same command does not work when run with the automation tool.

[IntenseDeveloper · Accepted solution]

I was able to resolve this problem by tinkering with the settings. Since our server will be dedicated for this printing automation process, disabling the security features and protected mode fixed my issue.

Enabling "Protected Mode" by default will not allow any external processes (PowerShell cmdlets) from interacting with Acrobat.

[E_Zanon]

Hi there, Just wondering, did you have to have the service account logged on to the server to do this or could you ran it as scheduled task? I can print via command line  when the service account is logged on to the server but the same script fails to run as a scheduled task and the user is not logged on.

[AnandSri]

Hello,

I hope you're doing well, and we apologize for the delayed response and the trouble.

Is it still happening with the latest version of Acrobat Reader 24.005.20421 Optional update, Feb 24, 2025? What happens when you disable the Protected Mode for testing purposes? Try disabling the Protected Mode, restart the app, and check.

Let us know how it goes.

Thanks,

Anand Sri.