Unless your bad command line is pointing to a script file, there is no script file, it is just the command line execution. If it is pointing to it, you should see the path in the command line.
Or I'm not understanding you.
Sorry maybe i'm not good at explaining.
Ok here the detail.
I have created a batch file called "Power.bat" in C:\Users\Username\Desktop\
In this script file :
####SOMESTUFF#####
Powershell -encode BASE64STUFFF
####SOMESTUFF#####
When I execute this script, i'm able to get an event based on the Powershell commandline but I'm not able to locate this script from ePO.
From Exploit Prevention or MAR ProcessHIstory i'm not able to find "Power.bat"
(same story if the file is .ps1)
ok.. I got you, I think.
If you double click it, then you will see what generates from it I think, but not the file name. If you call it at a command prompt, you should see the script file called.
Ultimately, you will see every execution that the bat causes, but you wouldn't see the bat itself as there is no command line calling it, I think.
Dave
New to the forums or need help finding your way around the forums? There's a whole hub of community resources to help you.
Thousands of customers use our Community for peer-to-peer and expert product support. Enjoy these benefits with a free membership: