The customer.inf setup is only available for the Barracuda VPN Client. It requires administrator rights on the target system.

Transcription

1 In this Article: Preparing a The customer.inf setup is only available for the Barracuda VPN Client. It requires administrator rights on the target system. Customer.inf setup is a comprehensive installation method, allowing you to fully preconfigure all Network Access Client settings on multiple installation systems remotely. This method addresses the experienced system administrator. In addition to pure installation and basic configuration, it allows you to: Preconfigure an arbitrary number of connection profiles on the Network Access Client. Import license (.lic) files and X.509 certificates into the Network Access Client. Import preconfigured rule sets into the Personal Firewall. Exemplary script files required for (customer.inf, silent.cmd) are available on the Application thumb drive or on the Template Code: Customer Install Files (customer.inf) [1] page, allowing you to adapt the remote configuration procedure. Proceed as follows to prepare a completely customized setup: Edit the customer.inf file. For more information on this, see [2]. Edit the silent.cmd file. For more information on this, see [3]. Copy the following files to the folder containing the setup.exe file: 1. customer.inf 2. silent.cmd 3. active.i_fwrule (optional) 4. [LicenseName].lic (optional) 5. [CertificateName].pem (optional) Execute the silent.cmd file. The customer.inf File The syntax examples below are partly arranged in abstracts only. If needed as template, refer to the full exemplary customer.inf file found on this [4] page. The customer.inf file directs the copying of required files and the insertion of registry entries. It is divided into three sections of interest (Customer Areas): Section 1: Customer Area / [PhionCustomerCopyFiles] [5] Section 2: Customer Area / [CustomerReg] [6] Section 3: Customer Area / [SourceDisksFiles] [7] Do not rename the customer.inf file. 1 / 8

2 Remove nonessential parameters from the customer.inf file before applying it for custom setup. Both files customer.inf and silent.cmd are adapted for inclusion of a customer.lic file. If you are not importing a license (.lic) file during installation, delete the corresponding entries in both files. If you are using another name for the.lic file, do not forget to respectively edit the installation files. The content of the customer.inf file is treated case sensitive. Section 1: Customer Area / [PhionCustomerCopyFiles] Example for Section [PhionCustomerCopyFiles] [PhionCustomerCopyFiles] ; destination-file-name[,source-file-name][,temporary-file-name][,flag] customer.inf,,,2 ; important, do not remove<br/>customer.lic,,,2 ; if importing a license file<br/>active.i_fwrule,,,2 ; if importing a firewall rule set Optionally, the following file directives may be detailed: Directive destination-file-name source-file-name temporary-file-name File Directives Applicable in the Customer Area / [CustomerCopyFiles] Comment Name of the destination file. If no source-file-name is given, this specification is also the name of the source file. Name of the source file. If the source and destination file names for the file copy operation are the same, source-file-name can be omitted. Name of a temporary file to be created in the copy operation, if a file of the same name on the destination is open or currently in use. Only used on Windows 9x/Me platforms. The NTbased operating system automatically generates temporary file names when necessary and renames the copied source files the next time the operating system is started. flags These optional flags, expressed in hexadecimal notation or as a decimal value in a section entry, can be used to control how (or whether) a particular source file is copied to the destination. One or more (ORed) values for the following system-defined flags can be specified, but some of these are mutually exclusive: 0x <br/>(COPYFLG_REPLACEONLY) 0x <br/>(COPYFLG_NODECOMP) 0x <br/>(COPYFLG_FORCE_FILE_IN_USE) Copy the source file to the destination directory only if the file is already present in the destination directory. Copy the source file to the destination directory without decompressing the source file if it is compressed. Force file-in-use behavior. Do not copy over an existing file of the same name if it is currently open. Instead, copy the given source file with a temporary name so that it can be renamed and used when the next reboot occurs. 2 / 8

