Deploy myViewBoard 3.0 via SCCM

This article describes how to deploy myViewBoard 3.0 to Windows devices using a single DISM command and Microsoft Configuration Manager (SCCM). The command installs myViewBoard and its four framework packages together, so you only need one application in Configuration Manager, plus an optional application for myViewBoard Entity. It covers preparing the content folders, creating the applications, deploying, upgrading, and removing myViewBoard.

Before you begin

Confirm that the following requirements are met before proceeding.

• Configuration Manager console.

Access to the Microsoft Configuration Manager console, with permissions to create and deploy applications.

• Target devices.

Windows 10 version 2004 (build 19041) or later, or Windows 11 (64-bit), managed by the Configuration Manager client.

• Sideloading.

App sideloading must remain allowed. The Group Policy Allow all trusted apps to install (Computer Configuration » Administrative Templates » Windows Components » App Package Deployment) must not be set to Disabled. If you use AppLocker packaged app rules, they must allow packages from ViewSonic International Corporation and Microsoft Corporation.

• Microsoft Store.

Not required. Blocking the Microsoft Store does not affect this deployment.

• myViewBoard Entity (optional).

Devices must be able to reach https://api.myviewboard.com in the SYSTEM context.

No script changes needed
This method does not use PowerShell scripts, so you do not need to change the PowerShell execution policy in Client Settings.

Remove previous myViewBoard deployments

If myViewBoard was deployed before with Configuration Manager (for example, with the MSI installer or an earlier version of this guide), delete those deployments first so they do not conflict with the application in this article.

1. In Software Library » Application Management » Applications, select the previous myViewBoard application.
2. In the bottom pane, open the Deployments tab, right-click each deployment, and select Delete.
3. Right-click the application and select Retire.

⚠️
Warning
Do not create an Uninstall deployment. The application in this article installs over the existing myViewBoard.

Prepare the content folders

Create the following folders on a network share that the SCCM server can read. For example, \\SCCMServer\Packages. Configuration Manager downloads the entire content folder to each client, so keep each application in its own folder.

myViewBoard folder (for example, \\SCCMServer\Packages\myViewBoard):

Entity enroll folder (optional):

Version
This article uses version 3.5.0.1144 as an example. Replace it with the version you deploy.

Open the Configuration Manager console

From the Start menu, open Microsoft Configuration Manager » Configuration Manager Console.

Start menu showing Configuration Manager Console under Microsoft Configuration Manager

Create the Entity enroll application (optional)

Complete this section only if your organization uses myViewBoard Entity. Otherwise, skip to Create the myViewBoard application.

1. Select Software Library » Application Management » Applications.
2. Click Create Application.

Applications node with Software Library and Create Application highlighted

3. In the Create Application Wizard:
   1. Select Manually specify the application information.
   2. Click Next.

Create Application Wizard with Manually specify the application information selected

4. For Name:
   1. Type Entity_Enroll.
   2. Click Next until you reach the Deployment Types page.

General Information page with Name set to Entity_Enroll

5. On the Deployment Types page, click Add.

Deployment Types page with the Add button

6. In the Create Deployment Type Wizard:
   1. Set Type to Script Installer.
   2. Click Next.

Create Deployment Type Wizard with Script Installer selected

7. For Name:
   1. Type Script.
   2. Click Next.

General Information page with Name set to Script

8. For Content location, type the folder that contains vBoardInfoGet.exe and Newtonsoft.Json.dll.
9. For Installation program:
   1. Type the following command, replacing Your Entity Name with the name of your entity:

      "vBoardInfoGet.exe" ORGANIZATION="Your Entity Name"

   2. Click Next.

Content page with the content location and installation program entered

10. Select Configure rules to detect the presence of this deployment type.
11. Click Add Clause.

Detection Method page with Configure rules to detect the presence of this deployment type selected

12. Configure the detection rule with the following values:

12. Finish the wizard:
    1. Click OK.
    2. Click Next until the wizard completes.

