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 |
1 |
In the Navigation pane, click Guided Configuration, and then on the NetVault Configuration Wizard page, click Install Software/Add Clients. |
2 |
3 |
4 |
In the Select Packages for Deployment window, select the installation packages that you want to use: |
• |
• |
For NetVault plug-in packages, expand Select plug-in packages, and then select the appropriate “.npk” binary file that you want to use. |
5 |
On the Machines to Be Added as Clients page, next to Machines, click the add (+) drop-down list, and select a method for adding the deployment targets. |
6 |
In the Add Machines window, on the Machine Details tab, enter the following details based on your method selection. |
To manually add the deployment targets, select this method. On the Machine Details tab, provide the following details:
Optionally, if you want NetVault to remember the password for this user name, select Save Credential. | |||||||||
Click Next.
Press Enter.
If the remote Windows machine is in a workgroup, you can also use a local account with administrative privileges. However, to use a local administrator account, disable the User Account Control: Run all administrators in Admin Approval Mode setting. For security reasons, disabling this setting is not recommended; using the built-in Administrator account is the recommended approach. | |||||||||
To select machines from an Active Directory Domain, select this method. On the AD Details tab, provide the following details:
Optionally, if you want NetVault to remember the password for this user name, select Save Credential. Click Connect. In the list of Active Directory Objects, select the target machines, and then click Next. | |||||||||
To import the target list from a file, select this method. In the Add machines from file dialog box, click Select a file. After selecting the file in the browse window, click OK to upload the file. For more information about the file format, see File format for specifying deployment targets. |
NOTE: The Installation Settings, Client Settings, and Firewall Settings are only effective when a machine is being added as a client for the first time. If a machine is already added to the server, these settings are not used for that machine. |
On the Installation Settings tab, provide the following details:
If multiple clients are selected from an Active Directory Domain, the label changes to Machine Name Prefix. The machine name that you provide is used as the base name, and NetVault adds “_n” to the base name while assigning client names. For example, if the Machine Name is “WinClient,” the clients are assigned the names WinClient_1, WinClient_2, … WinClient_n. If you leave the field blank, NetVault uses the host names.
\ and spaces.
Click Next. | |||||||||
On the Client Settings tab, provide the following details:
Click Next. | |||||||||
If the client resides on a network that is outside the firewall, select the Client is Outside Firewall check box on the Firewall Settings tab, and provide the TCP/IP port specifications. For more information, see About firewall settings. |
9 |
If you are performing an upgrade installation on any client, select the Allow existing NetVault client installations to be upgraded check box. |
• |
Click Verify to ensure connectivity to the clients. If any errors are reported, click Edit, and modify the applicable installation parameters. |
• |
11 |
NOTE: The installer generates a log file in the system temporary directory. (The TEMP environment variable for system account determines the location of this directory; this path is typically set to %windir%\Temp.)
The log file is named as follows: netvault_{GUID}_install.log, where {GUID} is unique for each installation occurrence (for example, netvault_274bffb2-a3c1-457e-7f5e-221bf60a7689_install.log). |
You can specify the following fields in the input file.
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Terms of Use Privacy Cookie Preference Center