Mass Distributing the Laptop Package Using Third Party Tools in an AD Environment

You can mass distribute and install the laptop package using a third-party software, such as Microsoft System Center Configuration Manager (SCCM) or Jamf software.

Installation Using an Authorization Code

If you created an installation user and entered those credentials to create the package, those credentials will be used to install the software.

Note

When you install with either an excluded installation user or an authorization code, the Edge Monitor on the client will query the AD server from the client and give the current logged on user's logon name and email to the CommServe database.

If the logged on user is associated with a plan in the Command Center, then during activation, the associated plan is assigned to the laptop.

If the logged on user is not associated to any plan, then the default plan is assigned to the laptop.

Before You Begin

If you want to install the package by using an authorization code, activate the authorization code in the Command Center:
- To activate an authorization code to be used by all clients in the CommCell, see Activating an Authorization Code for Software Installation in the CommCell.
- To activate an authorization code to be used by all clients in a company, see Activating an Authorization Code for Tenant Software Installation - MSP self-service.
If you need to configure Full Disk Access for macOS laptops, see macOS Mojave Version 10.14: Considerations.

Procedure

Configure the third-party software to run the following command from the folder containing the laptop package contents.

Windows

Windows packages use a self-extracting executable that can be launched using a deployment tool with command line. The package must be pushed to the machine locally before running the command line. Running the package remotely over the network is not supported.
```
 
WindowsEndpoint32.exe /silent /install /silent /authcode authcode
```
```
 
WindowsEndpoint64.exe /silent /install /silent /authcode authcode
```
Where authcode is the authorization code. The authorization code is required if the package does not contain user credentials for an installation user.

Optionally, to hide the Edge Monitor application and Commvault shortcuts from the end users, enter /hideapps.
```
 
WindowsEndpoint32.exe /silent /install /silent /authcode authcode /hideapps
```
```
 
WindowsEndpoint64.exe /silent /install /silent /authcode authcode /hideapps
```
Macintosh Operating System (macOS)

Silent macOS packages use the macOS pkg framework. These can be directly placed into the Jamf Casper software to run anytime. The package does not take arguments on command line, so you need to create a text file with the arguments, on the local macOS computer.

On the local macOS computer, create an "install.ini" file in the global application support directory:
- Path to the ini file: /Library/Application Support/Commvault/install.ini
- Parameters inside the ini file:
  - AUTH_CODE="######"
  - HIDE_APPS="YES"
    
    Note
    
    Add the optional HIDE_APPS parameter to hide the Edge Monitor application and Commvault shortcuts from the end-users.
After creating the text file, you can push the macOS.pkg package to the client.
```
 
sudo installer -pkg path_to_pkg -target /
```
UNIX Operating System

For silent install on a UNIX machine, perform the following steps:
1. Extract the tar file.
```
tar -xvf LinuxEndpoint.tar
```
  A pkg folder is created on the computer.
2. Go to the pkg folder.
```
cd pkg
```
3. Run the installer.
```
 
sudo ./silent_install -p default.xml -authcode authcode
```
  Where authcode is the authorization code. The authorization code is required if the package does not contain user credentials for an installation user.
For interactive or semi-silent install on a UNIX machine, use the following:
```
 
./cvpkgadd –authcode authcode
```
Where authcode is the authorization code. The authorization code is required if the package does not contain user credentials for an installation user.

For a list of installer error codes, see Installer Error Codes.

Results

The laptop is auto-activated and the discovered user, which is the logged on user, is assigned as the owner of the laptop.

Installation Using a Plan Name

When you mass distribute and install the laptop package, you can specify the plan name that you want to assign to the laptops.

During activation, the laptop is automatically assigned to the specified plan, but the logged in user account is not assigned as the client owner for the laptop, automatically.

Procedure

Configure the third-party software to run the following command from the folder containing the laptop package contents.

Windows

Windows packages using a self extracting executable which can be launched using a deployment tool with command line. The package must be pushed to the machine locally before running the command line. Running the package remotely over the network is not supported.
```
 
WinX64_Client.exe /silent /install /silent /authcode authcode /plan planname
```
Where authcode is the authorization code which is required if you did not enter the installation user's credentials when the package was created.

To obtain the authorization code, go to Command Center Companies > Company name > General or Administration > General.
Macintosh Operating System (macOS)

Silent macOS packages are built using the macOS pkg framework. These can be directly placed into the Jamf Casper software to run anytime. The package does not take arguments on command line, so you need to create a text file with the arguments, on the local macOS computer.

On the local macOS computer, create an "install.ini" file in the global application support directory.

Path to the ini file: /Library/Application Support/Commvault/install.ini

Parameter inside the ini file:

AUTH_CODE="######"

PLAN_NAME="Plan name"

After creating the text file, you can push the macOS.pkg package to the client.
```
sudo installer -pkg <path_to_pkg> -target /
```

Result

The laptop is auto-activated, but the logged in user account is not assigned as the owner of the laptop, automatically. To set the client owner assignment, see User Permissions and Administration for Laptop Backups.