Compatibility
|
Imaging & Deployment v1.1 requires VSA v6.3. If upgrading to VSA v6.3, and Imaging & Deployment is installed, you will be required to upgrade to Imaging & Deployment v1.1.
|
Two New Boot Methods
|
Three boot methods are now supported:
- PXE boot - Enables a PXE server located on the same subnet as the target machine to control the bootup of the target machine. During bootup a boot menu displays and is used to deploy an image or backup.
- Disk boot (new) - Enables agent machines to boot into the pre-OS to perform imaging operations without a PXE server. Disk boot does not display the boot menu used to deploy an image or backup. The choice of selecting an image is made within the VSA user interface, prior to the reboot of the target machine.
- CD boot (new) - Enables any Windows or Linux machine to be booted up using a CD, without a PXE server. The CD displays the boot menu used to deploy an image or backup.
Both disk boot and CD boot make it possible to clone machines in subnets different from the subnet used by the repository. While internet image deployment is possible using these two methods, image deployment to a LAN with multiple subnets is recommended, due to image bandwidth issues across the internet.
|
Disk Boots
|
- Applies to agent managed machines only.
- Enables agent machines to boot into a pre-OS environment to perform imaging operations without a PXE server. Disk boot does not display the boot menu used to deploy an image or backup. The choice of selecting an image is made within the VSA user interface, prior to the reboot of the target machine.
- Used as a backup method to deploy images to agent machines, when a PXE boot server is not available on that subnet.
- Supports image deployment to more than one subnet per repository.
|
Live CD ISO
|
Imaging & Deployment 1.1 now includes a Live CD ISO, shipped with the Imaging & Deployment install. Create a Live CD using this ISO, then use the Live CD to bootup a machine you want to deploy an image or backup to. The CD bootup menu requires you to specify the VSA name or IP address, the repository, and the image or backup you want to deploy. So the same Live CD can be used generically for different VSAs and repositories.
- Allows for deployment to bare metal systems outside of the repository subnet, or where using a PXE server is a problem.
- Requires TFTP access to the repository.
- If a PXE boot or disk boot fails to complete, the Live CD can be used to remove left over bootup files and deploy an image or backup successfully.
- The ISO file is located at <KaseyaInstallDirectory>/WebPages/ManagedFiles/VSAHiddenFiles/ImageDeploy/kid11.iso
|
Boot Menu
|
A new Boot Menu feature replaces the feature called Auto Deploy in the previous release. The Boot Menu applies to non-agent machines booting up using PXE boot or the CD boot method. The Boot Menu page enables the definition of many different deployment configurations. During bootup, the user sees an image deployment boot menu that shows all the configurations available for a particular repository. The machine user selects the configuration he and she wants to use. Boot Menu configuration options include:
- Multiple images or backups to select from
- Computer naming
- The joining of a domain
- Post-cloning agent procedures
|
Multiple Repositories on the Same Subnet Supported
|
Multiple repositories on a single subnet are now supported. Only one repository on a given subnet may enable the Boot Menu, else target machines would receive instructions from competing PXE servers.
|
Cloning GPT Disks
|
The cloning of Guid Partition Table (GPT) disks is now supported.
|
Linux Backup and Restore
|
Backup and restore of Linux systems are now supported. Linux image creation and and restore are not yet supported.
|
Unicast SMB Deployment
|
Most networks support multicasting and multicasting provides better performance when multiple endpoints are cloned at once. A unicast SMB deployment option is provided for networks not configured to support multicast. Multicast capability of the network is not detected automatically.
|
VirtualBox VM for Hosting Repositories Eliminated
|
Previously repositories were hosted on a VirtualBox VM installed on a Windows machine. In Imaging & Deployment 1.1, repositories no longer run within a VirtualBox VM and instead run directly on the Windows host.
- This eliminates the need to specify a separate PXE address range.
- Repositories are automatically upgraded to remove the old VirtualBox VM when next activated after the upgrade to KID 1.1.
|
KID Repositories on Virtual Machines
|
The elimination of the VirtualBox VM hosting requirement enables Imaging & Deployment repositories to be deployed to virtual machines running Windows. Deployment of a repository on a VM is configured exactly the same way as for a physical machine.
|
KID Repositories on Kaseya Server
|
Repositories can now be installed on the Kaseya Server.
|
IP Addresses Provided by Existing DHCP Server
|
During imaging operations, IP addresses are provided by the network's existing DHCP server.
|
History Page and Details Column
|
- A new History page displays previously executed jobs. The Schedule page now only shows current or pending jobs.
- Both the Schedule page and the new History page show event history links in a new Details column. An event history link shows the step by step status of a job. From the event history page a view machines link shows the status of individual computers involved in the operation.
|