3 0x <br/>(COPYFLG_NO_OVERWRITE) 0x <br/>(COPYFLG_REPLACE_BOOT_FILE) 0x <br/>(COPYFLG_NOPRUNE) 0x <br/>(COPYFLG_NO_VERSION_DIALOG) 0x <br/>(COPYFLG_NOVERSIONCHECK) 0x <br/>(COPYFLG_OVERWRITE_OLDER_ONLY) 0x <br/>(COPYFLG_WARN_IF_SKIP) 0x <br/>(COPYFLG_NOSKIP) Do not replace an existing file in the destination directory with a source file of the same name. This flag cannot be combined with any other flags. This file is required by the system loader. The system will prompt the user to reboot the system. Do not delete this operation to effectuate optimization. For example, Setup might determine that the file copy operation is not necessary because the file already exists. However, the writer of the INF knows that the operation is required and directs Setup to override its optimization and perform the file operation. This flag can be used to ensure that files are copied if they are also specified in an INF DelFiles directive or an INF RenFiles directive. Do not overwrite a file in the destination directory with the source file if the existing file is newer than the source file. This flag is irrelevant to digitally signed INF files. If a driver package is digitally signed, Setup installs the package as a whole and does not selectively omit files in the package based on other versions already present on the machine. Ignore file versions and overwrite existing files in the destination directory. This flag and the next two are mutually exclusive. This flag is irrelevant to digitally signed INF files. Copy the source file to the destination directory only if the file on the destination will be superseded by a newer version. This flag is irrelevant to digitally signed INF files. Send a warning if the user selects to not copy a file. This flag and the next are mutually exclusive, and both are irrelevant to INF files that are digitally signed. Do not allow the user to skip copying a file. This flag is implied if the driver package is signed. Do not change the name of the firewall rule set entry (active.i_fwrule). If you do not intend installing the Personal Firewall with a predefined rule set meeting company policy, uncomment or delete this line. Section 2: Customer Area / [CustomerReg] This section controls the configuration of profiles set up during installation. Profile settings are saved to HKEY_USERS\.DEFAULT\Software\Phion\phionvpn\Profile. The structure is the following: HKU,.DEFAULT\Software\Phion\phionvpn\Profile\1,dhcp,0x ,1<br/> Registry Path<br/> Profile Path<br/> - Profile ID For automated VPN profile creation, the following syntax is applicable in the customer.inf file: 3 / 8

4 reg-root, [subkey], [value-entry-name], [flags], [value] This section is used for creating profiles and defining default values. Directive reg-root HKCR HKCU HKLM HKU subkey value-entry-name Directives Applicable in the Customer Area / [CustomerReg] Comment Identifies the root of the registry tree for other values supplied in this entry. The value can be one of the following: Abbreviation for HKEY_CLASSES_ROOT. Abbreviation for HKEY_CURRENT_USER. Abbreviation for HKEY_LOCAL_MACHINE. Abbreviation for HKEY_USERS. Optional; formed either as a %strkey% token defined in a Strings section of the INF or as a registry path under the given reg-root (key1\key2\key3 ), specifies one of the following: A new subkey to be added to the registry at the end of the given registry path. An existing subkey in which the additional values specified in this entry will be written (possibly replacing the value of an existing named value entry of the given subkey). Both a new subkey to be added to the registry together with its initial value entry. Optional; either names an existing value entry in the given (existing) subkey or creates the name of a new value entry to be added in the specified subkey, whether it already exists or is a new key to be added to the registry. This value can be expressed either as "quoted string" or as a %strkey% token that is defined in the INFs Strings section. (If this is omitted for a string-type value, the value entry name is the default unnamed value entry for this key.) The operating system supports some system-defined special value-entryname keywords. See the end of this comments section for more information. 4 / 8

5 value Optionally specifies a new value for the specified value-entry-name to be added to the given registry key. Such a value can be a replacement value for an existing named value entry in an existing key, a value to be appended (flag value 0x ) to an existing named REG_MULTI_SZ-type value entry in an existing key, a new value entry to be written into an existing key, or the initial value entry for a new subkey to be added to the registry. The expression of such a value depends on the registry type specified for the flag as follows: A registry string-type value can be expressed either as a "quoted string" or as a %strkey% token defined in a Strings section of the INF file. Such an INF-specified value must not include a NULL terminator at the end of each string. A registry numerical-type value can be expressed as a hexadecimal (using 0x notation) or decimal number. flags Optional hexadecimal value, expressed as an ORed bitmask of system-defined low word and high word flag values, defines the data type for a value entry and/or controls the add-registry operation. Bitmask values for each of these flags are as follows: 0x <br/>(FLG_ADDREG_BINVALUETYPE) 0x <br/>(FLG_ADDREG_NOCLOBBER) 0x <br/>(FLG_ADDREG_DELVAL) 0x <br/>(FLG_ADDREG_APPEND) 0x <br/>(FLG_ADDREG_KEYONLY) 0x <br/>(FLG_ADDREG_OVERWRITEONLY) 0x <br/>(FLG_ADDREG_64BITKEY) 0x (FLG_ADDREG_KEYONLY_COMMON) 0x <br/>(FLG_ADDREG_32BITKEY) The given value is raw data. This value is identical to the FLG_ADDREG_TYPE_BINARY. Prevent a given value from replacing the value of an existing value entry. Delete the given subkey from the registry, or delete the specified value-entry-name from the specified registry subkey. Append a given value to that of an existing named value entry. This flag is valid only if FLG_ADDREG_TYPE_MULTI_SZ is also set. The specified string value is not appended if it already exists. Create the given subkey, but ignore any supplied value-entry-name and/or value. Reset to the supplied value only if the specified value-entry-name already exists in the given subkey. Make the specified change in the 64-bit registry. If not specified, the change is made to the native registry. Only Windows XP and later. Same as FLG_ADDREG_KEYONLY but also works in a del-registry-section (see INF DelReg Directive). Only Windows XP and later. Make the specified change in the 32-bit registry. If not specified, the change is made to the native registry. Only Windows XP and alter. 5 / 8

