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. |
• |
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. |
• |
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. |
• |
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: |
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++. |
• |
Ensure the WinRM version is greater than 2.0. |
2 |
• |
Configure Kerberos on Linux machine: |
• |
• |
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. |
This section includes the following topics:
1 |
In the Navigation pane, click Guided Configuration, and then on the NetVault Configuration Wizard page, click Install Software/Add Clients. |
2 |
3 |
Click Manage Stores, and provide the following details. |
Select CIFS. | |
Provide the Uniform Naming Convention (UNC) path of the CIFS (Common Internet File System) share. The format for specifying the path for a Windows-based server is: 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.
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). | |
Specify a user account that can be used to access the CIFS share using one of the following formats: | |
4 |
You can update the UNC path or user credentials for an existing package store.
1 |
In the Navigation pane, click Guided Configuration, and then on the NetVault Configuration Wizard page, click Install Software/Add Clients. |
2 |
3 |
Click Manage Stores, and in the package store list, select the applicable package store. |
5 |
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Conditions d’utilisation Confidentialité Cookie Preference Center