Release Notes for Acronis Snap Deploy 4 Update 1
Release date: Oct 3rd, 2012
Build: English USA, English UK, German & French
Build number: 540
Installation procedure
The installation procedure is straightforward. Please, run the downloaded executable file and follow the instructions.
General improvements from the previous build (268)
- [New feature] UEFI architecture support for imaging and deployment
- [New feature] GPT disks support for imaging and deployment. Images taken on machines with BIOS architecture can be also deployed to UEFI machines – disk layout will be converted to GPT automatically.
Limitations: Linux GPT volumes are not supported for imaging and deployment.
- [New feature] Windows 8/Windows Server 2012 and WAIK 4 support
Limitations: Deployment of *.vhdx master images with Windows 8/Windows Server 2012 OS is not supported
- Fixed compatibility issues with Acronis Backup and Recovery PXE Server
- Acronis SnapAPI driver was updated
- A Linux kernel has been updated for the better hardware support in Linux bootable media.
List of issues fixed since the previous build (268)
Installation
- Acronis Snap Deploy 4 PXE service is not started automatically after installing Acronis Snap Deploy PXE server over Acronis Backup and Recovery PXE server
- Acronis Managed Machine Service is stopped and not restarted automatically if Acronis Snap Deploy 4 is installed on the machine after Acronis Backup and recovery 10\11
- There is no warning during installation if only Acronis Snap Deploy 4 upgrade serial number is specified without full Acronis Snap Deploy 3 license
- Acronis File Server files are not overwritten during installation of Acronis Snap Deploy 4 over Acronis Backup and Recovery 10\11 until reboot or Acronis File Server service restart
- Impossible to install Acronis Snap Deploy 4 PXE server over Acronis backup and Recovery 10 PXE
Management Console
- It is not possible to create new user-initiated deployment after you delete the old one and reboot
- “Enable\Disable PXE server” button does not make any affect until Management Console is restarted
- “Help->Collect system information” menu option does not work in Acronis Snap Deploy if Acronis Backup and Recovery 11 is installed on the same machine
- Template changes made during editing are not shown when template is being edited second time
- Credentials are not accepted in deployment template wizard if Acronis Snap Deploy 4 was installed on the machine after Acronis Backup and Recovery 11
- Option “Repeat the task every X hours until …” in deployment template wizard not working
Deployment
- Universal Deploy does not install drivers for NIC on deployed machine
- Universal Deploy fails with error “Failed to download file” if “Specify mass storage drivers to install anyway” option was selected
- Machine is not joined to domain after deployment if credentials are specified as “domain\user” if only first level domain name is specified in credentials instead of FQDN
- Deployment fails with "Failed to start multicast session on FileServer" error if target machine is started from PXE server installed with Acronis Backup and Recovery 10\11 on the same machine
- Deployment fails with "Failed to start multicast session on FileServer" error if Acronis Backup and Recovery 10\11 PXE server service is started on Acronis OS Deploy Server machine
- “Application to run” option does not work - after deployment transferred script is not executed on the deployed machine
- Deployment of password–protected master image fails if image password contains Unicode symbols
- Deployment fails if master image is located on a network share and credentials were not specified in deployment template
- Deployment fails with “Failed to start multicast session” if OS Deploy Server has additional network connections (e.g. Wi-Fi, Bluetooth, etc) besides regular Ethernet connection used to communicate with target machines
- Deployment template option “Default gateway” is not applied to deployed machines
- Acronis Universal Deploy does not inject NIC drivers into the deployed machine if they are stored on the network share
Bootable Media
- It is not possible to upload Acronis Snap Deploy 4 components to PXE server with Acronis Bootable Media Builder if ASD and ABR11 are installed on the same machine
- OS Autostart feature is not working if password-protected components are uploaded to PXE
- User-initiated deployment fails if target machine has NIC adapters not connected to the network
- TCP\IP settings in deployment template of Standalone Utility are not accepted even if filled correctly (e.g. same values as those that work in deployment template wizard in Windows)
- IP address for Standalone utility media cannot be specified manually
- Acronis Bootable Media Agent hangs if there are no NIC adapters on the machine
Documentation
- Description Security Identifiers in deployment template is updated – SID is not changed after deployment for master images of servers with Domain Controller role enabled.
- Note for Acronis Bootable Media has been added – bootable CD cannot resolve machine names correctly if name contains non-English characters. IP address should be used instead for such scenarios.
Other fixes
- Acronis File Server crashes after service is restarted if there are two network adapters in the system and one of them is disabled in device manager
- Sporadic crashes of Acronis Snap Deploy PXE server
- Wrong error message “Failed to start multicast session on FileServer.” instead of “Failed to start unicast session on FileServer.” when unicast session on File Server fails to start
- Remote Assistance does not work on the deployed machine if SID was changed during deployment
- Creation of master image from machine containing Dell OEM fails with “Failed to read from sector ‘63’ of hard disk” error
Known issues
- Deployment fails with “Host ‘X.X.X.X’ has failed the deployment” error if Jumbo Packet property of network adapter is enabled on OS Deploy Server
- Booting Hyper-V 3.0 virtual machines from Acronis PXE is very slow
- Incorrect error “Deployment has failed” appears after successful deployment from external network via VPN connection
- Windows 8 App Store applications cannot be updated/re-installed after deployment if deployment template option “Generate a unique SID for each deployed machine” was used