Release Notes

deployment.
Resolution/Workaround: Make sure that any default template is cloned, and then passwords are
updated for the new template.
Issue [ASM-1198]: Issue while provisioning virtual machines with hostname that has already been used.
Description:
If you provide the same name of the virtual machine which exists for an earlier deployment
to vCenter, even if it does not exist anymore, virtual machines cannot be provisioned. The virtual
machine is created on vCenter, but the OS cannot be installed on the virtual machine and virtual
machines are not provisioned indicating an error.
Resolution/Workaround: You cannot use the same virtual machine name on subsequent deployments.
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
characters.
Resolution/Workaround: Make sure while importing the Active Directory user name, the user name
contains only alphanumeric characters.
Issue [ASM-1055]: After configuring networks for vSwitch on ESXI, all dialog boxes display UUIDs.
Description: While deploying a service, the dialog boxes in the Service Recent Activity display UUIDs
instead of actual network names.
Issue [ASM-1001]: Unable to deploy a service for Fiber Channel storage component if the server object
is already mapped to the volume in Storage Center.
Description: If the server object is already mapped to a volume in Compellent Storage Center then a
service cannot be deployed for storage component.
Resolution/Workaround: Un-map the volume in Compellent Storage Center, and then retry the service
deployment.
Issue [ASM-1469]: Unable to deploy a Resource Module using CentOS 6.5 because devices do not check
in using ASM.
Description: ASM installs an agent in the deployed operating system using a CIFs share, and this agent
should check in to confirm the deployment. If the minimal ISO is used on CentOS, the correct packages
for the samba-client to mount the share are not included. Therefore, the agent RPM cannot be
downloaded.
Resolution/Workaround: To install CentOS, do not use the minimal install because
this does not include