Detection Rule dialog configured for the config.json file

Entity enrollment notes

• The content folder must contain both vBoardInfoGet.exe and Newtonsoft.Json.dll.
• Replace Your Entity Name with your organization name in myViewBoard Entity.
• Enrollment runs in the SYSTEM context and must be able to reach https://api.myviewboard.com. If your network uses a proxy, allow this traffic for the SYSTEM account.
• If enrollment fails, config.json is not created and Configuration Manager reports error 0x87D00324. Check C:\ProgramData\ViewSonic\Sparrow\myViewBoardEntity.log on the client.

Create the myViewBoard application

Create the application

1. Select Software Library » Application Management » Applications.
2. Click Create Application.

Applications node with Software Library and Create Application highlighted

3. In the Create Application Wizard:
   1. Select Manually specify the application information.
   2. Click Next.

Create Application Wizard with Manually specify the application information selected

4. Specify the application details:
   1. Type the following information:
      • Name: myViewBoard 3.5.0.1144
      • Publisher: ViewSonic Corporation
      • Software version: 3.5.0.1144
   2. Click Next.
5. Click Next until you reach the Deployment Types page, then click Add.

Deployment Types page with the Add button

Add the deployment type

1. In the Create Deployment Type Wizard:
   1. Set Type to Script Installer.
   2. Click Next.

Create Deployment Type Wizard with Script Installer selected

2. For Name:
   1. Type Script.
   2. Click Next.

General Information page with Name set to Script

3. For Content location, type the path to the myViewBoard folder from Prepare the content folders.
4. For Installation program, type the following command:

   DISM.exe /Online /Add-ProvisionedAppxPackage /PackagePath:myViewBoardV3_3.5.0.1144_x64.msix /DependencyPackagePath:Microsoft.NET.CoreRuntime.2.2.appx /DependencyPackagePath:Microsoft.UI.Xaml.2.8.appx /DependencyPackagePath:Microsoft.VCLibs.x64.14.00.appx /DependencyPackagePath:Microsoft.VCLibs.x64.14.00.Desktop.appx /SkipLicense

5. For Uninstall program, type the following command:

   powershell.exe -NoProfile -Command "Get-AppxProvisionedPackage -Online | Where-Object DisplayName -eq '8df0095f-e86a-41f8-a95b-f78c4f33ef08' | Remove-AppxProvisionedPackage -Online -AllUsers; Get-AppxPackage -AllUsers -Name 8df0095f-e86a-41f8-a95b-f78c4f33ef08 | Remove-AppxPackage -AllUsers"

6. Leave Run installation and uninstall program as 32-bit process on 64-bit clients unchecked, then click Next.

Content page with the content location, installation program, and uninstall program entered

⚠️
Important
Replace the .msix file name in the installation program with the file name of the version you deploy. The 32-bit option must stay unchecked, because the 32-bit DISM cannot service 64-bit Windows.

Configure the detection method

1. Select Configure rules to detect the presence of this deployment type.
2. Click Add Clause.

Detection Method page with Configure rules to detect the presence of this deployment type selected

3. Configure the detection rule:
   1. Set Setting Type to Registry.
   2. Set Hive to HKEY_LOCAL_MACHINE.
   3. For Key, type the following path:

      SOFTWARE\Microsoft\Windows\CurrentVersion\Appx\AppxAllUserStore\Applications\8df0095f-e86a-41f8-a95b-f78c4f33ef08_3.5.0.1144_x64__5nn9p46j8xz7t

   4. Leave Value blank.
   5. Leave This registry key is associated with a 32-bit application on 64-bit systems unchecked.
   6. Select This registry setting must exist on the target system to indicate presence of this application.
   7. Click OK.

Detection Rule dialog with the registry key entered in the Key field

4. Click Next.

⚠️
Important
The last part of the key is the package full name of myViewBoard: 8df0095f-e86a-41f8-a95b-f78c4f33ef08_<version>_x64__5nn9p46j8xz7t. For another version, change only the version number.

