Skip to content

Commit 68d2b31

Browse files
Update linux-install-manually.md
1 parent 4bdf9e6 commit 68d2b31

File tree

1 file changed

+3
-40
lines changed

1 file changed

+3
-40
lines changed

defender-endpoint/linux-install-manually.md

Lines changed: 3 additions & 40 deletions
Original file line numberDiff line numberDiff line change
@@ -55,6 +55,8 @@ A successful deployment requires the completion of all of the following tasks:
5555

5656
Before you begin, see [Prerequisites for Defender for Endpoint on Linux](mde-linux-prerequisites.md) for a description of prerequisites and system requirements for the current software version.
5757

58+
For installation at a custom path, refer to [Prerequisites and system requirements for custom path installation](linux-custom-path-installation.md#prerequisites-and-system-requirements).
59+
5860
> [!WARNING]
5961
> Upgrading your operating system to a new major version after the product installation requires the product to be reinstalled. You need to [Uninstall](linux-resources.md#uninstall-defender-for-endpoint-on-linux) the existing Defender for Endpoint on Linux application, upgrade the operating system, and then reconfigure Defender for Endpoint on Linux following the steps in this article.
6062
@@ -261,46 +263,7 @@ In order to preview new features and provide early feedback, it's recommended th
261263
## Pre Install Setup for Custom Path Installation
262264

263265
These steps are applicable only if Defender is to be installed in a custom location.
264-
265-
The custom installation path is denoted here as <custom_path>
266-
267-
> [!NOTE]
268-
> Only absolute custom installation path is supported
269-
270-
1. Create the required directories for setup
271-
```bash
272-
sudo mkdir -p <custom_path>
273-
sudo mkdir -p /etc/opt/microsoft/mdatp
274-
```
275-
276-
2. Create the config json file `/etc/opt/microsoft/mdatp/mde_path.json`, specifying the custom installation path, in the mde config directory
277-
278-
File Content:
279-
```
280-
{"path":"<custom_path>"}
281-
```
282-
283-
For example, if the custom installation path is to be set as `/custom/microsoft_mdatp`, `/etc/opt/microsoft/mdatp/mde_path.json` will be created with the following content:
284-
```
285-
{"path":"/custom/microsoft_mdatp"}
286-
```
287-
3. Set required permissions
288-
```
289-
chmod 755 <custom_path>
290-
chmod 644 /etc/opt/microsoft/mdatp
291-
```
292-
293-
4. Create a symlink to the installation location
294-
```
295-
mkdir -p /opt/microsoft
296-
mkdir -p <custom_path>/opt/microsoft/mdatp
297-
ln -sf <custom_path>/opt/microsoft/mdatp /opt/microsoft/mdatp
298-
```
299-
> [!NOTE]
300-
>
301-
> If you choose to skip creation of symlink, you can rely on the installer package to create the symlink for you, provided you have -
302-
> 1. 1GB space in /opt or
303-
> 2. You have managed the disk space check issue at your end
266+
For detailed instructions on installing Microsoft Defender for Endpoint to a custom path, see [Manual installation: Pre-installation setup](linux-custom-path-installation.md#manual-installation-pre-installation-setup).
304267

305268
## Application installation
306269

0 commit comments

Comments
 (0)