These release notes provide information about Ensim Pro for Windows 4.0.1 hotfix 8 resolved issues, prerequisites, and installation instructions.
Topics include:
This hotfix contains the following files:
This hotfix resolves the following issues. The numbers in parentheses indicate the Ensim problem report (PR) number.
(49619 - default DNS zones are incorrect).
We are addressing following issue
Value of Responsible person field in SOA record is not correct. After applying the hotfix, SOA record for newly added zone will have correct value for responsible person
This section describes the new features added by this hotfix. Some of these features might not be available by default and you need to enable them by following the instructions given in the section Enabling and disabling new features
Add additional NS records when zones are created.
Before installing this hotfix, ensure that your Ensim Pro 4.0.1 for Windows system has the following:
Ensim Pro for Windows 4.0.1 - hotfix 1, 2, 3, 4, 6
This section explains how to install the hotfix.
- Login to the Ensim Pro server as administrator.
- Open a command window and run the command iisreset /stop.
- Stop the EnsimProvisionEngine COM+ component. Open Start > Programs > Administrative Tools > Component Services
Navigate to : Computers > My Computer > COM+ Applications > EnsimProvisionEngine. Right Click > Shut Down- Unzip the hotfix zip file to a temporary directory.
- Change to the directory <install_dir>\cp\admin\bin\serviceComponents\msdns where <install_dir> refers to the path where Ensim Pro is installed. For example, if Ensim Pro is installed in C:\Program Files\Ensim\WEBppliance, then switch to C:\Program Files\Ensim\WEBppliance\cp\admin\bin\serviceComponents\msdns directory.
- Back up the existing DNSBackend.dll file to a location other than the existing directory.
Important: Do not rename the file and keep it in the current directory.- Copy the new DNSBackend.dll from the temporary directory to the current directory.
- Start the EnsimProvisionEngine COM+ component. Open Start > Programs > Administrative Tools > Component Services
Navigate to : Computers > My Computer > COM+ Applications > EnsimProvisionEngine. Right Click > Start- Open a command window and run the command iisreset /start.
You can remove (or roll back) the installed hotfix by restoring the backed up DLL files.
To remove (or roll back) the hotfix installation:
- Login to the Ensim Pro server as administrator.
- Open a command window and run the command iisreset /stop
- Stop the EnsimProvisionEngine COM+ component. Open Start > Programs > Administrative Tools > Component Services
Navigate to : Computers > My Computer > COM+ Applications > EnsimProvisionEngine. Right Click > Shut Down- Restore the DNSBackend.dll file from the backup location to the directory <install_dir>\cp\admin\bin\serviceComponents\msdns where <install_dir> refers to the path where Ensim Pro is installed. For example, if Ensim Pro is installed in C:\Program Files\Ensim\WEBppliance, then switch to C:\Program Files\Ensim\WEBppliance\cp\admin\bin\serviceComponents\msdns directory.
- Start the EnsimProvisionEngine COM+ component. Open Start > Programs > Administrative Tools > Component Services
Navigate to : Computers > My Computer > COM+ Applications > EnsimProvisionEngine. Right Click > Start- Open a command window and run the command iisreset /start.
The hotfix rollback is complete.
How to use this:
You can add additional NS records whenever DNS zones are created. To enable this perform the following steps:
Log on to the Ensim Pro server as administrator.
Open the Registry Editor.
In the editor window expand HKEY_LOCAL_MACHINE > SOFTWARE > Ensim > WEBppliance
Right click WEBppliance, point to new and click string value.
Rename the string value to AdditionalDNSNameServers.
Double-click the AdditionalDNSNameServers, specify the name servers separated by comma for which NS records are required to be added whenever zones are created. For example: if you want NS record to be added for ns1.server.com and ns2.server.com server, the value should be ns1.server.com,ns2.server.com
This completes the steps required to add additional NS records whenever DNS zones are created.