As a side note here, the script gets a random name and you can fully see the patch and name is the logs.
J ________________________________ From: [email protected] <[email protected]> on behalf of Nash Pherson <[email protected]> Sent: Tuesday, December 2, 2014 11:21 AM To: [email protected] Subject: [mssms] RE: Compliance script compiled locally on workstation? Bah... Sherry beat me to it but my email didn't update. It is indeed C:\windows\ccm\systemtemp instead of \temp. From: [email protected] [mailto:[email protected]] On Behalf Of Nash Pherson Sent: Tuesday, December 2, 2014 11:01 AM To: [email protected] Subject: [mssms] RE: Compliance script compiled locally on workstation? I'm not positive, but I think it is c:\windows\ccm\temp... I saw it in the logs last week while troubleshooting a powershell detection method last week. I hope that helps, Nash From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Daniel Ratliff Sent: Tuesday, December 2, 2014 9:34 AM To: [email protected]<mailto:[email protected]> Subject: [mssms] Compliance script compiled locally on workstation? At MMS 2014, one of the presentations mentioned a location on a workstation where a PowerShell compliance script is compiled and sits on the workstation while running, but is removed when complete. Does anyone know this location? I think it was C:\windows\....something or other. Daniel Ratliff The information transmitted is intended only for the person or entity to which it is addressed and may contain CONFIDENTIAL material. If you receive this material/information in error, please contact the sender and delete or destroy the material/information.
