# SCCM Administration Guide # Integration SCCM Connector empowers Apptimized customers to: - import software estate from SCCM server to Apptimized project portfolio; - create an application in SCCM Console; - add the deployment type to application with automatic media transfer; - start the deployment of an application. SCCM Connector Integration saves time and provides instant deployment of SCCM packages without the need to leave Apptimized. ### Requirements and limitations The following prerequisites apply for SCCM connector: - endpoint PC or VM with access to the 443 port of app.apptimized.com host; - endpoint membership in Active Directory domain; - Microsoft Windows Desktop (Windows 7 and above) or Server OS (Windows Server 2012 R2 and above) with installed .NET Framework 4.6.1; - write permissions for network share with packages source media for automatic media transfer; - administrator role for SCCM or permissions to create applications, deployment types, and deployments; - installed SCCM Administrator Console with a connection to the SCCM server. ### Integration configuration with Apptimized Initial integration to Apptimized requires a one-time configuration of SCCM Connector settings. It is required to establish a connection to the remote SCCM Environment. It is possible to override preconfigured settings during the creation of an object in SCCM if needed, so they take precedence over the template of settings defined during the initial setup. ### Connection and default configuration ##### SCCM Environment Apptimized enables a user to set up SCCM environments to perform with SCCM connector deployment integration. Each SCCM Environment is configured separately and can be used for any purpose. The option to create SCCM environment is available for project administrators under **Settings** in the project menu > **Integratio**n section > **SCCM** > New SCCM Environment [![SCCM_24_01-2.png](https://docs.apptimized.com/uploads/images/gallery/2021-12/scaled-1680-/dgumBva6jAdJeXWz-SCCM_24_01-2.png)](https://docs.apptimized.com/uploads/images/gallery/2021-12/dgumBva6jAdJeXWz-SCCM_24_01-2.png) Apptimized shows the following screen when successful: [![sccm_25_03.png](https://docs.apptimized.com/uploads/images/gallery/2021-12/scaled-1680-/sAlTB1mia6aGUWMT-sccm_25_03.png)](https://docs.apptimized.com/uploads/images/gallery/2021-12/sAlTB1mia6aGUWMT-sccm_25_03.png) THe option to set the name of SCCM Environment is available under **SCCM Environment name** field. The option to finish the creation process is available after setting the **SCCM Environment** name > **Create** button. Apptimized shows the created environment when successful: [![sccm_26_01.png](https://docs.apptimized.com/uploads/images/gallery/2021-12/scaled-1680-/VgaWvFRzkrFT0Zec-sccm_26_01.png)](https://docs.apptimized.com/uploads/images/gallery/2021-12/VgaWvFRzkrFT0Zec-sccm_26_01.png) ##### General settings The one-time configuration is available for project administrators under **Settings** in the project menu > **Integration** section > **SCCM** > **General**. [![sccm_11_03.png](https://docs.apptimized.com/uploads/images/gallery/2021-12/scaled-1680-/PMQVtYvFOKHNj8Iv-sccm_11_03.png)](https://docs.apptimized.com/uploads/images/gallery/2021-12/PMQVtYvFOKHNj8Iv-sccm_11_03.png) SCCM Connector becomes active when switched on and once the settings are completed. [![SCCMSettingsTemplate.png](https://docs.apptimized.com/uploads/images/gallery/2024-03/scaled-1680-/sccmsettingstemplate.png)](https://docs.apptimized.com/uploads/images/gallery/2024-03/sccmsettingstemplate.png) Table 1. General settings
**Settings** **Details**
Environment nameThe Environment name is the name of SCCM environment the SCCM connector operates in.
Remote IDThe remote ID is a unique identifier generated automatically for every project during its creation. Remote ID provides customer identification. The Remote ID is used during SCCM connector installation on customer's environment.
Site codeSite codes and site names identify sites in a Configuration Manager hierarchy. Configuration Manager Setup prompts for a site code and site name for the central administration site, and each primary site and secondary site installation. [Learn more.](https://docs.microsoft.com/en-us/configmgr/core/servers/deploy/install/prepare-to-install-sites)
DML LocationSecondary deployment target which packaged files will be copied to during the SCCM push in addition to the deployment type content library.
Name of the default distribution groupIndicates the default group of users or devices where to Install applications. This setting corresponds to the term "**Distribution point group**" in the SCCM admin console.
Collection typeIndicates the type of collection where apps should be installed. The following types are: - Device - User
Collection nameIndicates the collection of devices where to install applications. This setting corresponds to the term "**Collection name**" in the SCCM admin console.
Folder for application in SCCM ConsoleThis field is optional and can stay blank. If provided, overrides the default “**Application**” folder in SCCM Administrator Console as a target path for created application records.

Example: **Testfolder1\\testFolder2** or **Testfolder1\\testfolder2\\testfolder3**.

Install or uninstall the application This setting indicates whether a task sequence action in SCCM Console can install the application. **Yes** or **No** options are available.
Deploy the purpose of the installation This option specifies whether the application deployment can is mandatory or optional. **Available** or **Required** options are available.
Application display nameThe name of the application to be shown in SCCM Console.
Localized application nameSpecifies the application name for the English(US) default language.
Administrator comments This optional field indicates the optional content with the dynamic variables can be filled by the user.
If the endpoint connects to the internet via the proxy server, configure the connection by turning on **Enable proxy** and selecting **Use default windows credentials** or providing credentials in **Username** and **Password fields**. [![sccm_06_02.png](https://docs.apptimized.com/uploads/images/gallery/2021-07/scaled-1680-/NoOdXcV7JwJo6jTW-sccm_06_02.png)](https://docs.apptimized.com/uploads/images/gallery/2021-07/NoOdXcV7JwJo6jTW-sccm_06_02.png) The option to use a proxy server whiсh is configured o VM where SCCM connector will be running is available under **Use default Windows proxy server** switch. [![sccm_06_03.png](https://docs.apptimized.com/uploads/images/gallery/2021-07/scaled-1680-/EoSN2qvpQliEtq70-sccm_06_03.png)](https://docs.apptimized.com/uploads/images/gallery/2021-07/EoSN2qvpQliEtq70-sccm_06_03.png)

Note. If **Use default Windows proxy server** switched to **Yes**, the **Proxy address** field disappears.

The option to set a **Proxy address** is available under the **Proxy address** field. [![sccm_06_04.png](https://docs.apptimized.com/uploads/images/gallery/2021-07/scaled-1680-/IBjyUv2bDjZ01rw5-sccm_06_04.png)](https://docs.apptimized.com/uploads/images/gallery/2021-07/IBjyUv2bDjZ01rw5-sccm_06_04.png) ##### Deployment types templates settings This setting enables a user to implement multiple deployment types by creating multiple deployment templates within one project. The option to enable SCCM deployment templates becomes active when all required fields in the SCCM general tab are filled in. [![sccm_03_01.png](https://docs.apptimized.com/uploads/images/gallery/2021-11/scaled-1680-/fRU6q5aEMllwCKLk-sccm_03_01.png)](https://docs.apptimized.com/uploads/images/gallery/2021-11/fRU6q5aEMllwCKLk-sccm_03_01.png) The deployment types sections is displayed in 2 blocks: - Information block – this block contains detailed information about the Deployment templates; - Actions block – this block provides the options to operate with the deployment templates. [![sccm_05_01.png](https://docs.apptimized.com/uploads/images/gallery/2021-11/scaled-1680-/8XLAffjECI2IyzVe-sccm_05_01.png)](https://docs.apptimized.com/uploads/images/gallery/2021-11/8XLAffjECI2IyzVe-sccm_05_01.png) Deployment type templates data is grouped into the following categories:
**Сategory ** **Description **
Template name The field indicates the template name to help a user to identify templates in Apptimized portal.
Name This field indicates the name of a deployment type.
Technology title This field indicates the type of template installation.
Source folder This field indicates the path to the location of the package source.
Path to executable This field indicates the path to the location of the package source executable file.
[![sccm_06_01.png](https://docs.apptimized.com/uploads/images/gallery/2021-11/scaled-1680-/8KVk2f4tdngNbZg9-sccm_06_01.png)](https://docs.apptimized.com/uploads/images/gallery/2021-11/8KVk2f4tdngNbZg9-sccm_06_01.png) Users actions are grouped into the following categories: - Edit - enables a user to enter edit Deployment type template; - Delete - allows a user to delete the Deployment type template. [![sccm_07_01.png](https://docs.apptimized.com/uploads/images/gallery/2021-11/scaled-1680-/Odr4obu21F3iD28f-sccm_07_01.png)](https://docs.apptimized.com/uploads/images/gallery/2021-11/Odr4obu21F3iD28f-sccm_07_01.png) The option to Create new deployment type is available under **Create Deployment type **button [![sccm_04_01.png](https://docs.apptimized.com/uploads/images/gallery/2021-11/scaled-1680-/1GIHfICvhbO4PvHk-sccm_04_01.png)](https://docs.apptimized.com/uploads/images/gallery/2021-11/1GIHfICvhbO4PvHk-sccm_04_01.png) Apptimized shows the following screen when successful: [![Deployment type.png](https://docs.apptimized.com/uploads/images/gallery/2024-03/scaled-1680-/deployment-type.png)](https://docs.apptimized.com/uploads/images/gallery/2024-03/deployment-type.png) The set of SCCM deployment template settings depends on the chosen installer type. Table 3. Deployment types template settings
**Settings** **Description** **Availability of settings depending on the Installer type**
MSIScript Installer AppV
Microsoft Application Virtualization 4 Microsoft Application Virtualization 5
Deployment type template name The field indicates the template name to help a user to identify templates in Apptimized portal. The default value is **Deployment type template name \[number\]**. This field is required. ++++
Deployment type nameThis field indicates the name of a deployment type. It is implemented during SCCM application deployment process and is sent to SCCM server. A user can set the **Deployment type name** manually or use the following dynamic variables: [![sccm_changes_03.PNG](https://docs.apptimized.com/uploads/images/gallery/2020-07/scaled-1680-/HaMcsDfHOvB1BG7s-sccm_changes_03.PNG)](https://docs.apptimized.com/uploads/images/gallery/2020-07/HaMcsDfHOvB1BG7s-sccm_changes_03.PNG) This field is required. ++++
Path to the sourceThis field indicates the path to the location of the package source. SCCM deployment template automatically generated this field. This field is required. ++++
Path to the executableThis field indicates the path to the location of the package source executable file. A user can set the **Path to the executable** manually or use the following dynamic variables: [![image-1612449200206.png](https://docs.apptimized.com/uploads/images/gallery/2021-02/scaled-1680-/e1EgqwCesELYfLQ1-image-1612449200206.png)](https://docs.apptimized.com/uploads/images/gallery/2021-02/e1EgqwCesELYfLQ1-image-1612449200206.png) This field is required. ++++
Copy source to file shareThis option allows to copy to the folder, the location of which was defined in field **Place for storing sources** in the **General** SCCM settings tab. ++++
Installer typeThis setting indicates the type of installer to use. The following installer types are available: - [MSI (Microsoft Installer)](https://docs.microsoft.com/en-us/windows/win32/msi/about-windows-installer); - [Script Installer](https://docs.microsoft.com/en-us/powershell/module/configurationmanager/add-cmdeploymenttype?view=sccm-ps#-scriptinstaller); - [AppV (Microsoft Application Virtualization 4)](https://docs.microsoft.com/en-us/microsoft-desktop-optimization-pack/appv-v4/); - [AppV (Microsoft Application Virtualization 5)](https://docs.microsoft.com/en-us/microsoft-desktop-optimization-pack/appv-v5/). The default value is **Script Installer**.++++
Script type for the detection methodThis setting indicates the type of script content of the [detection method](https://docs.microsoft.com/en-us/configmgr/apps/deploy-use/create-applications#bkmk_dt-detect). The following script types for detection method are available: - [Powershell](https://docs.microsoft.com/en-us/powershell/scripting/overview?view=powershell-7); - [VB Script](https://docs.microsoft.com/en-us/previous-versions/sx7b3k7y%28v%3dvs.85%29); - [JScript](https://docs.microsoft.com/en-us/previous-versions/hbxc2t98(v=vs.85)). The default value is **Powershell**. +
Detection script content template This field specifies the script template of the detection method. It is possible to provide a custom template with mandatory variables in square brackets, indicating them in any order and quantity. The Connector replaces these variables with specific values during the deployment to SCCM. The default value is **Get-ItemProperty "HKLM:Software\\\[PackageName\]\\** **\[Manufacturer\]\\\[ApplicationName\]\\\[ApplicationVersion\]" -ErrorAction SilentlyContinue | Where { $\_.IsInstalled -eq 1 }** +
Persist content in the client cache This setting indicates the necessity to upload the application or package source to the client's machine or device cache. **Yes** or **No** options are available. The default value is **No**. +
Installation command with parametersThis setting indicates the command to run during the package installation. The default value for the Script Installer is **Deploy-Application.exe -DeploymentType Install** The default value for the MSI Package is **msiexec /i "\\\\atd-dist01\\Public\\CM\\DTeam\\FeatureData\\OSD\\Tbreck\\Setup1.msi" or msiexec /i "\\\\atd-dist01\\Public\\CM\\DTeam\\FeatureData\\OSD\\Tbreck\\Setup1.msi" /qn**++
Uninstallation command with parameters This setting indicates the command to run during the package uninstallation. The default value is **Deploy-Application.exe -DeploymentType Uninstall** +
Installation context This option defines the context of the package installation. The following installation contexts are available: - install for the system; - install for a user; - install for the system if a resource is a device otherwise install for the user. The default value is **Install for the system**. This option corresponds to the term **Installation behaviour** in the SCCM admin console. +
Should the user be logged on or not This option defines the required user state when the installation starts. The following options are available: - only when no users are in the system; - only when a user logs in; - whether or not users are active in the system. The default value is **Whether or not users are active in the system**. This option corresponds to the term **Logon requirement** in the SCCM admin console. +
Installation visibility for the userThis option defines the installation process visibility. The following options are available: - normal; - minimized; - maximized; - hidden. The default value is **Normal**. This option corresponds to the term **Installation program visibility** in the SCCM admin console. +
Requires user interactionThis setting indicates if the user can be involved in the installation or uninstallation process. **Yes** or **No** options are available. The default value is **No**. +
Identify deployment type information from a package fileThis setting indicates the option of a manual (**Yes**) or automatic (**No**) deployment type information identification. The default value is **No**.+ ++
The file where to get informationThis field indicates the file with the deployment type information. The following options are available: - MSI file for MsiInstaller; - XML manifest for AppvInstaller; - AppV file for App5xInstaller. An installation type defines default value.+ ++
What to do on a slow networkThis option specifies actions with package sources in case of a slow network. Following options are available: - do nothing; - download; - download content for streaming. The default value is **Download**.++++
Maximum installation time (minutes)This option indicates the maximum duration per installation in minutes. The default value is **120**.++++
Estimated installation time by default (minutes)This option indicates the estimated duration per installation in minutes. The default value is 0.++++
Run installation program as a 32-bit process on 64-bit clientThis setting forces the installer to launch as a 32-bit process on the 64-bit client. **Yes** or **No** options are available. The default value is **No**.++
Administrator comments This optional field corresponds to the term **Administrator comments** in the SCCM admin console. ++++
The screenshot below shows the default values of the Deployment type template settings: [![sccm_09_02.png](https://docs.apptimized.com/uploads/images/gallery/2022-04/scaled-1680-/jviYRJ0fxiSTK5S9-sccm_09_02.png)](https://docs.apptimized.com/uploads/images/gallery/2022-04/jviYRJ0fxiSTK5S9-sccm_09_02.png) Settings are persisted on click to **Save** button. Apptimized shows the following notification when successful: [![sccm_changes_07.png](https://docs.apptimized.com/uploads/images/gallery/2020-07/scaled-1680-/bTAjeZIC7D1cHfn9-sccm_changes_07.png)](https://docs.apptimized.com/uploads/images/gallery/2020-07/bTAjeZIC7D1cHfn9-sccm_changes_07.png) ### Package template The option to configure SCCM package template is available under **Project settings** > **Integration > **choose **SCCM Environment** > **Package template****.** [![sccm_11_03.png](https://docs.apptimized.com/uploads/images/gallery/2021-12/scaled-1680-/mIP9LJnNeczw0FOE-sccm_11_03.png)](https://docs.apptimized.com/uploads/images/gallery/2021-12/mIP9LJnNeczw0FOE-sccm_11_03.png) Apptimized shows the following screen when successful: [![PackageTemplateSCCM.png](https://docs.apptimized.com/uploads/images/gallery/2024-03/scaled-1680-/packagetemplatesccm.png)](https://docs.apptimized.com/uploads/images/gallery/2024-03/packagetemplatesccm.png) Table 4. Package template settings
Setting Description
Package name This setting enables a user to set up the name for package template. This setting is **required**. The default value is: **\[Manufacturer\]\_\[ProductName\]\_\[ProductVersion\]\_\[AppLanguage\].**
Comment This setting enables a user to set an optional descriptions for the package template.
Where unzip package source This setting enables a user to set up patch for unzipped package source files will be placed on. This section is **required**.

**Note. **In most cases, this field will be the same as **Source path **field value.

Use package name for the folder name This setting enables a user to use package name as package folder name. The default value is **No**.
Source path This setting enables a user to set up folder where the source is placed in zip file. The zip file name is ignored under clarifying the source path. This setting is **required**. The default value is **\[Manufacturer\]\_\[ProductName\]\_\[ProductVersion\]\_\[AppLanguage\]**

**Note.** This path is relative to **Where unzip package source **field value.

Folder for package in SCCM Console This setting enables a user to set up folder for package in SCCM Console. Example: - Dummy\\Folder; - Dummy.

**Note.** The package will be created under the root if the value is empty.

Remove default User account This setting enables a user to Remove user from Manage Access Account window, which is added to package by default. The default value is **Yes**.
Add account access This setting enables a user to fill **Group name **and **Permission access level** fields. The default value is **Yes**.
User name This setting enables a user to fill name of the user that will be addedd to Manage Accont Acces window of SCCM servier. The fill within form is **\[domain\]\\\[userName\]**. This setting is **required**.
Permission access level This setting enables to set up permission access level for the specified user. The following levels available: - Read; - Change; - Full control; - No access. The default value is **Read**.
Set security scope This setting enables to set up **Security scope **field to be specified.
Security scope This setting enables a user to set up Security scope name that will be set to most (or all) packages. This setting is **required**. The default value is **Factory DPs**.
##### Programs for packages The created programs for SCCM packages are stored under **Programs for packages** section. [![sccm_12_01-(1).png](https://docs.apptimized.com/uploads/images/gallery/2021-11/scaled-1680-/dDCA7v3dbjwlFxj5-sccm_12_01-(1).png)](https://docs.apptimized.com/uploads/images/gallery/2021-11/dDCA7v3dbjwlFxj5-sccm_12_01-(1).png) The option to create program is available under **Create program** button. [![sccm_27_01-(1).png](https://docs.apptimized.com/uploads/images/gallery/2021-11/scaled-1680-/KXDMrK9YqMDrCBNp-sccm_27_01-(1).png)](https://docs.apptimized.com/uploads/images/gallery/2021-11/KXDMrK9YqMDrCBNp-sccm_27_01-(1).png) Apptimized shows the following screen when successful: [![sccm_13_01-(1).png](https://docs.apptimized.com/uploads/images/gallery/2021-11/scaled-1680-/SKJ6wgjGqzCMADX6-sccm_13_01-(1).png)](https://docs.apptimized.com/uploads/images/gallery/2021-11/SKJ6wgjGqzCMADX6-sccm_13_01-(1).png) Table 5. Program template settings
**Setting****Description**
Program nameThis setting enables a user to set up the name of the program template. This setting is **required**. The default value is **Install.**
Command lineThis setting enables a user to set up the command line of the program template. The default value is **install.cmd**
Start folder This setting enables a user to set up he name of startup folder of the program template.
User interaction This setting enables to set up interaction lever of user with package. The following levels available: - Hidden; - Minimized; - Normal; - Maximized. The default value is **Hidden**.
Program can run This setting enables a user to define run context of package. The following contexts available: - Whether or not user is logged on; - Only when user is logged on; - Only when no user is logged on. The default value is **Whether or not user is logged on**.
Run mode This setting enables a user to define permission level of package context run. This setting is available to change only if **Only when user is logged on **setting is set under **Program can run **setting. The following permission levels available: - Run with Administrative rights; - Run with user rights; The default value is **Run with Administrative rights**.
Allow users to view and interact with the program installation This setting enables to allow users to view and interact with the program insallation. The default value is **No**.
Drive mode This setting enables to define drive mode of the package installation / uninstallation. The following modes available: - Runs with UNC name; - Required drive letter - Requires specific drive letter (example: Z:). The default value is **Runs with UNC name**.
Allow this program to be installed from task sequence This setting enables to allow the program to be installaed from the Install Package task sequecne without being deployed. The default value is **No**.
Select platfroms This setting enables to select OS platforms where package can run. The following platforms available: - All Windows 10 (64-bit); - All Windows 7 (64-bit); - All Windows 8.1 (64-bit); - All Windows Server 2008 R2 (64-bit); - All Windows Server 2012 R2 (64-bit); - All Windows Server 2016 (64-bit); - All Windows 7 (32-bit).

**Note**. Empty field value is allowing any platform.

Estimated disk space This setting enables to estimate disk space for packages if required. The value if unknown is 0 or empty. The default value is 0.
Select unit of a disk sace size This setting enables to define unit f the disk space if the estimated disk space is set. The following units available: - KB; - MB; - GB. The default value is **MB**.
Maximum allowed run time (minutes) This setting enables a user to set up maximum allowed run time in minutes. The default value is **120**.
Administrative comment This optional field corresponds to the term **Administrator comments** in the SCCM admin console.
The option to save settings is available under **Save **button. Apptimized shows the following notification when successful: [![sccm_14_01-(1).png](https://docs.apptimized.com/uploads/images/gallery/2021-11/scaled-1680-/Ou02sx0vUfhF3kDN-sccm_14_01-(1).png)](https://docs.apptimized.com/uploads/images/gallery/2021-11/Ou02sx0vUfhF3kDN-sccm_14_01-(1).png) [![sccm_15_01-(2).png](https://docs.apptimized.com/uploads/images/gallery/2021-11/scaled-1680-/4jjUWbtWtVeNnmvq-sccm_15_01-(2).png)](https://docs.apptimized.com/uploads/images/gallery/2021-11/4jjUWbtWtVeNnmvq-sccm_15_01-(2).png) ##### Deployment for packages Created deployments for packages are stored under** ****Deployments ****for packages** section. [![sccm_16_01-(2).png](https://docs.apptimized.com/uploads/images/gallery/2021-11/scaled-1680-/SeF5URI5ffzRo8Hf-sccm_16_01-(2).png)](https://docs.apptimized.com/uploads/images/gallery/2021-11/SeF5URI5ffzRo8Hf-sccm_16_01-(2).png) The option to create deployment is available under **Create deployment** button. [![sccm_28_01-(1).png](https://docs.apptimized.com/uploads/images/gallery/2021-11/scaled-1680-/68LXHoZzdhjvZHUe-sccm_28_01-(1).png)](https://docs.apptimized.com/uploads/images/gallery/2021-11/68LXHoZzdhjvZHUe-sccm_28_01-(1).png) Apptimized shows the following screen when successful: [![sccm_17_01.png](https://docs.apptimized.com/uploads/images/gallery/2021-11/scaled-1680-/aNdGHhxomvpHM82d-sccm_17_01.png)](https://docs.apptimized.com/uploads/images/gallery/2021-11/aNdGHhxomvpHM82d-sccm_17_01.png) Table 6. Package deployment template settings
**Setting** **Description**
Program name This setting enables to set up program name to which deployment belongs to. This field is **required**. The default value is **Install**.
Collection type This setting enables to indicate the collection type that will be loaded from the user SCCM server. This setting is **required**. The following types are available: - Device; - User. The default value is **Device**.
Limiting collection for the deployment This setting enables settng limiting collection for the collection deployment.
Collection folder in SCCM Console This setting enables setting up a collection path under the SCCM console.
Action This setting enables set the action during deployment. The available action is **Install**. The value can not be changed.
Purpose This setting enables the definition of the requirement of the installation/uninstallation process. The following values are available: - Available; - Required. The default value is **Available**.
Send wake-up packets This setting enables to define sending [wake-up packets](https://docs.microsoft.com/en-us/mem/configmgr/core/clients/deploy/plan/plan-wake-up-clients) before deployment under SCCM. The default value is **No**. Note. This setting is available only if **Required **purpose is set.
Allow clients on a metered internet connection to download content after the installation deadline, which right incurs additional costs This setting enables to allow clients on a metered internet connection to download content after the installation deadline, which right incurs additional costs. The default value is **No**. Note. This setting is available only if **Required **purpose is set.
Rerun behavior This setting enables to specify rerunning deployment behavior on a client. The following values are available: - Always rerun program; - Never rerun deployed program; - Rerun if failed previous attempt; - Rerun if succeeded on the previous attempt. The default value is **Always rerun program**. Note. This setting is available only if **Required **purpose is set.
Recur every The setting enables to specify a recurring interval. The default value is **1**. **Note**. This setting is available only if **Required **purpose is set.
Recurrence interval type This setting enables selection of recurrence interval types for the schedule. The following options are available: - Days; - Hours; - Minutes. The default value is **Days**. **Note**. This setting is available only if **Required **purpose is set.
Schedule This setting enables to schedule date and time for the deployment. **Note. **Time must be UTC. The time will be converted to the timezone of the User’s SCCM Server. This setting is** **available only if** Required **purpose is set.
Allow users to run the program independently of assignments This setting enables users to run the program from Software Center. The default value is **Yes**. The value can not be changed.
Software installation This setting enables a user to allow installation of the deployed software outside of maintenance windows. The default value is **No**.
System restart (if required to complete the installation) This setting enables to set up system restarting outside a maintenance window. The default value is **No**.
Commit changes at deadline or during a maintenance window (requires restarts) This setting enables to setting up write filters for embedded devices. The default value is **Yes**. **Note**. If this setting is not enabled, the content will be applied on the overlay and committed later.
Select the deployment option to use when a client uses a distribution point from a current boundary group This setting enables to specify client behavior on a fast network. The following options are available to select: - Download content from distribution point and run locally; - Run program from the distribution point. The default value is **Download content from distribution point and run locally**.
Select the deployment option to use when a client uses a distribution point from a neighbor boundary group or the default site boundary group This setting enables to specify client behavior on a slow network. The following options are available to select: - Download content from distribution point and run locally; - Do not run program; The default value is **Download content from distribution point and run locally**.
Allow clients to use distribution points from the default site boundary group This setting enables allow clients to use shared content. The default value is **No**.
The option to save deployments for packages settings is available under **Save **button. Apptimized shows the following notification when successful: [![sccm_18_01-(3).png](https://docs.apptimized.com/uploads/images/gallery/2021-11/scaled-1680-/JWn2VRCss96D58Rr-sccm_18_01-(3).png)](https://docs.apptimized.com/uploads/images/gallery/2021-11/JWn2VRCss96D58Rr-sccm_18_01-(3).png) The option to save package templates settings is available under **Save** button. [![sccm_10_2.png](https://docs.apptimized.com/uploads/images/gallery/2021-11/scaled-1680-/GbtxVDr8dkgx6JQE-sccm_10_2.png)](https://docs.apptimized.com/uploads/images/gallery/2021-11/GbtxVDr8dkgx6JQE-sccm_10_2.png) Apptimized shows the following notification when successful: [![sccm_19_01-(3).png](https://docs.apptimized.com/uploads/images/gallery/2021-11/scaled-1680-/qhiWskqOkBQ0ze9o-sccm_19_01-(3).png)](https://docs.apptimized.com/uploads/images/gallery/2021-11/qhiWskqOkBQ0ze9o-sccm_19_01-(3).png) ### Apptimized SCCM Connector Installer The integration procedure of the Apptimized SCCM Connector and SCCM environment ends up with the installation of SCCM Connector Agent to the endpoint PC. Apptimized **SCCM Connector Installer** can be downloaded once the **required settings** are completed. [![Group 4.png](https://docs.apptimized.com/uploads/images/gallery/2024-03/scaled-1680-/group-4.png)](https://docs.apptimized.com/uploads/images/gallery/2024-03/group-4.png) **SCCM API Key** also must be generated. [![Group 6.png](https://docs.apptimized.com/uploads/images/gallery/2024-03/scaled-1680-/group-6.png)](https://docs.apptimized.com/uploads/images/gallery/2024-03/group-6.png) After downloading **Apptimized SCCM** **Connector Installer**, a user has to run an **Install CMD.**** ** **[![DownloadingInstaller.png](https://docs.apptimized.com/uploads/images/gallery/2024-03/scaled-1680-/downloadinginstaller.png)](https://docs.apptimized.com/uploads/images/gallery/2024-03/downloadinginstaller.png)** A service with **entered credentials** is created when finished successfully: [![Group 27.png](https://docs.apptimized.com/uploads/images/gallery/2024-02/scaled-1680-/group-27.png)](https://docs.apptimized.com/uploads/images/gallery/2024-02/group-27.png) Creating a **new user** is available under **Server Manager** > **Dashdoard** > **Tools** > **Active Directory Users and Computers** > **New** > **User**. [![Anewuser.png](https://docs.apptimized.com/uploads/images/gallery/2024-03/scaled-1680-/anewuser.png)](https://docs.apptimized.com/uploads/images/gallery/2024-03/anewuser.png) The following fields must be filled with **proper information**. [![Fields.png](https://docs.apptimized.com/uploads/images/gallery/2024-03/scaled-1680-/fields.png)](https://docs.apptimized.com/uploads/images/gallery/2024-03/fields.png) Adding a user to a group is available under “**Add to a group**”. [![addingtogroup.png](https://docs.apptimized.com/uploads/images/gallery/2024-03/scaled-1680-/addingtogroup.png)](https://docs.apptimized.com/uploads/images/gallery/2024-03/addingtogroup.png) After the previous steps a user must go to **Server Manager** > **Dashdoard** > **Tools** > **Local Security** > **Log on as a service and run the service.**** ** **[![Logonasservice.png](https://docs.apptimized.com/uploads/images/gallery/2024-03/scaled-1680-/logonasservice.png)](https://docs.apptimized.com/uploads/images/gallery/2024-03/logonasservice.png)** **[![Runasadiffuser.png](https://docs.apptimized.com/uploads/images/gallery/2024-03/scaled-1680-/runasadiffuser.png)](https://docs.apptimized.com/uploads/images/gallery/2024-03/runasadiffuser.png)** Before installing and pushing an application to SCCM, a user must have **certain permissions.**** ** **A Security role (Application Administrator****)** or **Configuration Manager**. [![SCCMm1.png](https://docs.apptimized.com/uploads/images/gallery/2024-02/scaled-1680-/sccmm1.png)](https://docs.apptimized.com/uploads/images/gallery/2024-02/sccmm1.png) The account also must have the **Windows Server Distributed Component Object Model (DCOM) Remote Activation permission** for the computer running the **Configuration Manager** site server and the **SMS provider**. [![SCCMm2.png](https://docs.apptimized.com/uploads/images/gallery/2024-02/scaled-1680-/sccmm2.png)](https://docs.apptimized.com/uploads/images/gallery/2024-02/sccmm2.png) The user must be added to a policy called **"Log on as a service".** **[![SCCMm3.png](https://docs.apptimized.com/uploads/images/gallery/2024-02/scaled-1680-/sccmm3.png)](https://docs.apptimized.com/uploads/images/gallery/2024-02/sccmm3.png)** **Apptimized **shows the following window when successful**: ** **[![SCCMm4.png](https://docs.apptimized.com/uploads/images/gallery/2024-02/scaled-1680-/sccmm4.png)](https://docs.apptimized.com/uploads/images/gallery/2024-02/sccmm4.png)** The account name must contain** a domain: ** **[![SCCMm5.png](https://docs.apptimized.com/uploads/images/gallery/2024-02/scaled-1680-/sccmm5.png)](https://docs.apptimized.com/uploads/images/gallery/2024-02/sccmm5.png)** **Apptimized** shows an error if a user doesn’t exist: [![SCCMm6.png](https://docs.apptimized.com/uploads/images/gallery/2024-02/scaled-1680-/sccmm6.png)](https://docs.apptimized.com/uploads/images/gallery/2024-02/sccmm6.png) After this action, the user can push the application same as it was in the **previous** **version**, even in case he is **signed out**. ##### Install Behavior Settings If needed to close apps before installation a user should go to > **Administration** > Settings> Integration> **SCCM**> Project settings >Create Deployment type >**Install Behavior Settings** and add an **Executable File Name** and a **Display Name**. [![Inslallbehavior1.png](https://docs.apptimized.com/uploads/images/gallery/2024-04/scaled-1680-/inslallbehavior1.png)](https://docs.apptimized.com/uploads/images/gallery/2024-04/inslallbehavior1.png) It is possible more than one apps to be closed. Adding **more fields** is available under **Actions.** **[![Inslallbehavior2.png](https://docs.apptimized.com/uploads/images/gallery/2024-04/scaled-1680-/inslallbehavior2.png)](https://docs.apptimized.com/uploads/images/gallery/2024-04/inslallbehavior2.png)** After entering the proper names a user must click on a **Save** button. [![Installbehavior3.png](https://docs.apptimized.com/uploads/images/gallery/2024-04/scaled-1680-/installbehavior3.png)](https://docs.apptimized.com/uploads/images/gallery/2024-04/installbehavior3.png) A **Software Center** shows the following when successful: [![Installbehavior4.png](https://docs.apptimized.com/uploads/images/gallery/2024-04/scaled-1680-/installbehavior4.png)](https://docs.apptimized.com/uploads/images/gallery/2024-04/installbehavior4.png) ### Manage project roles SCCM Connector requires the assignment of the project user to the role with the required permission. Assign needed permissions under **Roles** in a project setting. [![sccm_17.png](https://docs.apptimized.com/uploads/images/gallery/2020-03/scaled-1680-/t4cHPiFkzN7a8SZm-sccm_17.png)](https://docs.apptimized.com/uploads/images/gallery/2020-03/t4cHPiFkzN7a8SZm-sccm_17.png) It is possible to add permission to the existing group or create a new one by clicking on the “**Add new role**” button, as shown on the screenshots below. [![sccm_18.png](https://docs.apptimized.com/uploads/images/gallery/2020-03/scaled-1680-/5teW7nWyHApBpmyl-sccm_18.png)](https://docs.apptimized.com/uploads/images/gallery/2020-03/5teW7nWyHApBpmyl-sccm_18.png) The new role requires its name and SCCM project permission. [![sccm_20_01.png](https://docs.apptimized.com/uploads/images/gallery/2023-02/scaled-1680-/tE1RfeZth3bia1MI-sccm_20_01.png)](https://docs.apptimized.com/uploads/images/gallery/2023-02/tE1RfeZth3bia1MI-sccm_20_01.png) Apptimized shows the following notification when completed successfully: [![sccm_21.png](https://docs.apptimized.com/uploads/images/gallery/2020-03/scaled-1680-/WgsggGRtUF5BIij9-sccm_21.png)](https://docs.apptimized.com/uploads/images/gallery/2020-03/WgsggGRtUF5BIij9-sccm_21.png) Users can be added to the role via **Update users** or **Update groups** screens. [![sccm_22_1.png](https://docs.apptimized.com/uploads/images/gallery/2020-03/scaled-1680-/3E9G0q1LhsxKKcvS-sccm_22_1.png)](https://docs.apptimized.com/uploads/images/gallery/2020-03/3E9G0q1LhsxKKcvS-sccm_22_1.png) [![sccm_22_2.png](https://docs.apptimized.com/uploads/images/gallery/2020-03/scaled-1680-/qS2emMQxV5erabKm-sccm_22_2.png)](https://docs.apptimized.com/uploads/images/gallery/2020-03/qS2emMQxV5erabKm-sccm_22_2.png) A new group or user can be selected on the next screen, and click on **Save** persists all changes. [![sccm_23.png](https://docs.apptimized.com/uploads/images/gallery/2020-03/scaled-1680-/Rona1PGaSsbtmUhj-sccm_23.png)](https://docs.apptimized.com/uploads/images/gallery/2020-03/Rona1PGaSsbtmUhj-sccm_23.png) [![sccm_24.png](https://docs.apptimized.com/uploads/images/gallery/2020-03/scaled-1680-/mC1Pt2IACanc7Abs-sccm_24.png)](https://docs.apptimized.com/uploads/images/gallery/2020-03/mC1Pt2IACanc7Abs-sccm_24.png) A current role can be changed with the **Edit** screen and by following the same set of operations as for adding a new role. [![sccm_22_3.png](https://docs.apptimized.com/uploads/images/gallery/2020-03/scaled-1680-/AWPjflLYMXjAjfpr-sccm_22_3.png)](https://docs.apptimized.com/uploads/images/gallery/2020-03/AWPjflLYMXjAjfpr-sccm_22_3.png) [![sccm_25_01.png](https://docs.apptimized.com/uploads/images/gallery/2023-02/scaled-1680-/YhtsX7FftabpCtTj-sccm_25_01.png)](https://docs.apptimized.com/uploads/images/gallery/2023-02/YhtsX7FftabpCtTj-sccm_25_01.png) The role can be removed by clicking on the **Delete** button and after providing a confirmation. [![sccm_22_4.png](https://docs.apptimized.com/uploads/images/gallery/2020-03/scaled-1680-/N3dZ6GK89tX3Ne33-sccm_22_4.png)](https://docs.apptimized.com/uploads/images/gallery/2020-03/N3dZ6GK89tX3Ne33-sccm_22_4.png) [![sccm_26.png](https://docs.apptimized.com/uploads/images/gallery/2020-03/scaled-1680-/EEi9vPf9VJqqYQS6-sccm_26.png)](https://docs.apptimized.com/uploads/images/gallery/2020-03/EEi9vPf9VJqqYQS6-sccm_26.png) ### # Infrastructure ### Infrastructure components The figure below shows the scheme of the SCCM connector infrastructure. ### [![Drawing-2_3_3.png](https://docs.apptimized.com/uploads/images/gallery/2020-03/scaled-1680-/LAO46MZ7RkZ24aSX-Drawing-2_3_3.png)](https://docs.apptimized.com/uploads/images/gallery/2020-03/LAO46MZ7RkZ24aSX-Drawing-2_3_3.png) The infrastructure components details are described in Tables 1 - 2. Table 1. Infrastructure components
**Component** **Details**
1\. Apptimized Portal The platform where Apptimized customer manages projects portfolios. Requires an active project with enabled and configured SCCM connector settings.
The screenshot below shows the Apptimized Portal interface. [![sccm_adm_01.png](https://docs.apptimized.com/uploads/images/gallery/2020-03/scaled-1680-/ddy7ZMWiUcGn4t98-sccm_adm_01.png)](https://docs.apptimized.com/uploads/images/gallery/2020-03/ddy7ZMWiUcGn4t98-sccm_adm_01.png) Table 2. Infrastructure components
**Component** **Details**
2\. Customer Environment Information technology environment, including software, hardware, and systems (e.g., endpoint PCs, VMs, servers, networks).

The access of endpoint PC or VM to the 443 port of the app.apptimized.com host is a prerequisite.

2.1. Proxy server This component is optional. A proxy server is a third party between the customer and the service (the Apptimized Portal). A proxy server manages the requests sent by the customer and completes them depending on the system's preferences.
2.2. Apptimized SCCM connector A tool that enables customers to deploy ready-made packages directly from Apptimized to an SCCM environment and to upload applications from the SCCM server to Apptimized for testing purposes or further processing. It connects Apptimized Portal and SCCM Admin Console via HTTPS long-polling strategy, where the SCCM connector pulls data from the Apptimized portal every 10 seconds. The SCCM connector must be launched on a local PC by the domain administrator or domain user. Runs on platforms: Microsoft Windows Desktop (Windows 7 and above) or Server OS (Windows Server 2012 R2 and above) with installed .NET Framework 4.6.1
2.3. SCCM administrator console Console to manage applications in the customer environment.
2.4. Customer SCCM server Customer’s server where the SCCM is installed.
The screenshot below shows the SCCM administrator console interface. [![image_2020-07-07_11-26-03.png](https://docs.apptimized.com/uploads/images/gallery/2020-07/scaled-1680-/A9U1eZoMPEM4Gwof-image_2020-07-07_11-26-03.png)](https://docs.apptimized.com/uploads/images/gallery/2020-07/A9U1eZoMPEM4Gwof-image_2020-07-07_11-26-03.png) ### Communication process The Apptimized Portal communicates to the Customer environment via API. To integrate the Apptimized Portal with the SCCM environment, the SCCM Connector must be installed to the endpoint PC. The SCCM Connector pings Apptimized Portal every 10 seconds for a new data on the project. To identify the customer, only the remote ID is used. Any other data from the customer will not be requested. When data is received from the Apptimized Portal, the SCCM Connector transforms it to [Powershell](https://docs.microsoft.com/en-us/powershell/scripting/overview?view=powershell-7) commands to communicate with the SCCM administrator console on the endpoint PC. The SCCM administrator console sends information to the SCCM server within its communication protocols and methods. The information flow content depends on the type of customer activity (see Cases 1-2). ##### Case 1. A customer pushes **TimKosse\_FileZilla\_3.46.3\_English(United States)** to SCCM. Outbound information** - a data sent from the Apptimized Portal: - the SCCM administrator console connection parameters

Site code - **DEM**; Path to the SCCM console - **C:\\Program Files (x86)\\Microsoft Configuration Manager\\AdminConsole\\bin**; Path to the network share - **\\\\WIN-2HDJCBHRRVB\\Sources$\\incoming\\TimKosse\_FileZilla\_3.46.3\_English(United States)**.

- package metadata;

Package name - **TimKosse\_FileZilla\_3.46.3\_English(United States)**; Application version - **3.46.3**; Application vendor - **Tim Kosse**; Application name - **FileZilla**; Application language - **English(United States);** Auto-install in task sequence of SCCM console - **Yes;** Application owner - **The default value is customer's name (i.e. John Doe);** Application description (optional) - Will be sent, if something has been indicated; SCCM optional reference (optional) - Will be sent, if something has been indicated; Folder in the SCCM console UI - **Applications/Test 1**.

- an application (package) sources in **.zip** format;

An archive in **.zip** format contains a PSADT Wrapper and a package source in **.msi** format.

- a deployment type information;

Deployment type name - **TimKosse\_FileZilla\_3.46.3\_English(United States)\_DT**; Path to the source in SCCM environment network - **\\\\WIN-2HDJCBHRRVB\\Sources$\\incoming\\TimKosse\_FileZilla\_3.46.3\_English(United States)**; Name of the default distribution group - **Demo Distribution Group**; Installer type - **Script Installer;** Script type for the detection method - **Powershell;** Detection script content - **Get-ItemProperty "HKLM:Software\\ TimKosse\_FileZilla\_3.46.3\_English(United States)\\TimKosse\\FileZilla \\3.46.3" -ErrorAction SilentlyContinue | Where { $\_.IsInstalled -eq 1 }**; Persist content in client cache - **Yes**; Installation command with parameters - **Deploy-Application.exe -DeploymentType Install**; Uninstallation command with parameters - **Deploy-Application.exe -DeploymentType Uninstall**; What to do on slow network - **Download**; Maximum installation time (minutes) - **120**; Estimated installation time by default (minutes) - 0; Run installation program as a 32-bit process on 64-bit client - **No**; Admin comment (optional) - Will be sent, if something has been indicated.

- deployment information for the application/package;

Collection name - **Demo devices;** Install or uninstall the application by default - **Install**; Deploy purpose of the installation by default - **Available;** Deadline date - **02.02.2020 00:00;** Deadline time - **18:00**; Time zone of a deadline - **Local time**.

**Inbound information** - a data sent to the Apptimized Portal: - a response to the outbound information commands (result - OK); - request to get information with remote ID parameter

Remote ID - **1745a854-2d9a-4f99-8a04-d511882f7028**.

##### Case 2. A customer imports **TimKosse\_FileZilla\_3.46.3\_English(United States)** from SCCM. **Outbound information** - a data sent from the Apptimized Portal: - the SCCM administrator console connection parameters;

Site code - **DEM**; Path to the SCCM console - **C:\\Program Files (x86)\\Microsoft Configuration Manager\\AdminConsole\\bin**; Path to the network share - **\\\\WIN-2HDJCBHRRVB\\Sources$\\incoming\\ TimKosse\_FileZilla\_3.46.3\_English(United States)**.

- a command to get a list of applications in the SCCM administrator console; ``` Get-WmiObject -Namespace ROOT\SMS\Site_$SiteCode `         -Query "SELECT * FROM SMS_ObjectContainerNode WHERE ObjectType='6000'" | `         Select-Object -Property Name, ContainerNodeID, ParentContainerNodeId; ``` - a command to get metadata of applications in the SCCM administrator console; ``` GetApplicationsMetadata(string stringPsApps) =>             SccmResultHelper.ConvertToSccmObjects(                 ExecutePsCommand($"Get-CMApplication | `" +                     $"Select-Object -Property LocalizedDisplayName, SDMpackageXML | `" +                     $"Where-Object {{({stringPsApps}).Contains($_.LocalizedDisplayName)}} | `" +                     $"Select-Object -ExpandProperty SDMpackageXML", out _)); ``` - a command to get an application (package) sources in the SCCM administrator console. The SCCM Connector will receive the path to the SCCM application source from SCCM application metadata. It will be zipped and sent to the Apptimized Portal. Inbound information** - a data sent to the Apptimized Portal: - request to get information with remote ID parameter

Remote ID - **1745a854-2d9a-4f99-8a04-d511882f7028.**

- an application (package) sources in **.zip** format;

An archive in **.zip** format contains a PSADT Wrapper and a package source in **.msi** format.

- a list of SCCM applications (or one specific application)

An application - **TimKosse\_FileZilla\_3.46.3\_English(United States)**; An application related data: "Path":"/Test 1", "ContainerId":"16777218", "ResourceId":"Res\_810274514", "IsDuplicated":false.

- an application's metadata in the SCCM administrator console;

Package name - **TimKosse\_FileZilla\_3.46.3\_English(United States)**; Application version - **3.46.3**; Application vendor - **Tim Kosse**; Application name - **FileZilla**; Application language - **English(United States).**

### Communication methods The SCCM Connector is configured to communicate with the Apptimized Portal using HTTPS protocol. The text box below provides the certificate details:

Issued by – K Software certificate Authority (DV) 2 [https://sectigo.com/legal](https://sectigo.com/legal) Version – V3 Signature algorithm – sha256RSA Signature hash algorithm – sha256 Public key – RSA (2048 Bits) TLS – 1.2

The Powershell commands are implemented to communicate the SCCM Connector with the SCCM Console. The text box below provides the commands list depending on the client's activities. 1. **Push to SCCM:** - Import-Module .\\ConfigurationManager.psd1; - New-CMApplication; - Add-CMDeploymentType; - Add-CMMsiDeploymentType; - Start-CMContentDistribution; - Start-CMApplicationDeployment; - Move-CMObject -FolderPath; - Set-ExecutionPolicy -ExecutionPolicy RemoteSigned -Scope Process -Force. 2. **Import from SCCM:** - Import-Module .\\ConfigurationManager.psd1; - Get-CMApplication; - Get-WmiObject; - Set-ExecutionPolicy -ExecutionPolicy RemoteSigned -Scope Process -Force. # Security and limitations To ensure security Apptimized complies with the following cybersecurity standards: - ISO 15408; - ISO/IEC 27001; - ISO/IEC 27002; - ANSI/ISA 62443 (Formerly ISA-99); - IEC 62443; A military-grade security protocol ([TLS/SSL](https://docs.microsoft.com/en-us/windows-server/security/tls/tls-ssl-schannel-ssp-overview)) is used by Apptimized to provide privacy and data integrity between two or more communicating applications. Apptimized safety audit entails a network scan of its resources to identify vulnerabilities and non-penetration. The screenshot below shows the vulnerability report provided by **Detectify** for **app.apptimized.com**. [![sccm_adm_03_4.png](https://docs.apptimized.com/uploads/images/gallery/2020-03/scaled-1680-/MmESvmM2142UiAbc-sccm_adm_03_4.png)](https://docs.apptimized.com/uploads/images/gallery/2020-03/MmESvmM2142UiAbc-sccm_adm_03_4.png) The screenshots below show the SSL report of **app.apptimized.com**. [![sccm_adm_05_1.png](https://docs.apptimized.com/uploads/images/gallery/2020-03/scaled-1680-/FDOxbDM9eImMUoJX-sccm_adm_05_1.png)](https://docs.apptimized.com/uploads/images/gallery/2020-03/FDOxbDM9eImMUoJX-sccm_adm_05_1.png) [![sccm_adm_05_5.png](https://docs.apptimized.com/uploads/images/gallery/2020-03/scaled-1680-/ochmWF8LIzubGeyF-sccm_adm_05_5.png)](https://docs.apptimized.com/uploads/images/gallery/2020-03/ochmWF8LIzubGeyF-sccm_adm_05_5.png) The SCCM connector must be launched on a local PC by the domain administrator or domain user. Domain user must have the permissions to: - create applications, deployment types, and deployments; - write permissions for network share with packages source media for automatic media transfer. # Technical workflows ### Push to SCCM workflow The figure below shows the push to the SCCM workflow. The instructions for SCCM connector integration are considered in the [Apptimized SCCM connector integration user manual](https://docs.apptimized.com/books/apptimized-platform-admin-manual/page/integration "Integration"). [![Push-to-SCCM.png](https://docs.apptimized.com/uploads/images/gallery/2020-03/scaled-1680-/P8yGeoawkOAREXaR-Push-to-SCCM.png)](https://docs.apptimized.com/uploads/images/gallery/2020-03/P8yGeoawkOAREXaR-Push-to-SCCM.png) ### Import from SCCM workflow The figure below shows the import from the SCCM workflow. The instructions for import from SCCM are considered in the [Apptimized SCCM connector integration user manual](https://docs.apptimized.com/books/apptimized-platform-admin-manual/page/integration "Import from SCCM"). [![Import-from-SCCM.png](https://docs.apptimized.com/uploads/images/gallery/2020-03/scaled-1680-/R0fksfo8TlIYxME8-Import-from-SCCM.png)](https://docs.apptimized.com/uploads/images/gallery/2020-03/R0fksfo8TlIYxME8-Import-from-SCCM.png)