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 the Entity_Enroll application 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

 

 

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.

 

  1. In Microsoft Configuration Manager, go to: 
    • Software Library » Application Management » Applications
       
  2. Select the previous myViewBoard application.
  3. On the bottom pane: 
    1. Open the Deployments tab. 
    2. Right-click each deployment. 
    3. Select Delete.
       
  4. Once all previous deployments are deleted:
    1. Right-click the application. 
    2. Select Retire.

 

 

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.msix
  • Microsoft.NET.CoreRuntime.2.2.appx
  • Microsoft.UI.Xaml.2.8.appx
  • Microsoft.VCLibs.x64.14.00.appx
  • Microsoft.VCLibs.x64.14.00.Desktop.appx

 

 

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.

 

  1. Download the following files: 
     The latest MSI installer for myViewBoard 3.0 
      The extraction script (ZIP)  
     
  2. Extract the contents of the ZIP file (the extraction script) in the same folder where the MSI installer was saved.
  3. Review the extracted files: two script files and one INSTRUCTIONS.txt file. 
  4. Follow the steps inside the INSTRUCTIONS.txt file to extract the target files out of the MSI installer. 
  5. Locate and copy the target files into your content folder.

   


   

Create Application Wizard

First, start Microsoft Configuration Manager to access the Create Application Wizard. 

 

  1. On the Start menu, access the location below to launch the program.

    📂 Microsoft Configuration Manager 
      └─» Configuration Manager Console

Start menu showing Configuration Manager Console under Microsoft Configuration Manager

Access Configuration Manager Console under Microsoft Configuration Manager on the Start menu

 

  1. Wait for the console to launch. On the left-hand menu: 
    1. Click on the Software Library option below. 
    2. Expand the Overview » Application Management folder. 
    3. Click on the Applications option inside the folder. 
    4. Click on the Create Application button on the ribbon.

 

Applications node with Software Library and Create Application highlighted

Click the Create Application button on the top ribbon.

 

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

 

 


General

Create Application Wizard with Manually specify the application information selected

Select the Manually specify the application information option.

General info

General Information page with the application name entered

On the General Information page, specify application details.

Deployment Types

Deployment Types page with the Add button

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.

 

  1. On the first General page:
    1. For Type, select Script Installer.
    2. Click Next.
       
  1. On the General Information page:
    1. For Name, specify Script.
    2. Click Next.
       
  1. On the Content page:

    1. For Content location: 
      Specify the network location of the myViewBoard folder you prepared earlier.
       
    2. For Installation program: 
      Type the following command. Replace the .msix file 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 
    3. 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" 
    4. Leave unchecked: 
      Run installation and uninstall program as 32-bit process on 64-bit clients
       
    5. Click Next.
       

 

  1. On the Detection Method page:
    1. Select Configure rules to detect the presence of this deployment type.
    2. Click Add Clause....

 

 


General

Create Deployment Type Wizard with Script Installer selected

Select Script Installer for Type.

General Info

General Information page with Name set to Script

Set Name to Script.

Content

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

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

Detection Method

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

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.

 

  1. On this new Detection Rule dialog, configure the rule with these values. 
    1. Set Setting Type to Registry.
    2. Set Hive to HKEY_LOCAL_MACHINE
    3. Set Key to:
      SOFTWARE\Microsoft\Windows\CurrentVersion\Appx\AppxAllUserStore\Applications\8df0095f-e86a-41f8-a95b-f78c4f33ef08_3.5.0.1144_x64__5nn9p46j8xz7t
      
    4. Leave blank/unchecked:
      • Value
      • This registry key is associated with a 32-bit application on 64-bit systems    
    5. 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. 

 

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

Configure the Detection Rule dialog.

 

 

  1. Back on the Detection Method page, click Next.
  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

Configure the User Experience page.

 

  1. On the Requirements page, click Next.
  1. 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_Enroll app as a dependency:
  1. Click Add to open a new dialog.
  2. For Dependency group name, type 1. 
  3. Click Add to configure the new dependency.

 

 

 

 

 


Add dependency

Add Dependency dialog with the dependency group name 1 entered

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

Dependencies

Dependencies page

Dependencies page with details.


  1. In the dialog that opens:
    1. Select Entity_Enroll.
    2. Select the Script checkbox for its deployment type.
    3. Click OK.
    4. Click OK again to close the Add Dependency dialog.
       
  1. Afterwards, back in the ‘Wizards’ dialogs: 
    1. On the Deployment Type Wizard: 
      • Click Next until you reach the Completion page. 
    2. On the Create Application Wizard: 
      • Click Next until you reach the Completion page. 

 

 

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:

 

  1. To distribute: 
    1. Right-click the new myViewBoard 3.5.0.1144 app.
    2. Select Distribute Content.
    3. Add your distribution point. If you created Entity_Enroll, distribute its content as well.
       
  2. To deploy: 
    1. Right-click the new myViewBoard 3.5.0.1144 app. 
    2. Select Deploy.
    3. Select a device collection that contains only the target devices. 
    4. Set Purpose to Required.
    5. Set the installation deadline to As soon as possible.
       
  3. To check deployment status:
    1. Go to Monitoring » Deployments.
    2. 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:

 

 

 

Verify on a client

Once complete, verify the deployment on each client.

 

  1. On the client, 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 the following log on the client:
    C:\Windows\CCM\Logs\AppEnforce.log

 

 

 

Upgrade to a new version

To upgrade, create a new application for the new version and configure it to supersede the previous one.

 

  1. Create a content folder for the new version. 
    See Prepare the content folder above.
     
  2. Create a new application for the new version by repeating the steps above. 
    Remember to update the placeholder values to match the new installer.
    1. Use the new .msix file name in the installation program.
    2. Use the new version number in the detection key.
       
  3. After creation:
    1. Right-click the new application. 
    2. 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.
     
  6. After deployment:
    1. Delete the deployments of the previous version. 
    2. Retire the previous application.

 

 

 

Remove myViewBoard

To remove myViewBoard from your devices:

 

  1. Delete the Install deployment of myViewBoard 3.5.0.1144.
  2. Right-click myViewBoard 3.5.0.1144: 
    1. Select Deploy. 
    2. 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.

 

 

Need additional help?

Check our other resources — we'll be happy to assist you.