Deploy myViewBoard via SCCM
This article describes how to deploy myViewBoard 3.0 to Windows devices using a single DISM command via Microsoft Configuration Manager (SCCM). The command installs myViewBoard and its four framework packages together.
Before you begin
Before proceeding, verify that you already have the following requirements set up.
-
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.
-
myViewBoard Entity (optional).
If your organization uses myViewBoard Entity, create theEntity_Enrollapplication first. For more details, see the following article:
Entity enrollment via SCCM
-
Sideloading.
- App sideloading must remain allowed.
- If you use AppLocker packaged app rules, they must allow packages from ViewSonic International Corporation and Microsoft Corporation.
- The Group Policy Allow all trusted apps to install must not be set to Disabled. To verify, navigate to the following location in Group Policy:
Computer Configuration » Administrative Templates » Windows Components » App Package Deployment
⚠️
Important
This guide assumes that the admin is already familiar with SCCM deployment, as it mainly focuses on the settings required to complete the Create Application Wizard and Create Deployment Type Wizard setup screens.
For more detailed steps on app deployment, kindly refer to the official Microsoft documentation for SCCM.
Remove previous deployments
If myViewBoard was deployed before with Configuration Manager, delete those deployments first so they do not conflict with the application in this article.
- In Microsoft Configuration Manager, go to:
-
Software Library » Application Management » Applications
-
Software Library » Application Management » Applications
- Select the previous myViewBoard application.
- On the bottom pane:
- Open the Deployments tab.
- Right-click each deployment.
- Select Delete.
- Once all previous deployments are deleted:
- Right-click the application.
- Select Retire.
⚠️
Warning
Do not create an Uninstall deployment. The application in this article installs over the existing myViewBoard.
Prepare the content folder
Create a folder on a network share that the SCCM server can read. For example, \\SCCMServer\Packages\myViewBoard. Note that Configuration Manager will download the entire contents of this folder to each client.
Place the following files in the folder:
myViewBoardV3_<version>_x64.msixMicrosoft.NET.CoreRuntime.2.2.appxMicrosoft.UI.Xaml.2.8.appxMicrosoft.VCLibs.x64.14.00.appxMicrosoft.VCLibs.x64.14.00.Desktop.appx
⚠️
Important
This article uses version 3.5.0.1144 as an example. Replace it with the version you deploy, for example myViewBoardV3_3.5.0.1144_x64.msix.
How to get these files
Perform one of the following:
Contact ViewSonic Support
To obtain a copy of the target files, submit a request at the following URL:
https://myviewboard.com/support
When submitting your request:
- Select myViewBoard.
- Specify the required files and their intended use for SCCM deployment.
Manually extract the target files from the MSI
Since this will extract multiple files, we recommend performing the steps below in a temporary folder.
- Download the following files:
The latest MSI installer for myViewBoard 3.0
The extraction script (ZIP)
- Extract the contents of the ZIP file (the extraction script) in the same folder where the MSI installer was saved.
- Review the extracted files: two script files and one
INSTRUCTIONS.txtfile. - Follow the steps inside the
INSTRUCTIONS.txtfile to extract the target files out of the MSI installer. - Locate and copy the target files into your content folder.
Create Application Wizard
First, start Microsoft Configuration Manager to access the Create Application Wizard.
- On the Start menu, access the location below to launch the program.
📂 Microsoft Configuration Manager
└─» Configuration Manager Console

Access Configuration Manager Console under Microsoft Configuration Manager on the Start menu
- Wait for the console to launch. On the left-hand menu:
- Click on the Software Library option below.
- Expand the Overview » Application Management folder.
- Click on the Applications option inside the folder.
- Click on the Create Application button on the ribbon.

Click the Create Application button on the top ribbon.
- This action opens the Create Application Wizard dialog.
On the first page:- Select Manually specify the application information.
- Click Next.
- On the General Information page:
- For Name, type
myViewBoard 3.5.0.1144. - For Publisher, type
ViewSonic Corporation. - For Software version, type
3.5.0.1144. - Click Next until you reach the Deployment Types page.
- For Name, type
- On the Deployment Types page, click Add.
General

Select the Manually specify the application information option.
General info

On the General Information page, specify application details.
Deployment Types

On the Deployment Types page, click the Add button.
Deployment Type Wizard
Once you click Add, the Create Deployment Type Wizard opens. Use this wizard to specify the commands that should run during deployment.
- On the first General page:
- For Type, select Script Installer.
- Click Next.
- On the General Information page:
- For Name, specify
Script. - Click Next.
- For Name, specify
- On the Content page:
- For Content location:
Specify the network location of the myViewBoard folder you prepared earlier.
- For Installation program:
Type the following command. Replace the.msixfile name with the file name of the version you deploy.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 - 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" - Leave unchecked:
Run installation and uninstall program as 32-bit process on 64-bit clients
- Click Next.
- For Content location:
*
Important
The 32-bit option must stay unchecked, because the 32-bit DISM does not work properly on 64-bit Windows for this procedure.
- On the Detection Method page:
- Select Configure rules to detect the presence of this deployment type.
- Click Add Clause....
General

Select Script Installer for Type.
General Info

Set Name to Script.
Content

Provide details for the Content location, Installation program and Uninstall program fields.
Detection Method

