LanSchool provides the ability to mass deploy the LanSchool student client for Mac OS through the creation of a custom installation package. Once this package has been created, you will be able to use your software distribution system to push the package out and install it.
Creating a Custom Installer Package
The LanSchool Student .DMG allows you to create a custom installer package that can be used for mass deployment of the LanSchool student client on Mac OS. In order to do this, follow these steps:
- Download the student.dmg file from the Lenovo Software Customer Portal.
- Mount the student.dmg by double clicking on it.
- Click on "Create a Custom Package"
- Depending on your macOS version, you may receive a security warning. Click Open.
- Follow the Customer Packager Wizard to determine what settings this custom package will apply to student device
- Name the file and navigate to the directory you wish to save the package. Click Save.
- Once the package is created, you will receive a notification upon completion.
Deploying the Custom Package
Using a remote software deployment tool (e.g. ARD, JAMF), deploy the LanSchool custom installer package to student devices. The specific steps will vary depending on the deployment tool you are using. Please refer to your vendor's documentation.
The LanSchool package should always be installed as the root user or equivalent. When the client package has finished installing, the client will start running automatically.
Browser Extension Profiles for macOS 11.0 (Big Sur)
Apple’s latest operating system
macOS 11.0 (Big Sur) prevents 3rd party software from installing Profiles on the
Mobile Device Management (MDM)
has the ability to install profiles, but anyone else who
previously installed them to configure application settings will no longer be able to do so in macOS
LanSchool Classic for many years has
installed profiles to specify Chrome, and now Edge Browser settings, specifically so
that our browser extensions are installed and cannot be removed.
For Big Sur and greater, we
recommend adding our Chrome and Edge policies to your MDM settings for those browsers:
In XML this would look like this:
In XML this would like like this:
Our Edge policies also configure two
other settings in the browser that you may find desirable in an education
1.Disable Developer Tools. These tools can be used to subvert extensions
and other things.
2. Disable Private Browsing. Our extension cannot record private browsing
in any reliable way.