Complete the wizard

1. On the User Experience page:
   1. Set Installation behavior to Install for system.
   2. Set Logon requirement to Whether or not a user is logged on.
   3. Set Installation program visibility to Hidden.
   4. Click Next.

User Experience page with Install for system, Whether or not a user is logged on, and Hidden selected

2. On the Requirements page, click Next.
3. On the Dependencies page, if you created Entity_Enroll:
   1. Click Add.
   2. For Dependency group name, type 1, then click Add.

Add Dependency dialog with the dependency group name 1 entered

3. Select Entity_Enroll, select the Script checkbox for its deployment type, then click OK. 4. Click OK.

4. Click Next until the wizard completes.

Deploy myViewBoard

1. Right-click myViewBoard 3.5.0.1144 and select Distribute Content, then add your distribution point. If you created Entity_Enroll, distribute its content as well.
2. Right-click myViewBoard 3.5.0.1144 and select Deploy.
3. Select a device collection that contains only the target devices, set Purpose to Required, and set the installation deadline to As soon as possible.
4. Go to Monitoring » Deployments and confirm that the target devices report Success.

For the full steps to deploy an application to a collection, refer to the Microsoft documentation:

Deploy applications with Configuration Manager

⚠️
Warning
Do not deploy to built-in collections such as All Desktop and Server Clients. They also contain servers, including the site server.

Verify on a client

1. Open PowerShell as administrator and run:

   Get-AppxProvisionedPackage -Online | Where-Object DisplayName -eq '8df0095f-e86a-41f8-a95b-f78c4f33ef08'

2. Confirm the output shows Version 3.5.0.1144.
3. If the installation fails, check C:\Windows\CCM\Logs\AppEnforce.log on the client.

Signed-in users
Users who are already signed in when myViewBoard is installed need to sign out and sign in again before it appears in the Start menu.

Upgrade to a new version

1. Create a content folder for the new version. See Prepare the content folders.
2. Create a new application for the new version. See Create the myViewBoard application. Use the new .msix file name in the installation program and the new version number in the detection key.
3. Right-click the new application and select Properties.
4. On the Supersedence tab:
   1. Click Add.
   2. Select the previous myViewBoard application and its deployment type.
   3. Leave Uninstall unchecked.
   4. Click OK.
5. Deploy the new application to the same collection. See Deploy myViewBoard.
6. Delete the deployment of the previous version, then retire the previous application.

⚠️
Important
If the deployment of the previous version is kept, Configuration Manager tries to install the previous version again after the upgrade, and the installation fails.

Remove myViewBoard

1. Delete the Install deployment of myViewBoard 3.5.0.1144.
2. Right-click myViewBoard 3.5.0.1144, select Deploy, and set Action to Uninstall for the same collection.

The uninstall program removes myViewBoard for all users. The four framework packages stay installed, because other apps can use them.

Draft notes (remove before publishing)

The items below could not be confirmed from the source guide. Resolve them before this article goes live.

1. Screenshots reused from the Entity section. The Entity and main application sections share the same wizard screenshots, but the Entity Content and Detection Rule images show Entity values. The main application's Content screenshot shows the install and uninstall commands.
2. Screenshot gaps. The source has no screenshots for the application details page (Name, Publisher, Software version), the Dependencies page selection of Entity_Enroll, deployment, upgrade, or removal.
3. Content location example. The source screenshots show \\cm1\packages$\myViewboard, while the text uses \\SCCMServer\Packages\myViewBoard. Align them if you want.
4. Sensitive values. The Entity Content screenshot has the entity name blacked out. Confirm that is intended.
5. Console screenshot. The Create Application screenshot is the cleaned version used in the MSIX article. The Start menu screenshot was not bordered.
6. Version example. The source uses 3.5.0.1144. Consider aligning with the latest release.
7. Entity_Enroll deployment. The source does not say when or to which collection Entity_Enroll should be deployed.
8. Requirements. Supported Configuration Manager versions are not stated in the source.