Printers are not being deleted/renamed - PowerShell Execution Policy

[SPLNTZ]

Hello,

I am working in Windows Server 2008r2 (Updated.)
I have installed the .net 3.5 in the features. I downloaded and installed the powershell version 3.0. I disabled easyprint driver in gpedit (user and computer.) edit: I also gave the printer manager Everyone Manage server permissions Added powershell executables to the printerceptor folder in the program files.
The tasks in task scheduler were created and the program does show all my drivers.
I am using us language ( (redirected (\d+))) and the test shows my printers with the redirect at the end.

In the options Current State is Ready and when I click Run it does go into running for a second and then goes back to ready. I did change the users on the tasks while trying to trouble shoot this to administrator of the local machine. Not sure where to go from here.

What am I doing wrong?

Thanks

SPLNTZ

[zniezelski]

The task must run under the system account because the owner is system on redirected printer security.

Does task scheduler show an error after it is run?

If it stops real quick when running without error, please try running the script the task runs manually and report output. Sounds like it is stopping unexpectedly.

Thanks,

Zach

Sent via the Samsung GALAXY S® 5, an AT&T 4G LTE smartphone

-------- Original message -------- From: SPLNTZ notifications@github.com Date: 7/5/2017 6:51 PM (GMT-05:00) To: zniezelski/Printerceptor Printerceptor@noreply.github.com Cc: Subscribed subscribed@noreply.github.com Subject: [zniezelski/Printerceptor] Printers are not being deleted/renamed (#16)

Hello,

I am working in Windows Server 2008r2 (Updated.) I have installed the .net 3.5 in the features. I downloaded and installed the powershell version 3.0. I disabled easyprint driver in gpedit (user and computer.) Added powershell executables to the printerceptor folder in the program files. The tasks in task scheduler were created and the program does show all my drivers. I am using us language ( (redirected (\d+))) and the test shows my printers with the redirect at the end.

In the options Current State is Ready and when I click Run it does go into running for a second and then goes back to ready. I did change the users on the tasks while trying to trouble shoot this to administrator of the local machine. Not sure where to go from here.

What am I doing wrong?

Thanks

SPLNTZ

[image]https://user-images.githubusercontent.com/29932722/27888186-95fe94ac-6199-11e7-87cd-d64e515fdadc.png

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHubhttps://github.com/zniezelski/Printerceptor/issues/16, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ANHvCOxVwhILAdpSn2lqObT06fA7s9nfks5sLBNqgaJpZM4OO9mH.

[SPLNTZ]

I set the task scheduler user to SYSTEM. It still did not run and gave me a code 0x1

In the image at the top it says it's the script isn't digitally signed so I'm betting that's where my problem lies.

Thanks

SPLNTZ

[zniezelski]

Splintz,

Your PowerShell is configured to only run digitally signed scripts.

Open powershell and run "set-ExecutionPolicy bypass" Then give it another try.

Zach

[SPLNTZ]

You sir are the man! Many thanks!!!!! You have solved a problem that I have been fighting with for years.

Thanks

SPLNTZ

[zniezelski]

Awesome! I'm glad it worked out for you. Let me know if you need further assistance.

Zach