This section includes the following topics:
You can run push installation tasks from the NetVault WebUI. When the task starts, a deployment agent is installed on the remote machines. The agent copies the installation packages from a shared location and performs silent installations on the machines. The agent also sends status messages to the server. By default, the client logs are preserved on the target machine. For more information about how to modify this setting, see Configuring default settings for Deployment Manager. You can view the task status from the WebUI. After the packages are successfully installed on the machines, the WebUI automatically adds the new clients to the NetVault Server.
By default, NetVault runs a maximum of 50 concurrent push-installation processes. You can modify the default settings to increase the number of concurrent processes. For more information, see Configuring default settings for Deployment Manager.
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: |
• |
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: |
• |
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Feedback Conditions d’utilisation Confidentialité Cookie Preference Center