Deploying Microsoft and third-party apps to client machines in a network is known as SCCM application deployment. Typically, the application deployment process is initiated from the SCCM Application Management tab, which can be found under the ‘Overview’ tab of the portal. Applications, licences, packages, and end-user requests can all be managed here by SCCM users. Expert offers support for SCCM application administration and, among its primary functions, third-party software deployment. The SCCM deployment process is detailed in this paper.
In this article, we will review the several SCCM deployment types compatible with application creation. Application installations using SCCM have been covered extensively in this blog. When distributing software to users and desktops, SCCM is the way to go. The most recent version of this piece, as of the time of writing, is SCCM 1902. There are several enhancements and new features in SCCM 1902 compared to earlier versions.
Essentials of SCCM Application Management
Let’s define a few terms associated with application deployments before moving on to deployment types. For those unfamiliar with SCCM and application packaging, you will see them frequently.
Please get started by getting SCCM Training, this will help you with the installation of files and instructions for deploying software are contained in an application. Since the programs can’t function without the OS and system utilities, they sit atop the system’s software.
Type of Application Deployment
At least one deployment type that is accessible to you is required for each program, as this type dictates the method of app installation. Using SCCM, you can configure various installation programs and content types for the same application using multiple deployment types. The following section will cover the different deployment types.
You can add requirements to ensure the application is targeted to the proper devices while planning to launch it. Consider the following scenario: Windows 7 and Windows 10 are coexisting at your company. You can only throw the app on Windows 10 devices. Therefore, you can limit the app’s installation to Windows 10 by setting prerequisites. Before Configuration Manager ensures that devices meet these prerequisites before installing the deployment type.
Any application or deployment type can use global conditions, a collection of specified criteria. You can build your global conditions or use the ones that come with Configuration Manager.
Practice Runs of Deployments
You can simulate deployment in Configuration Manager when you create an app. An application’s needs, detection technique, and dependencies can be tested through a simulated deployment. The customer only bothers to install the app after reporting the results. For more information on fake implementations, see this post.
How and Why the Deployment Occurred
The application can be installed or uninstalled during deployment. It is necessary to indicate if you wish to install or remove the application. Additionally, the goal of deployment should be considered. There are two possible deployment purposes: Available and Required.
You may find out if a device has an app installed or does not use detecting methods. If the detection method says it’s already installed, you won’t see Configuration Manager trying to install the app again.
With Supersedence, you may replace or upgrade current programs with ease. When an app’s version is up-to-date, you can return the old deployment type with the new one.
The client must install one or more deployment types from another application before installing this deployment type, and these dependencies specify them.
SCCM Application Deployment Types
Several choices are available to you when you build an application for deployment in SCCM, you can become a pro by taking a SSCM Training course. There are many options, but we only use some of them. The deployment type of Windows installer is prevalent. It is critical, though, to be familiar with the various application deployment types and their respective uses.
Configuration Manager supports the following application deployment types:
|A file that installs Windows.
|Windows app package
|Windows app package
|.appx, *.appxbundle, *.msix, *.msixbundle
|This rule applies to SCCM 1806 and up. The file types are Windows 10 app package (.msix) and app bundle (.msixbundle).
|Microsoft Application Virtualization 4
|App-V v4 package file
|Microsoft Application Virtualization 5
|Microsoft App-V v5 package file
|Windows Phone app package
|Windows Phone app package (Windows Phone Store)
|There are links to the PC Store app.
|App Package for iOS
|App Package for iOS from App Store
|Apple Store link to iOS app
|App Package for Android
|Choose this choice to give the app a link.
|App Package for Android on Google Play
|Choose a Google Play Store link for the game.
|Mac OS X
|To make an app for Mac, use this choice. It needs a.cmmac file, which can be made with the CMAppUtil tool.
|You can choose a link to a web application with this choice.
|Windows Installer through MDM
|You can make.msi apps and send them to Windows 10 devices if you choose this.
Which steps are necessary to install third-party apps in SCCM?
Deploying third-party software in SCCM requires several intermediate procedures to acquire and prepare the programme before deployment to systems, in contrast to the relatively uncomplicated application deployment in SCCM for Microsoft applications. Administrators must download programs, apply code signing certificates, and create application packages before deployment unless they employ additional tools that help with third-party application distribution.
Methods for Deploying SCCM Applications
Using an extensive library of 300+ programs prepared to be published to SCCM’s Application repository, third-party application deployment becomes much more accessible. Users can utilise the standard SCCM deployment when apps have been posted successfully. Establishing the application deployment SCCM settings before you begin is critical; we’ll walk you through it in detail below. After users have configured with SCCM, they can move on to creating application binaries for deployment.
Configuring the SCCM parameters
Specifying the SCCM settings in the dashboard before developing binaries of third-party programs is essential. This will ensure that the application binaries are immediately synchronised to your SCCM server. If you want to accomplish that,
- Go to the Admin tab and look for SCCM settings.
- In this section, you must specify the name and IP address of the Microsoft SCCM server that needs the binary details updated.
- Afterwards, enter the credentials of the SCCM administrator.
- Configuring the Parameters for Application Management
Configuring the network share path for all the software binaries in the Application Management settings is the second prerequisite to establishing third-party applications.
- Under the Admin tab, you should see Application Management settings. The path to the network share where all the software binaries will be kept should be mentioned here.
- The provided network path requires elevated read/write access, so please be aware.
- After that, establish a deadline, say 60 or 90 days from now, by which all out-of-date application binaries must be removed from the repository.
- Using the interface to build binaries for external applications
- After all the necessary conditions are satisfied, go to the console and select the Application Management option. You can see a complete list of all the third-party apps it is compatible with here.
- Then, under SCCM, find the third-party program you need and click the Create Application button.
- The SCCM console will generate the binaries for third-party applications when an alert message stating “Application creation in progress” is displayed.
Release of third-party apps through the SCCM interface
You’ll see all the third-party apps made with the console on the left side of the Software Library tree. Just look for the Applications tab. If you want to use Microsoft SCCM to install a third-party program on your endpoints,
- Choose Deploy from the context menu of the third-party software you want to install.
- The “Deploy Software Wizard” will pop up once you click the Deploy button. To proceed with the application’s deployment, choose the collection that needs it and click Next.
- The “content” page will now appear; you must confirm the application’s distribution point here.
- After you’ve chosen the distribution point, go to “Deployment settings” to change the application’s status from Available to Required. Next, once you’ve made your selection, press the button.
- Select the time you would like the deployment to occur under the Scheduling page, then click Next.
- The configuration of the update wizard and user notifications can be found in the “User Experience” section.
- Go to “Alerts” when customising the user experience. This is where you’ll set the timetable for when the deployment alerts will go out.
- When you’re done, a summary page will appear, showing all your chosen settings.
- The third-party program of your choice will be installed on the computers you specified when you clicked Next.
Finally, System Centre Configuration Manager (SCCM) deployment types simplify software management and distribution. Organisations can fulfil user requests and system configurations with flexible deployment types. SCCM streamlines programme, package, and software upgrade delivery. Granular deployment parameters allow SCCM administrators to modify software installs. This comprehensive system centralises management, security, and resource optimisation. Since SCCM streamlines software deployment, deployment types’ diversity and durability make IT infrastructure more agile and responsive, enabling more productive and safe computing.
Madhavi Gundavajyala is a Content contributor at Mindmajix.com. She is passionate about writing articles and blogs on trending technologies, project management topics. She is well-versed on AI & Machine Learning, Big data, IoT, Blockchain, STLC, Java, Python, Apache technologies, Databases.