Deploying the ClickView App for Windows 10

The following steps run through a basic deployment of the ClickView App for Windows 10 utilising a GPO script that runs upon User Login.

We have used Windows Server 2012 R2 for this deployment - this deployment method has also been tested and verified as fully operational on Windows Server 2016.

1. Click here to download the latest MSI package.

2. Log on to your institution's Active Directory Domain Controller (DC)

3.  We will be deploying the ClickView App through a PowerShell script that will run at User Login.

In preparation for this deployment, we need to create a shared folder and browse to the UNC path of this - 'Users' will need have 'Read & Execute', NTFS permissions to the shared folder that we have created.

In this scenario, I have created a new shared folder for this deployment on the root of 'C:\' named 'Rollouts' > Assigned the relevant NTFS permissions to the 'Rollouts' folder and then placed the 'ClickViewApp.MSI' file that we will be deploying within the root of the 'Rollouts' folder:

4. We now need to verify that the 'Rollouts' folder and ClickView App MSI is accessible over UNC path.

To verify this, launch 'Run' and type in the UNC path of your DC (or the machine you will be deploying from) in our case, the server we will be deploying from is named 'cvts-adfs' so we will specify "\\cvts-adfs"

Upon typing this in to 'Run' you should be presented with all shared folders that currently exist on the machine.

As we can see from the screenshot below the 'Rollouts' folder that we created is visible and accessible over UNC path:

Upon accessing this folder we can see the 'ClickViewApp.msi' file that we will be deploying:

We have successfully confirmed that the shared folder and the ClickView App MSI file is accessible over a shared UNC path.

5. We now need to create a script which will install the ClickView App for Windows 10 upon a user initially logging in to the machine using their domain credentials.

In this scenario we will be creating an 'msiexec' script that will run upon user login through Windows PowerShell.

Launch the 'Notepad' application > In our particular example, the 'msiexec' command will be as follows:

msiexec.exe /i \\cvts-adfs\rollouts\ClickViewApp.msi /quiet

You will simply need to amend the "\\cvts-adfs\rollouts\ClickViewApp.msi" section to that of your own UNC path where the ClickViewApp MSI resides - the rest of the script should be structured the same:

msiexec.exe /i \\yourdeploymentserver\yoursharedfolder\ClickViewApp.msi /quiet

You now need to save the notepad file you have created within the shared folder that you created and that the ClickView MSI is located in.

As this script will run using PowerShell we will be saving it as a '.ps1' file:

6.  Click on Start, then Administrative Tools, then Group Policy Management.

7.  Expand Forest, then click on Domains, then the [domain.name] of the domain that you will be deploying to > Group Policy Objects > in this scenario we will be deploying the ClickView App through the Default Domain Policy > Right click on this and select the 'Edit' option.

Note: If you do not wish to deploy through the 'Default Domain Policy' GPO, you can simply create a new GPO for deployment by right-clicking on 'Group Policy Objects' > 'New GPO'

8.  In the context menu, expand 'User Configuration' > 'Windows Settings' > 'Scripts' (Logon/Logoff) > 'Logon' > Display Properties

9.  Within the 'Logon Properties' area select 'PowerShell Scripts' > 'Add' > 'Browse'

Important: When browsing to the script that we created in Step 4 of this article, we must locate the script over UNC path, rather than through the local path.

As we can see in the screenshot below, I have located this by specifying '\\cvts-adfs\Rollouts' and then selecting the 'ClickViewApp.ps1' file:

The script will now appear within the 'Script Name' section and clearly display the UNC path to the .PS1 file location:

We do not need to add any 'Script Paramaters' to this.

Once you have confirmed the script name is correct and shows the UNC path of the ClickView App .PS1 file you can proceed to click 'OK'

The script we have just added will now be visible:

You will see we have also selected to 'Run Windows PowerShell Scripts first' - setting this ensures the script runs during the users logon and helps prevent any undue delays.

10. We have successfully setup a script to run at user login which should automatically install the ClickView App for Windows 10 automatically.

Upon logging in to a Windows 10 machine using domain credentials, we should see a 'ClickView' icon appear within 5-20 seconds and then be able to seamlessly use the ClickView App for Windows 10 by double-clicking on the Desktop Shortcut.

Download the latest Appx file for Windows 10 

Alternatively you can download the latest MSI installer.

Requirements

• ClickView Appx file for Windows 10 - ClickView will provide to this to you upon request
  
  
• Windows 10 build 10586 or newer.

• Devices that you will be installing this to will need to be unlocked for sideloading (unlock policy must be enabled on each device)

• Certificate assigned to app - the certificate can be found within the attachment that ClickView provided

And here's what you'll need to do:

• Turn on sideloading - you can push a policy with an MDM provider, or you can use Settings > Update and Security > For Developers > Sideload Apps
  

• Trust the app - import the security certificate to the local device

• Install the app - using PowerShell, SCCM or any other method that your institution has knowledge of

Comprehensive information on how to sideload Apps can be found at the Microsoft MSDN website page below:

Sideloading Apps using DISM (Windows PowerShell)