Release Notes
7
must be associated in ASM. A non-administrator user can be assigned the Administrator role in ASM.
Resolution/Workaround: Make sure that during import of Active Directory users, appropriate ASM role
level is assigned.
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-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-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.
Resolution/Workaround: Make sure that any default template is cloned, and then passwords are
updated for the new template.
Issue [ASM-1196]: The Windows unattend file contains a clear text password.
Description: The Windows unattend.xml.erb file contains a clear text password. This password is
required for razor to install Windows. It is accessible through the svc URL,
which should be isolated on
the PXE network.
Resolution/Workaround: You should make sure that the password is changed after the Windows
install or set to Windows to force you to change password on first login.
Issue [ASM-1086]: Active Directory user import displays an error message
if the name contains invalid