SRM 4.0.3 corrects several problems in SRM 4.0.2. This release also includes those updates included in 4.0.2. For information on issues resolved in 4.0.2, see VMware Site Recovery Manager 4.0.2 Release Notes. This update can be installed over 4.0, 4.0.1, or 4.0.2.
This update corrects the following problems:
Parsing of URLs has been improved to avoid unauthorized directory traversals.
The dns_update.cmd script has been modified to implement the skipmode command as expected. DNS records are now skipped, as expected, when the skipmode parameter is used.
In Windows Server, in the case where Windows Firewall is unregistered, SRM installation could fail, resulting in installation rollback. This issue has been resolved, so installation now completes as expected.
When SRM attempted to create a placeholder virtual machine at the recovery site to protect a virtual machine, the action could fail with the error Unable to create placeholder virtual machine at the recovery site: Recovery Virtual machine could not be created: The operation is not supported on the object. This issue has been resolved, and placeholder virtual machines are now created as expected.
It is possible to complete an upgrade or installation using an existing database. In some cases, if an installation or upgrade failed, during the rollback process, the existing database was deleted. Databases from previous installations are now kept if a rollback is required.
It is possible to install SRM into environments that use firewalls. For SRM to complete necessary communications, ports must be opened in the firewall. In the past, these ports were not opened. These ports are now opened.
The upgrade process expected certain resources to be on the C:\ drive. As a result, attempts to upgrade a system that was configured to use other drives, could fail with errors. For example, the following error might occur: can't open perl script "e:\program": no such file or directory. This issue has been resolved and varied drive letters are now handled as expected.
When attempting to authenticate to SRM, sometimes the error 411: Length Required occurred, even when correct authentication information was provided. The authentication mechanism now provides an appropriate Content-Length value, so authentication now proceeds as expected.
When multiple datastores are created in very rapid succession over a short period of time, vCenter Server may provide SRM with duplicate information about the new datastores. This might have occurred, for example, if one hundred datastores were created in one second. In the past, this created problems, but SRM now handles this information as expected.
When using network security and vulnerability scanning tools, such as Tenable Nessus, the VMware vCenter Site Recovery Manager (SRM) server might fail or the SRM service might stop. Site Recovery Manager is no longer negatively affected by these scans.
Applying the Update
This update can only be applied to SRM 4.0, 4.0.1, or 4.0.2 server. After applying this update, then update each vSphere client that is using the SRM 4.0, 4.0.1, or 4.0.2 client plug-in.
Download the update and save it on a volume that is accessible to all of your SRM 4.0, SRM 4.0.1, and SRM 4.0.2 server hosts. The update file name is VMware-srm-4.0.3-375173.exe.
To apply the update to an SRM server host, log in to the host as a member of the Administrators group.
Run the update file. The update installation stops the SRM service, installs the updated files, and restarts the SRM service.
Update the SRM plug-ins on client hosts. For each host whose vSphere client has downloaded, installed, and enabled the SRM 4.0 plug-in:
Close any open instances of the vSphere Client.
Use the Windows Add or Remove Programs tool to uninstall the VMware Site Recovery Manager plug-in
Connect to the SRM server that you updated in Step 3.
Follow the procedure in Chapter 2 of the Administration Guide to install and enable the new plug-in.
Removing the Update
To remove this update:
Use the Windows Add or Remove Programs tool to uninstall VMware vCenter Site Recovery Manager.
Install VMware vCenter Site Recovery Manager 4.0, as described in Chapter 2 of the Administration Guide.