NetVault 13.0.1 - Administration Guide

Prerequisites

Before you start the push installation procedure, verify that the following requirements are met:

•

Copy the packages to a shared location: Copy the client and plug-in packages to a shared location. Only CIFS shares, including Linux Samba Shares, are currently supported as package stores. The path must be accessible to the NetVault Server and all target machines where you want to install the packages.

Ensure that you use the original names of the installation packages. Renamed packages cannot be selected for push installations.

•

Configure a package store in NetVault: After copying the installation packages, configure the shared location details in NetVault. For more information, see Configuring a package store.

•

Configure the preferred network address setting on multihomed NetVault Servers: On multihomed NetVault Servers, configure the Preferred Network Address setting to allow the remote clients to send status messages to the correct address. For more information about this setting, see Configuring network addresses for multihomed machines.

If the remote clients fail to contact the server on the correct address, the task status is not updated on the server. In such cases, the clients are not added to the server and the task either remains in the Running state or completes with warnings.

•

Verify that the firewall is configured to allow traffic through the ports required for push installation: To push the client and plug-in packages to a remote Windows machine, the NetVault Server establishes the initial WMI session with the remote machine using RPC over port 135. All further WMI traffic uses the dynamic port range of 49152 through 65535.

To push the client and plug-in packages to a remote Linux machine, the NetVault Server establishes an SSH connection with the remote machine over port 22.

If there is a firewall between the server and the remote client, ensure that these ports are opened to allow the WMI RPC traffic to pass through the firewall. Also ensure that an inbound rule is created for the HTTP or HTTPS listen port that is configured on the NetVault Server.

When pushing the NetVault client installation to a Linux machine, you need the following additional prerequisites:

•

Grant the proper access: The user must have root-level access, with the NOPASSWD flag set in the sudoers file on the remote Linux machine. To complete this prerequisite, add one of the following entries to the sudoers file:

<username> ALL=NOPASSWD: ALL

<username> ALL=(ALL) NOPASSWD: <users home directory [/home/username or

/home/domainname/username]>/nvpushinstall/nvclientinstaller


	NOTE: If user fails to get sudoers privilege from the sudoers file, the deployment task will always be in the running state with Request sent to launch installation agent on the remote machine message.

•

Affirm the password authentication: In the sshd_config file, set the PasswordAuthentication entry to yes.

•

If you are not using the default cipher setting, then support for aes128-ctr should be present. If it is not, then you must add aes128-ctr at the end of the list following a comma in the etc/ssh/sshd_config file.

•

Install libstdc++: If you are pushing the hybrid installation package of the NetVault client on a 64-bit Linux machine, you must first install the 32-bit version of libstdc++.

When you push the NetVault client from a Linux machine to Windows machine, you need the following additional prerequisites:

•

Ensure the WinRM version is greater than 2.0.

•

Check WinRM on Windows client machine to verify Kerberos value:

Run the following command as an administrator in command line interface to open the config file.

winrm get winrm/config

Check the Kerberos value in the Auth section is set to true:

Kerberos = true

•

When using push install as a local user, ensure that the following WinRM configurations exist on the target Windows machine:

•

Under Service:

AllowUnencrypted="true"

•

Under Service/Auth:

Basic="true"

For more information on Installation and configuration for Windows Remote Management, see,

https://docs.microsoft.com/en-us/windows/desktop/winrm/installation-and-configuration-for-windows-remote-management.

•

Configure Kerberos on Linux machine:

•

Run the following command to open the krb5 config file:

vi /etc/krb5.conf

In the libdefaults section set the following value:

default_realm=<EXAMPLE.COM>

default_ccache_name = KEYRING:persistent:%{uid}

•

When using domain user for push installation from a Linux machine to a Windows machine, mention the target machine in FQDN format. When using local user, mention the IP address of the target machine.

•

During Push installation specify the domain suffix (for example: domain.com or domain.local) for the same account name or DL format.

Managing package stores

This section includes the following topics:

•

Configuring a package store

•

Modifying a package store

•

Removing a package store

Configuring a package store

A package store is a shared location used for storing NetVault Client and plug-in binary files for push installations. Only CIFS shares, including Linux Samba shares, are currently supported as package stores. You can set up a package store in NetVault by providing the path and user credentials for the CIFS share.


	NOTE: Quest recommends using shared folders instead of shared drives as package stores for NetVault.

To configure a package store:

In the Navigation pane, click Guided Configuration, and then on the NetVault Configuration Wizard page, click Install Software/Add Clients.

On the Machines to Be Added as Clients page, click Install Software.

Click Manage Stores, and provide the following details.

Option

Description

Store Name

Provide a display name for the package store.

You cannot change the store name after it is configured.

Type

Select CIFS.

Location

Provide the Uniform Naming Convention (UNC) path of the CIFS (Common Internet File System) share.

NOTE: Do not use hyphens in the folder names of the package store path. Underscores are acceptable.

The format for specifying the path for a Windows-based server is:

\\<server>\<share name>

The format for specifying the path for a Linux-based server is:

NOTE: //<server>/<share name>To reduce the time it takes to browse the package store for automatic upgrades, locate the shared folder in a minimal directory hierarchy.

Verify that the path is accessible to the NetVault Server and all target machines where you want to install the packages.

NOTE: On the Windows-based server, if the server IP address is used to configure a local package store (for example, \\10.11.12.3\PkgStore), the user credentials are not validated when the package store is added or updated. If you specify invalid credentials, no errors are reported. However, the deployment task fails if the authentication fails and the packages cannot be retrieved from the store. Therefore, Quest recommends that you use the server name when configuring the path to a local store (for example, \\WinServer1\PkgStore).

User Name

Specify a user account that can be used to access the CIFS share using one of the following formats:

•

•

•

Password

Specify the password for the user account.

Click Add to add the store, and then click OK.