Lockdown Browser 1.0.7.02 LAB SCCM deployment

I needed to update from Respondus LockDown Browser Lab version 1.0.5.14 to version 1.0.7.02. This is how I've done it as an SCCM application. This could probably be modified to be used in some other deployment solution, but I've tested it with SCCM 2012 R2 and Windows 7 clients running 32 and 64 bit versions.

After 1.0.7.02 was activated this error shows on 1.0.5.14

Install Shield files and installer folder

First, you'll need to create setup.iss files. Instructions can be found here: http://www.respondus.com/update/2009-11-d.shtml

Here's their instructions for convenience:

First, be sure that Respondus LockDown Browser isn’t already installed on the computer. If it is, then un-install it before continuing.
  1. Download the full installer (LockDownSFX.exe) from the Respondus website. BE SURE to obtain the .exe via the admin login for your institution since the installer differs for each institution.
  2. Run the installer and select the "Click Here" link that appears next to the text, "Problems with the installation program?" This will allow you to extract the setup files to a folder on your local disk (such as "lockdown").
  3. Start the Windows Command Prompt (or run CMD.exe).
  4. Change directories to where the installer was extracted (i.e. the “lockdown” folder).
  5. From the command line run:

    setup /r

    This runs the regular installer but also creates c:\windows\setup.iss
  6. Copy the file c:\windows\setup.iss into the “lockdown” folder.
  7. Un-install Respondus LockDown Browser.
Now you now have a silent installer that can be run using this command:
setup /s /f1"%CD%\setup.iss"

Create three iss files using the same method, setup /r inside the expanded installer files. You will use each of these iss files later in SCCM; the normal silent install won't work to upgrade existing versions, and the third one will be used for uninstallation.

  1. Normal install with no other version installed - named setup.iss
  2. A re-install with version 1.0.5.14 installed - named update.iss
  3. An uninstall of 1.0.7.02 - named uninstall.iss

Put all of the iss files in the installer folder with setup.exe etc.


Install script

Create a bat file with the contents below named installLDB.bat. See in-line comments for what it's doing. Basically it is checking if version 1.05 is installed, running with the update iss file, and otherwise installing with the setup file. The last part is changing the registry entry for versioning because for some reason Respondus doesn't like to do this in their installer. We will also use that key in SCCM for detection.


@echo off

REM Check registry for version 1.0.5
REG QUERY HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{3DEC3ECB-D6FB-450E-8248-D05C36AD5FA4} /f "DisplayVersion" | find "1.0.5"
IF %ERRORLEVEL% == 1 goto newinstall
IF %ERRORLEVEL% == 0 goto update


REM If doesn't exist as 1.0.5 run new install
:newinstall
setup /s /f1"%CD%\setup.iss"
goto registry

REM if exists with version 1.0.5 run update
:update
setup /s /f1"%CD%\update.iss"

:registry
REM Update registry to show version 1.0.7.02 instead of 1.0.5
REG QUERY HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{3DEC3ECB-D6FB-450E-8248-D05C36AD5FA4} /f "DisplayVersion" | find "1.0.5"
IF %ERRORLEVEL% == 1 goto end
REG ADD HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{3DEC3ECB-D6FB-450E-8248-D05C36AD5FA4} /v DisplayVersion /t REG_SZ /d 1.0.7.02 /f

:end


You may want to verify that the registry key matches what actually shows when it is installed. Also create a bat file named uninstall.bat with the line below and copy to your installation folder.


setup /s /f1"%CD%\uninstall.iss"


Copy the folder to your network share or SCCM server.

SCCM Application

Create a new Application (not package). I'm not going to show how to create an application step by step here, but I've included the settings I used, everything else is default. This part is pretty straight forward if you've done it before, and these details are easily viewed for verification after the application is created by going to the application properties.

Name: Respondus LockDown Browser 1.0.7.02 LAB
Administrator Comments: Will update from 1.0.5 or perform a clean install, tested on Windows 7 64 and 32 bit, might not update other versions
Publisher: Respondus
Software Version: 1.0.7.02
Localized Application Name: Respondus LockDown Browser 1.0.7.02 LAB
Localized description: Respondus LockDown Browser 1.0.7.02 for labs only
Deployment type: script

Script
   Name: Lockdown Browser 1.0.7.02
   Content location: [enter UNC path to the folder you copied]
   Installation program: "InstallLDB.bat"
   Uninstall program: "uninstall.bat"
   Run as 32 bit on 64: CHECKED

Detection Method
   Setting Type: Registry
   Hive: HKEY_LOCAL_MACHINE
   Key: SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{3DEC3ECB-D6FB-450E-8248-    D05C36AD5FA4}
   Value: DisplayVersion
   Associated with 32-bit: CHECKED
   Data Type: String
   Operator: Equals
   Value: 1.0.7.02

Install for System
Whether or not a user is logged on
Installation visibility: Normal
Max allowed run time: 20
Estimated installation: 5


It's important to check run as 32 bit on 64 bit machines, and associated with 32 bit in the detection method, or you will have problems on 64 bit Windows.

Deploy (test first) your application and you're done.


Another solution
http://windowsmasher.wordpress.com/2012/03/17/sccm-package-respondus-lockdown-browser/

More about reg command
http://technet.microsoft.com/en-us/library/cc732643.aspx

Respondus LockDown Browser silent install - updated instructions
http://support.respondus.com/support/index.php?/Knowledgebase/Article/View/136/0/does-the-lockdown-browser-lab-edition-support-silent-or-unattended-installs-under-windows

InstallShield Parameters
http://helpnet.installshield.com/installshield18helplib/IHelpSetup_EXECmdLine.htm

Create System Center Configuration Manager Application
http://technet.microsoft.com/en-us/library/gg682159.aspx

Comments

Post a Comment

Popular posts from this blog

Simple powershell ping log with timestamp

Here's a quick and dirty script that will ping with a timestamp, and save the ouput to a text file. I have used pingInfoView quite a bit, but sometimes this fits the situation better. $hostAddress = Read-Host -Prompt 'IP Address or Hostname' $fileName = Read-Host -Prompt 'Output file' ping.exe -t $hostAddress|Foreach{"{0} - {1}" -f (Get-Date),$_}| Tee-Object -file $fileName
Read more

DNS entries needed for MLB app

I have a pi-hole DNS server and fairly aggressive block lists from https://firebog.net/ . The MLB TV android app was crashing until I whitelisted this google entry. It looks like it's for serving ads in the app. imasdk.googleapis.com These other entries can stay blocked and the app still worked. X   api.onesignal.com X   mlb.sc.omtrdc.net X   api.branch.io X   assets.adobedtm.com X   mlb.siteintercept.qualtrics.com X   udm.scorecardresearch.com X   b.scorecardresearch.com X   datadoghq.eu X   demdex.net X   app-measurement.com X   conviva.com
Read more

OBi 200/202 no audio but call connects

Image
After installing a Palo Alto PA-220 with standard policies, there were several things that were broken. VOIP phone through Google Voice/OBi analogue - no audio on any call (STUN over port 19305) Speedtest.net find server and tests would not complete (SSL over port 8080) Our washer and drier were no longer sending notifications when laundry was done (SSL over 46030) External Plex server (SSL over port 32400) The offender was the default outbound policy to the internet/WAN. While the source/destination are any/any, the Service specified is application-default which basically means that if services are using non-standard ports they won't be allowed in this policy. There weren't any indications of dropped traffic in the logs, because default policies are not logged in Palo Alto devices by default, and this traffic was getting denied by the interzone-default policy. To resolve this easily, just change application-default to any. However, you may want to see wha...
Read more