If powershell.exe is blocked on client by carbon black sccm deployments fails . Why ? RRS feed

  • Question

  • In my organization carbon black has blocked powershell.exe and due to which CcmExec.exe and deployment of application fails. What is the reason can any one help ? is there any official Microsoft documents which shows the Powershell and sccm client dependence.

    Thanks in advance for your help

    Friday, January 17, 2020 11:15 AM


All replies

  • There is no dependence on PowerShell for deployments. Something else is going on.

    Garth Jones

    Blog: Old Blog:

    Twitter: @GarthMJ Book: System Center Configuration Manager Reporting Unleashed

    • Marked as answer by HusainC Tuesday, January 21, 2020 6:55 AM
    Friday, January 17, 2020 12:10 PM
  • Hi,

    Do you mean you are using SCCM deploy the powershell and blocked by carbon black?
    There is no dependency between powershell and sccm client, maybe we can consult carbon black support for help.


    Please remember to mark the replies as answers if they help.

    If you have feedback for TechNet Subscriber Support, contact

    Monday, January 20, 2020 6:45 AM
  • Ok I will check as it is very strange and need deep analysis
    Tuesday, January 21, 2020 6:55 AM
  • Thanks Allen,

    Yes we can raise a case with carbon black but I only wanted to know if SCCM deployments may invoke powershell in background and hence getting blocked.



    Tuesday, January 21, 2020 6:57 AM
  • Thanks for your prompt help Garth.



    Tuesday, January 21, 2020 6:57 AM
  • Do you mean App-v user targeted deployments fail?

    I was about to post a question about this as the security team want powershell blocked for users but I deploy App-v to users. When CM deploys it adds (add-appvclientpackage) the package as system but when it publishes (publish-appvclientpackage) it does this in a user context then fails.

    Any help would be great too

    • Edited by rtimmsie Wednesday, February 19, 2020 3:05 PM
    Wednesday, February 19, 2020 2:59 PM