Click Add Clause… on the Detection Method page.
Once you click the Add Clause… button, a new Detection Rule dialog opens. Use this dialog to specify how the app verifies if the same version is already installed, in order to prevent double installation.
- On this new Detection Rule dialog, configure the rule with these values.
- Set Setting Type to Registry.
- Set Hive to HKEY_LOCAL_MACHINE
- Set Key to:
SOFTWARE\Microsoft\Windows\CurrentVersion\Appx\AppxAllUserStore\Applications\8df0095f-e86a-41f8-a95b-f78c4f33ef08_3.5.0.1144_x64__5nn9p46j8xz7t - Leave blank/unchecked:
- Value
- This registry key is associated with a 32-bit application on 64-bit systems
- Select the option:
This registry setting must exist on the target system to indicate presence of this application.
Click OK to save and close the dialog.

Configure the Detection Rule dialog.
*
Change KEY version
Note that the last part of the key is the full package name of the myViewBoard app to be deployed: 8df0095f-e86a-41f8-a95b-f78c4f33ef08_<version>_x64__5nn9p46j8xz7t
The <version> placeholder in this key must match the version you deploy. For another version, change only the version number.
- Back on the Detection Method page, click Next.
- On the User Experience page:
- Set Installation behavior to Install for system.
- Set Logon requirement to Whether or not a user is logged on.
- Set Installation program visibility to Hidden.
- Click Next.

Configure the User Experience page.
- On the Requirements page, click Next.
- On the Dependencies page, perform one of the following:
↪ If you do not need to enroll devices to your entity:
- Click Next until the wizard completes.
↪ If you need to enroll devices to your entity:
- Add the
Entity_Enrollapp as a dependency:
- Click Add to open a new dialog.
- For Dependency group name, type
1. - Click Add to configure the new dependency.
*
Create and deploy the Entity_Enroll app
For steps on how to create the Entity_Enroll app, see the article below:
Add dependency

Set the Dependency group name to 1, then click Add.. to configure.
Dependencies

Dependencies page with details.
- In the dialog that opens:
- Select Entity_Enroll.
- Select the Script checkbox for its deployment type.
- Click OK.
- Click OK again to close the Add Dependency dialog.
- Afterwards, back in the ‘Wizards’ dialogs:
- On the Deployment Type Wizard:
- Click Next until you reach the Completion page.
- On the Create Application Wizard:
- Click Next until you reach the Completion page.
- On the Deployment Type Wizard:
Distribute and deploy
The myViewBoard app should now appear on your application list. Use the standard procedures to distribute and deploy your new app. For a quick summary of the process and recommended settings, see the list below:
- To distribute:
- Right-click the new myViewBoard 3.5.0.1144 app.
- Select Distribute Content.
- Add your distribution point. If you created Entity_Enroll, distribute its content as well.
- To deploy:
- Right-click the new myViewBoard 3.5.0.1144 app.
- Select Deploy.
- Select a device collection that contains only the target devices.
- Set Purpose to Required.
- Set the installation deadline to As soon as possible.
- To check deployment status:
- Go to Monitoring » Deployments.
- Confirm that the target devices report Success.
Follow the onscreen intructions for each procedure until you reach the Completion page. For more detailed information on how to deploy an application to a collection, refer to the official Microsoft documentation here:
⚠️
Warning
Do not deploy to built-in collections such as All Desktop and Server Clients. These also contain servers, including the site server.
Verify on a client
Once complete, verify the deployment on each client.
- On the client, open PowerShell as administrator and run:
Get-AppxProvisionedPackage -Online | Where-Object DisplayName -eq '8df0095f-e86a-41f8-a95b-f78c4f33ef08'
- Confirm the output shows Version
3.5.0.1144. - If the installation fails, check the following log on the client:
C:\Windows\CCM\Logs\AppEnforce.log
⚠️
Deployed app is missing in client's Start menu
Users who were already signed in when myViewBoard was installed need to sign out and sign in again before it appears in the Start menu.
Upgrade to a new version
To upgrade, create a new application for the new version and configure it to supersede the previous one.
- Create a content folder for the new version.
See Prepare the content folder above.
- Create a new application for the new version by repeating the steps above.
Remember to update the placeholder values to match the new installer.- Use the new
.msixfile name in the installation program. - Use the new version number in the detection key.
- Use the new
- After creation:
- Right-click the new application.
- Select Properties.
- On the Supersedence tab:
- Click Add.
- Select the previous myViewBoard application and its deployment type.
- Leave Uninstall unchecked.
- Click OK.
- Deploy the new application to the same collection.
- After deployment:
- Delete the deployments of the previous version.
- Retire the previous application.
⚠️
Important
If the deployments of the previous version are not removed:
After the upgrade, Configuration Manager may try to re-install the previous version. This attempt usually fails. You can also follow the steps here:
Remove myViewBoard
To remove myViewBoard from your devices:
- Delete the Install deployment of myViewBoard 3.5.0.1144.
- Right-click myViewBoard 3.5.0.1144:
- Select Deploy.
- Set Action to Uninstall for the same collection.
The uninstall program removes only myViewBoard for all users. The other four framework packages stay installed, since these packages can also serve as dependencies for other apps.