Environment
Novell Client 2 SP3 for Windows
Windows Vista
Windows 7
Windows 8
Windows Server 2008 R2
Windows Server 2012
Windows Vista
Windows 7
Windows 8
Windows Server 2008 R2
Windows Server 2012
Situation
The network administrator wants to update certain Novell Client settings without updating the Novell Client to a newer version.
Resolution
Method 1
The Novell Client's Client Update Agent is designed to be able to distribute Novell Client settings without updating the Novell Client at the same time. Note: ACU.EXE and SETUP.EXE will not update Novell Client properties without also updating the Novell Client. See TID 7010975.
The Novell Client 2 SP3 for Windows Administration Guide explains how to use the Client Update Agent to set properties on multiple workstations after installation:
https://www.novell.com/documentation/windows_client/windows_client_admin/data/btx1xfx.html
If the Novell Client in the installation set is the same version as what is already installed on the workstation, the Update Agent will not trigger a Novell Client installation/upgrade. But if the Novell Client Properties File is specified in the INSTALL.INI, and "ApplyNovellClientPropertiesFile=Yes" is set in the INSTALL.INI (which is the default), Update Agent will examine the time stamp of the Novell Client Properties File to see if it is newer than the one already applied on the workstation. If it is newer, Update Agent will apply the newer Novell Client Properties File settings and will then display the date and time of the currently applied file in the "Latest Novell Client Properties File" field of the Update Agent tab in the Novell Client Properties.
Note: The Client Update Agent method does not provide for removing entries that are not controllable through setting the entry. For example, it is not possible to remove a configured System Login Profile using CUA. Use either of the registry methods instead. See Microsoft KB article 310516 "How to add, modify, or delete registry subkeys and values by using a .reg file"
Method 2
It is also possible to push the Novell Client settings such as to enable the Client Update Agent (or any other registry settings) in the login script, by running REGEDIT.EXE. The Novell Client 2 SP3 for Windows registry settings can be found here:
https://www.novell.com/communities/coolsolutions/novell-client-2-sp3-windows-registry-settings/
It is possible to push different registry settings, depending on the version of Windows (and, therefore, the Novell Windows Client) installed on the workstation (or other variables). The following example shows how to push one file for Windows 7, and another for Windows 8. The values for various Windows operating systems are as follows:
Windows 10 V10.00
The Novell Client's Client Update Agent is designed to be able to distribute Novell Client settings without updating the Novell Client at the same time. Note: ACU.EXE and SETUP.EXE will not update Novell Client properties without also updating the Novell Client. See TID 7010975.
The Novell Client 2 SP3 for Windows Administration Guide explains how to use the Client Update Agent to set properties on multiple workstations after installation:
https://www.novell.com/documentation/windows_client/windows_client_admin/data/btx1xfx.html
If the Novell Client in the installation set is the same version as what is already installed on the workstation, the Update Agent will not trigger a Novell Client installation/upgrade. But if the Novell Client Properties File is specified in the INSTALL.INI, and "ApplyNovellClientPropertiesFile=Yes" is set in the INSTALL.INI (which is the default), Update Agent will examine the time stamp of the Novell Client Properties File to see if it is newer than the one already applied on the workstation. If it is newer, Update Agent will apply the newer Novell Client Properties File settings and will then display the date and time of the currently applied file in the "Latest Novell Client Properties File" field of the Update Agent tab in the Novell Client Properties.
Note: The Client Update Agent method does not provide for removing entries that are not controllable through setting the entry. For example, it is not possible to remove a configured System Login Profile using CUA. Use either of the registry methods instead. See Microsoft KB article 310516 "How to add, modify, or delete registry subkeys and values by using a .reg file"
Method 2
It is also possible to push the Novell Client settings such as to enable the Client Update Agent (or any other registry settings) in the login script, by running REGEDIT.EXE. The Novell Client 2 SP3 for Windows registry settings can be found here:
https://www.novell.com/communities/coolsolutions/novell-client-2-sp3-windows-registry-settings/
It is possible to push different registry settings, depending on the version of Windows (and, therefore, the Novell Windows Client) installed on the workstation (or other variables). The following example shows how to push one file for Windows 7, and another for Windows 8. The values for various Windows operating systems are as follows:
Windows 10 V10.00
Windows Server 2012 V6.02
Windows 8.1 V6.02
Windows 8.1 V6.02
Windows 8 V6.02
Windows Server 2008 R2 V6.01
Windows 7 V6.01
Windows Vista V6.00
To verify the OS_VERSION on a given workstation, add the following two lines to the login script, and ensure the "Display results window" checkbox in the Novell Login "Script" tab has been checked.
WRITE "OS_VERSION = %OS_VERSION"
PAUSE
EXAMPLE:
Assume you want different registry settings on Windows 7 and Windows 8 workstations. You have exported certain registry settings for each operating system to a .reg file. To push the respective registry files, you can add the following lines, adjusting as needed for your environment:
;test for Windows 7, and import the Windows 7 registry file
IF "%OS_VERSION" = "V6.01" THEN
;the next line executes regedit.exe silently,
;applying the settings specified in "win_7_registry_file.reg".
#regedit.exe /s win_7_registry_file.reg
ELSE
;test for Windows 8, and import the Windows 8 registry file
IF "%OS_VERSION" = "V6.02" THEN
;the next line executes regedit.exe silently,
;applying the settings specified in "win_8_registry_file.reg".
#regedit.exe /s win_8_registry_file.reg
END
See the "Novell Login Scripts Guide" for more information about using login script commands and variables.
https://www.novell.com/documentation/linux_client/login/data/front.html
Method 3
Employ a tool such as ZENworks Configuration Management to distribute registry settings.
https://www.novell.com/documentation/zcm10/zcm10_software_distribution/data/bagi8rl.html
Windows Server 2008 R2 V6.01
Windows 7 V6.01
Windows Vista V6.00
To verify the OS_VERSION on a given workstation, add the following two lines to the login script, and ensure the "Display results window" checkbox in the Novell Login "Script" tab has been checked.
WRITE "OS_VERSION = %OS_VERSION"
PAUSE
EXAMPLE:
Assume you want different registry settings on Windows 7 and Windows 8 workstations. You have exported certain registry settings for each operating system to a .reg file. To push the respective registry files, you can add the following lines, adjusting as needed for your environment:
;test for Windows 7, and import the Windows 7 registry file
IF "%OS_VERSION" = "V6.01" THEN
;the next line executes regedit.exe silently,
;applying the settings specified in "win_7_registry_file.reg".
#regedit.exe /s win_7_registry_file.reg
ELSE
;test for Windows 8, and import the Windows 8 registry file
IF "%OS_VERSION" = "V6.02" THEN
;the next line executes regedit.exe silently,
;applying the settings specified in "win_8_registry_file.reg".
#regedit.exe /s win_8_registry_file.reg
END
See the "Novell Login Scripts Guide" for more information about using login script commands and variables.
https://www.novell.com/documentation/linux_client/login/data/front.html
Method 3
Employ a tool such as ZENworks Configuration Management to distribute registry settings.
https://www.novell.com/documentation/zcm10/zcm10_software_distribution/data/bagi8rl.html