Package Creation: Just like in the System Center Configuration Manager (SCCM) process, you should convert your existing applications to MSIX using the MSIX Packaging Tool.

Application Publishing: With your MSIX package, you can now publish it using Citrix Studio. Make sure your Delivery Controllers are updated to the latest version to fully support MSIX.

Navigate to: https://download.laurel.ai/installer/windows/index.html
​

Click "Get the app"
​

After download is complete, double click the Laurel.Installer file and walk through each step for installation.
​
​Note: This method works well for individual users and the app will check for updates during each launch. It is our easiest and most simple way to install Laurel Assistant.

Uninstalling assistant by running the Powershell script below:

​Note: Powershell may need to be run in “Admin” mode.

Download the .msix file from: https://www.laurel.ai/downloads/windows

Install via Powershell using the following Powershell script:
​

After installation is complete you can now launch Assistant from the Start Menu. Under the About option you will see the new version installed
​
​Note: You can additionally launch the app as an administrator with the following Powershell command:
​

Download the .msix file this from: https://www.laurel.ai/downloads/windows

Once the x86.msix package is downloaded please use SCCM to deploy.

There are no additional switches required during deployment.

To verify that Laurel Assistant has been deployed it should appear as an application on the Users device and can be launched as normal

Log in to the Microsoft Endpoint Manager admin center.

Go to Apps > All apps and click Add.

Select the app type you want to deploy. Select "Windows 10 and later."

A wizard will ask you to configure information shared with users about your app. The default settings should be acceptable for most organizations, but feel free to edit as needed. Then, click "Next."

The second step, Configure app suite, is the place where the actual configuration takes place. Most of the settings are pretty self-explanatory, possibly except for the ones I list below, so let’s quickly discuss them:

Scope tags is an Intune feature that allows you to decide which admins in your organization will have access to a specific configuration or policy. To limit access to this Microsoft 365 Apps configuration and be able to select appropriate scope tags, you have to define and assign them to specific groups of users first. Learn more

Assignments is an important step. Here, you can decide for which users or on which devices the Microsoft 365 Apps will be installed (the Required section), available to install (the Available for enrolled devices section), or removed (the Uninstall section). If you would like to make assignments according to AAD groups (the Add group option), remember to create appropriate public AAD group(s) beforehand.

The last step, Review + create, allows you to review the whole configuration for Microsoft 365 Apps. If you’re fine with all the settings, click Create to start the deployment.

See Additional References: https://learn.microsoft.com/en-us/mem/intune/fundamentals/get-started-with-intune

Create a new Azure AD Domain Services (Azure AD DS).

Note: This is used to provide managed domain services such as domain join, group policy, lightweight directory access protocol (LDAP), and Kerberos/NTLM authentication.

To create an Azure AD DS, click on the Create button and input the required details.

Navigate to the Azure portal and search for Storage Accounts.

Then, click on Create and address the following:

You can further customize the storage as you wish, or continue by clicking on Review + Create.

Once the storage account is created, it’s time to add a new file share to it. Navigate to the created storage account and click on the File shares option.

Now, press the +File share button. This will bring up a window where you can input the Name of your share and which Tier you want to opt in for.

Click on the Review +Create button.

Navigate back to your Storage accounts, select File shares and click on the Active Directory button.

You will be prompted with a new window where you choose the Azure Active Directory Domain Services and click on Configure.

Check the Enable Azure Active Directory Domain Services (Azure AD DS) for this file share checkbox (in the upper right corner)

Navigate to the Storage accounts

Select your previously created storage account

Go to Access Control(IAM)

Click on Add and add the following roles:

Navigate to Azure Virtual Desktop and select your Host Pools.

In your host pool, you will see the MSIX Packages option. Click on the +Add option.

As you will see, this will require an MSIX image path - this path must correspond to the your storage account path that we previously created.

Add files to your Storage Account, navigate to the file share and click on Upload.

Note: The path that must be specified to MSIX App Attach is as follows:

Once the path is provided to Azure, a few options will appear such as Display name, Registration Type and State (it must be set to active).

To create the application group for assignment, click on Application Groups in your host pool.

Next, in the app group, select Applications and click on the +Add option:

Select your MSIX package from the list and press Save.

Note: The sync with AD will take some time, but the application will appear on your virtual machine after a few minutes.

See Additional References: https://learn.microsoft.com/en-us/azure/virtual-desktop/what-is-app-attach
​

First gather up all the installation files required and zip them up into a single zip file.

Save the zipped file to a location accessible when uploading to the KACE web interface.
​

Now, log into your KACE environment and pull up a current inventoried PC that already has all software in the zip file installed.

Under the Manage Operating Systems, ensure all OS versions you plan to distribute this version to are selected

Click on the Browse button, browse to and select the zipped file you have saved.
​

After selecting the file, change the Category and Threat Level as needed. Click Save button when finished.
​

Navigate to Home>Label Management, then click Labels

Complete Name, Description and selections for Restrict Label Usage To.

Navigate to Distribution > Managed Installations. Under File, click New.

Configure Name, Execution; choose the software from the drop down options (Choose the one you uploaded earlier)
​

Note that with Version 8 you can choose Cataloged Software or Software from the Software list. Your uploaded zip file will be associated under Software.
​

Now choose the installation commands. Most often you will choose Override Default Installation to include switches such as silent installation.
​

Under Deploy, click Manage Associated Labels and select the label you created for this distribution and click apply.
​

Configure Notifications to give the user warnings and completion messages.
​

Configure Schedules as needed (What times it is permitted to install and how many attempts until it reports failed, etc.) Click Save when complete.
​

Now apply the new Label to any device you wish to install it on. After the device inventories next, it will install per configured settings.
​

See Additional Resources: https://support.quest.com/kace-systems-deployment-appliance/9.2/technical-documents

​

​