Release Notes

Issue [ASM-1182]: After deploying an application, the actual state of deployment is not reflected. After
informing the Resource Module Agent, the status shows Complete. But the users do not know whether or
not the application is deployed.
Description: If you deploy a template that includes an Application, the service is deployed and ASM
displays status as Complete. But the application is not deployed. The Application will take no longer
than 30 minutes to deploy. The user should manually confirm whether or not the applicatio
n is deployed
successfully.
Resolution/Workaround: None
Issue [ASM-1240]: Unable to log in to Active System Manager (ASM) with the credentials of the users
imported from Active Directory when certain Bind DN formats are used.
Description: While creating a directory service to import Active Directory users, the only format used
for the “User Name (Bind DN)” value is <user>@<domain>. For example, [e-mail]. If any
other formats are used, you can import users, but users cannot log in to ASM.
Resolution/Workaround: If users have already been imported, delete the users. Edit the directory
service “User Name (Bind DN)” and use the format <user>@<domain>, and then re-import users.
Issue [ASM-1243]: While importing user from Active Directory (AD), an error message is displayed,
indicating user already exists.
Description: If you add the same user accidently one or more times by clicking the Add button more
than once. After adding the same user multiple times, if you click Apply to apply the new settings, an
error message is displayed indicating user already exists.
Resolution/Workaround: Close the Import Active Directory Services dialog box. Check whether or not
the user was successfully added. If the user was not added, open the Import Active Directory Services
dialog box and the user again. Make sure that you add the user only once.
Issue [ASM-1227]: The Edit Directory Services dialog box displays incorrect information about the
protocol used for Active Directory (AD) services. The Plain protocol is always displayed, even if the
service is set to SSL.
Description: While editing an Active Directory (AD) service, the Edit Directory Services dialog box
always displays the Plain protocol, even if the directory service is set up and uses SSL
protocol. This can
cause issues when importing Active Directory users for this service.
Resolution/Workaround: To make sure the correct setting, for SSL simply select SSL and save the
directory service settings, and then re-import users. If you want to use Plain protocol, first set the
protocol to SSL, and then from the drop-down list select Plain protocol. After selecting the protocol,
save the settings, and then re-import users. Therefore, the correct protocol is used, even if ASM GUI
does not display correct protocol.
Issue [ASM-1223]: ASM displays incorrect information about EQL storage details. Storage pool
information is not accurate.
Resolution/Workaround: Make sure that information about storage pools is retrieved from actual
EqualLogic Management GUI for the storage being managed.
Issue [ASM-1352]: After restoring a backup, non-ESXi repositories are not restored. The service cannot