Has anybody tried deploying solstice? I've tried the Autopkgr deployments and copying the app from a working machine into composer and every time I deploy to another machine, the icon has a line through it saying it's "Not supported on this type of Mac"
You have to modify permissions in my experience. Use the stub installer to download the full .app, put it in a custom package to install in /Applications/Solstice.app and have the post install script do a chown to current user and run a chmod -R 755 on it to be safe. This will at least allow any user to read/launch the app, which I have found to be the issue in the past when packaging for deployment. I am not worried too much about the permissions in my environment, as we have one user per computer, and everyone is authorized to use solstice within our environment.
Also......you don't NEED the solstice app in my experience, you can just airplay to connect to the solstice hub...
I'm still having issues with this. I've gone to mersive.com/download and downloaded the zip file. You open it, then it decompresses from that app and puts the actual solstice app on the desktop. I take that file put it in Composer as a new pkg, set root/admin permissions to go to the users application folder however it does not work. Any suggestions?
Also, be aware that if the user ever enables the "Automatically Share Audio With Desktop" setting it will prompt for admin credentials to install a Kernel Extension. To avoid this I add a PostInstall script (below), to call their kext installation script embedded in the Solstice app, to my Composer created package as well.
This assumes your package installs the Solstice Client to the main /Applications folder.
#!/bin/sh ## postinstall chmod ugo+x /Applications/Solstice Client.app/Contents/Resources/SolsticeAudioDeviceInstall.sh /Applications/Solstice Client.app/Contents/Resources/SolsticeAudioDeviceInstall.sh /Applications/Solstice Client.app/Contents/Resources/SolsticeAudioDevice.kext
The first line makes sure the script SolsticeAudioDeviceInstall.sh is executable because I have had issues in the past where that is not set properly by Solstice.
The second line calls the SolsticeAudioDeviceInstall.sh script with the main argument being the path to the .kext file that needs to be installed.
Haven't had anyone request that (yet), but thanks for posting this - I'll probably run it as a post-install script in Jamf if it ever comes up.
FYI, for those of us following along at home and wanting/needing to whitelist kexts, the TeamIdentifier for Mersive Technologies is 63B5A5WDNG.
@spalmer Looks like Mersive's dev team neglected to add the proper shebang (
#!/bin/bash) to the embedded shell script. Your script is spot on, thanks for sharing. Here's their whole embedded script...
IFS=$'' kextunload /System/Library/Extensions/SolsticeAudioDevice.kext rm -r /System/Library/Extensions/SolsticeAudioDevice.kext cp -R $1 /System/Library/Extensions chmod -R 755 /System/Library/Extensions/SolsticeAudioDevice.kext chown -R root:wheel /System/Library/Extensions/SolsticeAudioDevice.kext kextload /System/Library/Extensions/SolsticeAudioDevice.kext
@pitcherj thanks for the KEXT whitelist Team ID, here is the command in case anyone lands on this page:
# codesign -dr - /Applications/Solstice Client.app Executable=/Applications/Solstice Client.app/Contents/MacOS/SolsticeClient designated => identifier "com.mersive.solstice.client" and anchor apple generic and certificate 1[field.1.2.840.1136184.108.40.206.6] /* exists */ and certificate leaf[field.1.2.840.1136220.127.116.11.13] /* exists */ and certificate leaf[subject.OU] = "63B5A5WDNG"
Looks like Mersive changed the installation method for the Solstice app again. There's an executable in the download /SolsticeClientMacWeb.app/Contents/MacOS/SolsticeClientInstallerMac that installs the client onto the user's desktop, with the correct permissions, so the client now installs via an installer application.
When I package the download up and deploy it, it never appears in the Applications folder. Has anyone found a way to install this from Jamf without having to make a custom package to deploy it to a different directory than /Applications?