Release Notes

Resolution/Workaround: If you are on a page that displays a list view, make sure you close these pages.
Issue [ASM-1150]: Importing users from Active Directory blocks access for local users.
Resolution/Workaround: You cannot use “ASMLOCAL” for the imported domain name.
Issue [ASM-1240]: Unable to log in to 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-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-1352]: After restoring a backup, non-ESXi repositories are not restored. The service cannot
be deployed until you manually re-create repositories.
Description: After you restore a backup to an ASM virtual appliance, the backup cannot re-create OS
installation repositories. The service cannot be deployed using non ESXi-OS after restore until you
re-create their OS repositories in Razor.
Resolution/Workaround: After performing a restore, make sure all OS install repositories are re-
created.
Issue [ASM-1260]: An operator cannot delete an unsuccessful service deployment.
Description: An operator can initiate a service deployment, but ASM does not provide the ability for an
operator to delete that service. The Delete button is greyed out.
Resolution/Workaround: Only an admin user can delete a service that is failed.
Issue [ASM-1255]: Default template passwords are not displayed, and the users are not prompted to
change the password.
Description:
Default templates that ship with ASM appear to contain passwords because a masked value
is visible in password fields. Actually a password is not present, so this causes issues during service
deployment.