Fully Qualified Path to PowerShell.exe in Scheduled Jobs?
Read OriginalThis technical article addresses a security concern in Windows PowerShell scheduled jobs, where using just 'powershell.exe' could allow a malicious executable to be intercepted. It provides a step-by-step guide and code examples to modify the scheduled job's action to use the fully qualified path (C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe) via PowerShell commands, avoiding the GUI.
Comments
No comments yet
Be the first to share your thoughts!
Browser Extension
Get instant access to AllDevBlogs from your browser
Top of the Week
1
The Beautiful Web
Jens Oliver Meiert
•
2 votes
2
When your coding agent doesn’t understand your project, you’ll get junk
Benjamin Cane
•
1 votes
3
LLM Use in the Python Source Code
Miguel Grinberg
•
1 votes
4
Wagon’s algorithm in Python
John D. Cook
•
1 votes
5
An example conversation with Claude Code
Dumm Zeuch
•
1 votes