6 0x <br/>(FLG_ADDREG_TYPE_SZ) 0x (FLG_ADDREG_TYPE_MULTI_SZ) 0x <br/>(FLG_ADDREG_TYPE_EXPAND_SZ) 0x <br/>(FLG_ADDREG_TYPE_DWORD) 0x <br/>(FLG_ADDREG_TYPE_NONE) REG_SZ. Note that this is the default type for a specified value entry, so the flag's value can be omitted from any regroot line in an add-registry section that operates on a value entry of this type. REG_MULTI_SZ. This specification does not require any NULL terminator for a given string value. REG_EXPAND_SZ. REG_DWORD. REG_NONE. The following describes only the minimum required information. You may add any other Barracuda Networks registry entry. 1. Edit Default Entry HKU,.DEFAULT\Software\Phion\phionvpn\Profile\1, Default, 0x , 1 Value 1 sets a profile to the default profile of the Barracuda VPN Client. All other profiles take the value Edit DHCP Entry HKU,.DEFAULT\Software\Phion\phionvpn\Profile\1, dhcp, 0x , 1 Editing this value changes the value of the Virtual Adapter Configuration parameter: Assign IP address manually Use internal DHCP assignment (default) Direct assignment 3. Edit Profile Name HKU,.DEFAULT\Software\Phion\phionvpn\Profile\1, description, 0x , "profile name" 4. Name the License (customer.lic) HKU,.DEFAULT\Software\Phion\phionvpn\Profile\1, license, 0x , "%65600%\customer.lic" %65600% is used as a placeholder for the installation directory 5. Enter IP Address of the VPN Server HKU,.DEFAULT\Software\Phion\phionvpn\Profile\1, server, 0x , " " Section 3: Customer Area / [SourceDisksFiles] 6 / 8 Example for Section [SoruceDisksFiles]

7 [SourceDisksFiles]<br/>; Files for disk Customer Files #1<br/>; filename = diskid[,[ subdir][, size]] customer.inf,,,1<br/>customer.lic,,,1 ; if a license file is imported<br/>active.i_fwrule,,,1 ; if a firewall rule set is imported A SourceDisksFiles section names the source files used during installation, identifies the installation disks that contain these files, and provides the path to the subdirectories, if any, on the distribution disks containing individual files. The following directives are applicable: filename = diskid[,[ subdir][, size]] File Directives Applicable in the Customer Area / [SourceDisksFiles] Directive Comment filename Name of the file on the source disk. diskid subdir size Integer identifying the source disk that contains the file. This value and the initial path to the subdir(ectory), if any, containing the named file must be defined in a SourceDisksNames section of the same INF. Subdirectory (relative to the SourceDisksNames path specification, if any) on the source disk where the named file resides. If this value is omitted from an entry, the named source file is assumed to be in the path directory that was specified in the SourceDisksNames section for the given disk or, if no path directory was specified, in the installation root. Optional; uncompressed size, in bytes, of the given file. Do not change the name of the firewall rule set entry (active.i_fwrule). If you do not intend installing the Personal Firewall with a predefined rule set meeting company policy, then remove this line. The silent.cmd File Save the following to a.cmd file and execute this file to trigger an unattended customer setup. Separate multiple properties with off<br/>setup.exe /s /v"/qr CUSTOMER_INF=customer.inf PROGTYPE=R8 FW_NOTINSTALL=1" Specific properties must be inserted into one row. For an overview of the available properties, see the Unattended Setup [8] page. 7 / 8

8 Links 8 / 8