> For the complete documentation index, see [llms.txt](https://docs.secure-contacts.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.secure-contacts.com/quickstart-guide/windows-intune-managed-steps-to-activate-sca-in-your-entra-tenant/step-2-windows-deploy-sca-with-intune.md).

# Step 2 -Windows- Deploy SCA with Intune

In this step, you package the approved SCA MSI and create a Windows app (Win32) in Microsoft Intune.

{% hint style="info" %}
Application deployment and App Configuration are separate Intune objects. Assign both objects to the same Windows test device group.
{% endhint %}

In this step, you package the approved SCA MSI and create a Windows app (Win32) in Microsoft Intune.

{% hint style="info" %}
Application deployment and App Configuration are separate Intune objects. Assign both objects to the same Windows test device group.
{% endhint %}

{% stepper %}
{% step %}

## Download the SCA Package

* Download the `SecureContacts-<version>.msi` file from the latest release:

{% embed url="<https://github.com/Provectus-Software-GmbH/SCA_Desktop_Releases/releases/latest>" %}

{% hint style="warning" %}
Use the MSI file for this Intune workflow. Do not package the `.exe` installer when following the MSI commands and detection rule in this guide.
{% endhint %}

{% endstep %}

{% step %}

## Create the IntuneWin Package

* Copy the downloaded MSI into an empty input folder.

* Run Microsoft Win32 Content Prep Tool:

```powershell
IntuneWinAppUtil.exe -c "C:\SCA\Input" -s "SecureContacts-<version>.msi" -o "C:\SCA\Output"
```

Replace `<version>` with the exact version in the downloaded MSI filename.

* Verify that the `.intunewin` package was created in the output folder.

{% endstep %}

{% step %}

## Create the Windows App

* In the Microsoft Intune admin center, go to **Apps → Windows → Create**.

* Select **Windows app (Win32)**&#x20;

{% endstep %}

{% step %}

### App information

* Upload the generated `.intunewin` file from output folder.

* Review the automatically detected application information and enter the required metadata for your organization.
  {% endstep %}

{% step %}

### Program

* On the **Program** page, configure:

| Setting           | Value                                                      |
| ----------------- | ---------------------------------------------------------- |
| Install command   | `msiexec /i "SecureContacts-<version>.msi" /qn ALLUSERS=1` |
| Uninstall command | `msiexec /x "{PRODUCT-CODE}" /qn`                          |
| Install behavior  | System                                                     |

{% hint style="success" %}
Use the exact MSI filename contained in the `.intunewin` package. Replace `{PRODUCT-CODE}` with the ProductCode from the selected MSI
{% endhint %}

{% hint style="info" %}
Read the ProductCode from the selected MSI with your organization's approved MSI inspection tool. Keep the value including its braces for the uninstall command and detection rule.
{% endhint %}

{% hint style="warning" %}
Configure the device restart behavior and return codes according to your organization's Win32 application standard.
{% endhint %}

{% endstep %}

{% step %}

### Requirements

* Configure the operating system architecture, minimum Windows version, disk space, and other requirements approved for the selected SCA release.

{% hint style="warning" %}
Use the system requirements approved for the selected release. Do not broaden the Intune requirements to include unsupported devices.
{% endhint %}

{% endstep %}

{% step %}

### Detection Rule

* Select **Manually configure detection rules**.

* Add one rule with **Rule type: MSI** and enter the ProductCode from the selected MSI.

* Enable the option for a 32-bit application on 64-bit clients only if this matches the actual MSI installation.

{% hint style="danger" %}
Configure exactly one MSI ProductCode detection rule for SCA. Do not add a second MSI rule for the same application.
{% endhint %}

{% endstep %}

{% step %}

### Assignments

* Assign the application as **Required** to your Windows test device group.

{% endstep %}

{% step %}

## Review + create

Review the configuration and select **Create**

{% endstep %}
{% endstepper %}

{% hint style="success" %}
Deployment of the App is finalized, last step is to verify that configurations are applied and app gets installed via Intune on your Test-device.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.secure-contacts.com/quickstart-guide/windows-intune-managed-steps-to-activate-sca-in-your-entra-tenant/step-2-windows-deploy-sca-with-intune.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.