Deploying LogMeIn via Casper

pmcgurn
New Contributor III

I found several sparse tidbits on deploying LogMeIn, so I figured I'd share.

The script should be a simple drop-in to JSS 9.7 to deploy the LogMeIn software. It downloads the latest version of the client, rather than having you package a stale version. You could fairly easily modify it if you want ot manually control versions, but this was fine for our needs.

To use:
1. Add to Casper Admin/JSS like any normal script
2. In your Policy, set varible #4 (deployid) to be your Deployment ID (see note)
3. Deploy silently or advertise via Self Service

Note
In order to get a Deployment ID, you need to be using LogMeIn Central.
1. Log in to Central
2. Create a new Deployment
3. The ID is the "c" URL parameter in the link that the deployment will generate

#!/bin/sh
############################################
#   LogMeIn for Mac silent deployment script
#   In order to use, you must be a subscriber of LogMeIn Central
#
#   To get a Deploy ID, log in to Central, click Deployments, then create a new one
#   Customize the settings as you see fit
#   The Deploy ID is part of the URL that is generated
#   ex. https://secure.logmein.com/i?l=en&c=xyz
#   xyz is the Deploy ID
#
#   Tested on OS X 10.10.5 (Yosemite) with JSS 9.73
############################################

############################################
#   Set the deploy ID via command line argument
#   
#
DEPLOYID=$4  #Change to 1 if not using Casper Suite
#
echo "Deploy ID is: $DEPLOYID"
############################################

echo "Running LogMeIn host install"

# Change working directory to /tmp
cd /tmp

# Clean up any existing LogMeIn install files first
rm -rf /tmp/LMI

# Create working folder, LMI doesn't like being in the root of /tmp
mkdir LMI
cd LMI

# Download LogMeIn Mac  software
echo "Downloading LogMeIn installer"
curl -O https://secure.logmein.com/LogMeInInstallerMac.zip

# Extract the installer
echo "Unzipping LogMeIn installer"
unzip LogMeInInstallerMac.zip

# Get the versioned file name
FILE="$(ls | grep LogMeIn*.app)"
echo "File name is: $FILE" 

# Write the deploy ID as an extended attribute on the install package
echo "Setting deploy ID as attribute"
xattr -w com.logmein.deployid $DEPLOYID "$FILE"
echo "Reading deploy ID attribute to confirm"
xattr -p com.logmein.deployid "$FILE"

# Run the silent install
echo "Running the LogMeIn installer"
./"$FILE"/Contents/MacOS/Lili --silent

# Remove temp files
echo "Cleaning up temp files"
rm -rf /tmp/LMI

echo "Exiting with success"
exit 0
6 REPLIES 6

k_akuffo
New Contributor

AMAZING!
Thanks

pbenton
New Contributor II

has anyone used this with 10.11?

had a package with installer app and post flight script close to this. no longer works in 10.11for some reason.

thanks
Paul

d2techsupport
New Contributor

Good day all. I wanted to update this to let everyone know that I was able to make this work on 10.11.6 with JSS 9.93.1469132907.c : hosted server. I was able to run it as is. I had a little confusion on the "In your Policy, set variable #4 (deployid) to be your Deployment ID (see note)" I had to make a batch file within logmein central and then copy the unique ID for Line 4. Hope this helps anyone else out there trying to deploy LMI via a deployment package from LMI Central.

dsampley
New Contributor

I wanted to post that I have made use of this today and the script works fine. Thank you for sharing this with the group.

25CW25
New Contributor II

I got the command from logmeincentral below:

msiexec.exe /i LogMeIn.msi DEPLOYID=01_fxbvgtml9pcdbf7q3sq04iw3u3p7zfny2vrmp INSTALLMETHOD=5 FQDNDESC=1

so is my deploy ID is 01? or is it 01_fxbvgtml9pcdbf7q3sq04iw3u3p7zfny2vrmp

and do I modify the script below to be like this?

Set the deploy ID via command line argument

DEPLOYID=$01_fxbvgtml9pcdbf7q3sq04iw3u3p7zfny2vrmp #Change to 1 if not using Casper Suite

EDIT: I got it to work! The deployID is the entire string so in this example, DeployID is: 01_fxbvgtml9pcdbf7q3sq04iw3u3p7zfny2vrmp and I was confused as another poster mentioned of the ID4 in the policy. To clarify for those that are new to JAMF, when you create a new policy, and point to this new script, at the section where Parameter 4 is where you enter the DeployID string.

nstefanelli56
New Contributor II

Guys this is awesome! Thanks so much for everyone that has given their feedback and various tips here.

Install works without an issue. However, I still run into the issue where I have to approve accessibility control via sysprefs. Has anyone managed to identify a way to automate this?