The agents are installed automatically in the end-user's device and the installable gets deleted after a successful installation. This is used in places where there is minimal restriction on bandwidth consumption. Agents can be automatically installed in LAN network or in a remote office having a Distribution Server.

• From Web Console: Automate agent installation from the product web console
• Using SoM Policy: Agents get automatically installed in new machines when they are added to Active Directory
• Remote agent installation: Install agents in remote office with or without a Distribution Server

When there are numerous roaming users which move out of the network periodically or when there is bandwidth constraints, the installable can be downloaded and placed in a shared folder.

• Download agent installable

For enterprises which have new machines to be managed and where the required operating system has to be deployed, the agent can be deployed with the OS. 

• Windows OS imaging
• Mac OS imaging
• Linux OS imaging

When an enterprise has an Active Directory Domain based setup with numerous endpoints to be managed, the agent can be installed using the Group Policy Object.

• Using GPO light-weight tool: Simplest method to install agent in an Active Directory based network
• Using GPO scheduler: Fastest method to install the agent. Agents will be installed in the next refresh cycle
• Using GPO start-up script: Most common method of agent installation using GPO

When there are numerous endpoints in a workgroup based setup in an enterprise, using IP ranges, agents can be deployed in bulk to all the devices.

• IP ranges: Agent can be installed using IP address or IP ranges or using computer names

Agent installer files can be easily accessed from a common central location. There is no need for transferring complete agent installer files to all devices in a network.

• Network share installation

The product server can be hosted in cloud using Microsoft Azure or AWS. The agents can be deployed in Azure AD and AWS instances.

• In Azure AD environment: Agents can be installed with Intune or Azure automation Service
• To AWS instances: Agents can be deployed in bulk in AWS

When there is no need for manual intervention, agents can be installed in a silent manner. Silent command can also be used to install agent from any other third party tool.

• Steps for silent installation

1. Open the MDT Workbench application. 
2. Click the Application->New Application option. 

3. Select "Application with source files"

4. Enter the details of the target application 

5. Indicate the location of the source folder and click next

6. Enter a destination folder name.

Enter the command line for silent installation:

LocalOffice_Agent.exe /silent

Verify the summary and click finish, the application will be added to the list of apps. 

1. Navigate to the Agent tab > Agent Installation > Other methods > Download the zip folder present under SCCM tab.
2. Extract the UEMSAgent.msi and UEMSAgent.mst,, and paste them in a shared path accessible by all the computers you want to install the agent on.

-Kindly include DCAgentServerInfo.json file only if the build version is 10.1.2124.1 and above.

-Kindly include DMRootCA.crt and DMRootCA-Server.crt files only if the build version is 10.0.653 and above.

3. Change the shared path location as mentioned in the batch file, and create an SCCM package with this script.
4. Now, open System Center Configuration Manager (SCCM) and navigate to Software Library --> Overview--> Application Management -->Packages.
5. Right click on Packages and from the options listed, select Create Packages.
6. This will launch Create Package and Program Wizard window, in which you will be asked to fill in the necessary information like Name, Description, Manufacturer, etc.

7. Enable the checkbox This package contains source files. Select Network path and enter the path of the shared folder as shown below.

8. Select Architecture as x86 (if available) and the program type as Standard and click Next.

9. Fill in the necessary information, as shown in the image below and click Next.

10. Review the requirements and ensure they are like as shown in the image below and click Next.

11. After reviewing, confirm the settings to proceed to create the package

12. The package has been created successfully.

13. The package can now be deployed to the end user's computers.

You have now successfully installed agents in target endpoints using SCCM.