Deploy PowerShell Script on SCCM1802


  • Hi There,

    The SCCM 2012 has released an update 1802, that has enabled Script Deployment. After creating a script on SCCM, I am unable to deploy the script to an end device. The script is stuck on "Creating client jobs". Any advice would be most appreciated.



    Wednesday, April 18, 2018 1:02 AM

All replies

  • > "The SCCM 2012 has released an update 1802"

    No there isn't. 1802 is not a version of ConfigMgr/SCCM 2012. ConfigMgr 2012 is an older product and has been replaced by ConfigMgr which is often referred to as ConfigMgr Current Branch (CB).

    You'll have to be much more specific in describing your issue though. What exactly, step by step did you do? Where exactly are you getting the error message indicated?

    Jason | | @jasonsandys

    • Proposed as answer by Lorry Luo Friday, May 4, 2018 7:16 AM
    Wednesday, April 18, 2018 1:26 AM
  • Hi,

    Examine the SMS_PhasedDeployment.log -->Log file for phased deployments, a pre-release feature starting in Configuration Manager version 1802. See

    Best Regards,


    Please remember to mark the replies as answers if they help. If you have feedback for TechNet Subscriber Support, contact

    Wednesday, April 18, 2018 3:23 AM
  • Microsoft System Center Configuration Manager

    Version 1802

    Console Version : 5, 1802

    MDM - Intune + SCCM Hybrid Environment


    * Updated SCCM to 1802

    *Turned on Feature Updates - Create and Run Scripts

    *Created a PowerShell Script

    *Approved the Script

    *Assigned Script to a Device Collection.

    After assigning the script, the Deployment never completes.

    Thank you for the Response
    Wednesday, April 18, 2018 6:12 AM
  • Are the systems in the collection properly reporting to the site via client notification; i.e., do they have green check-marks next to them?

    Is your MP healthy?

    Jason | | @jasonsandys

    Wednesday, April 18, 2018 4:10 PM
  • Hi Jason,

    Yes, the systems are healthy. I am able to deploy APPs, Policies and updates.

    Any ideas why only creating and deploying a script to a collection does not work?

    Thursday, April 19, 2018 2:29 AM
  • That doesn't really answer my first question though: do the systems have a green checkbox next to them -- this isn't an indicator of health?

    Have you reviewed the script status node in the monitoring workspace?

    Jason | | @jasonsandys

    Thursday, April 19, 2018 2:47 AM
  • Hi,

    You have not update for a long time. 

    Have you solved this problem? Can you share the solutions to help more people?

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

    Best Regards,


    Please remember to mark the replies as answers if they help. If you have feedback for TechNet Subscriber Support, contact

    Monday, April 30, 2018 8:45 AM
  • Hi,

    When the client computer met the following conditions then the script deployment will run successfully.

    • The client device must be running PowerShell version 3.0, or later;
    • The Configuration Manager clients must be running client version 1706, or later



    Thursday, July 5, 2018 4:41 PM
  • This pointed me in the correct direction.  Thank you.
    Thursday, December 13, 2018 1:30 AM