SCCM 1802 phased deployment was introduced as a pre-release feature and was supporting only Task Sequence deployments. Beginning with SCCM 1806, it’s no longer a pre-release feature and it now supports application deployments. If you’re not familiar with Phased deployments, they allow orchestrating a software deployment based on certain criteria and condition. For example, you could use it to deploy an application to a pilot collection and then automatically continue the deployment based on success criteria. SCCM Application Phased Deployment Creation For now, it’s only possible to create a 2 phase deployment. Let’s go ahead and deploy 7zip : In Software Library / Application Management / Applications Right-click an existing application and select Create Phased Deployment On the General page, give the phased deployment a Name, Description and select Automatically create a default two-phase deployment Click Browse and select a target collection for the First Collection and Second Collection On the Settings page, … Read More
Deploy PowerShell Scripts using SCCM 1706
Beginning with SCCM 1706, you can now run and deploy Powershell script from the SCCM console. In addition, all directly from the SCCM console you can: edit your scripts, import existing scripts, approved or deny scripts, run script on specific collections and examine the scripts results. This can be useful to run a script quickly without the burden of creating a package or an application. Unlike standard deployments, when you deploy scripts, they are run almost immediately using Client Operations. This feature is still in pre-release version and needs to be enabled manually before using it. Prerequisites for SCCM Deploy PowerShell Script Before using scripts on your clients you need : SCCM 1706 Create and Run scripts pre-release features enabled Targeted clients must have client version 1706+ Clients must be running PowerShell v3.0+ Have the necessary SCCM permissions Enable Create and Run Scripts Feature Open the SCCM Console Go to your Administration / … Read More
Enable and Configure SCCM Install Behavior for Applications
SCCM 1702 introduce a new feature to check and close executable files before application installation. This could be useful if you need to close a certain process before an SCCM application installation. One example would be some Adobe products that need Internet Explorer to be closed before installation. Before 1702 there was no way to do this using a built-in option in SCCM. A popular User Voice item was delivered as a pre-release feature in SCCM 1702 which is called SCCM install behavior for applications. We will show you how to enable and configure the Install Behavior tab in an application deployment type and show you the different behaviors based on the deployment properties. Enable SCCM Install Behavior for Applications Before you can use the Install Behavior feature, you must enable it as it’s still a pre-release feature: In the SCCM Console, go to Administration \ Site Configuration \ Sites Click on the … Read More