New
#30
Is the technology preview stable?
Just wondering if the viboot technology-preview is stable enough to use? Has anyone experienced any problems?
Just wondering if the viboot technology-preview is stable enough to use? Has anyone experienced any problems?
No issues so far.
I have for instance a Macrium image created from Build 14372, which I upgraded to 14379 with viBoot, then again upgraded to 14385 on Sunday. Restoring the twice upgraded image went without problems and computer where image was restored to runs now 14385 as it should.
Of course I have to admit that I have not tested it extensively. My use of viBoot is quite basic; I have a few base Macrium images, containing a sysprepped customized Windows, which I then upgrade with new builds.
I occasionally add / remove some files and software to these images.
The one and only minor issue is that when modified image is saved it uses a lot of computer resources. On my 12 GB system the available RAM for instance dives down to less than 500 MB when writing the modified image, making the PC almost unusable while the image is being written.
viBoot Released! – Macrium Software BlogviBoot Released!
JULY 15, 2016 SAUL PAINTER
Today we release a new update to our popular Macrium viBoot product. Macrium viBoot has been created to allow you to answer some important questions about your disaster recovery plan… Will my backups allow me to successfully boot into Windows if I needed to restore from them? Are new applications or updates safe to install? How long would it take to recover data should a disaster strike?
Macrium viBoot not only ensures that you have an incredibly effective disaster recovery tool, but also that your live environment is free from risk.
Create a replacement virtual machine in minutes
Macrium viBoot provides a simple and efficient route to creating a Microsoft Hyper-V virtual machine from one or more Macrium Reflect image files. Within minutes you will have an almost identical replica of the computer from which the image was taken; allowing you to continue working as though you were sat at the original computer. When coupled with Macrium Reflect, all of the changes made while the viBoot virtual machine session is running, can be added to the existing backup set or a new backup set can be created.
Macrium viBoot - Release Notes
http://updates.macrium.com/viboot/v6...ase_notes.html
Release Date
15th July 2016 Version
6.1.1405 - First production release Download Link
http://updates.macrium.com/viboot/v6...ibootsetup.msi New Features
- Improved support for Windows 10.
- Supports images with up to 64 drives.
- Backup the virtual machine without deleting it (requires Macrium Reflect).
- Added “None” option when selecting virtual switches.
- Optimized the drive mounting process to reduce virtual machine creation time.
- Improved user interface components.
- Automatic CPU count detection.
- Complete overhaul of the logging capabilities and a new log pane view.
- Removed dependency on Microsoft services.
Bug Fixes
- Improved support for booting Windows XP based images.
- Temporary files are now deleted when no longer needed.
- Improved reliability of the Virtual SCSI Adapter device driver.
Known Issues
- Virtual Machines based on images stored on a network share will not persist over a restart of the host computer.
Thanks Cliff, need to edit tutorial, remove the references for viBoot still being Tech Preview :)
Tweet
— Twitter API (@user) View on Twitter
Tweet
— Twitter API (@user) View on Twitter
Tweet
— Twitter API (@user) View on Twitter
Hi Kari,
Which version of Windows are you running?
The log file correctly states that viBoot has failed to initialize the Macrium Reflect SCSI adapter. Without the Macrium Reflect SCSI adapter it is not possible to create a Hyper-V VM.
Did you uninstall the tech-preview before installing the released version of viBoot?
Thanks,
Mike.
I have viBoot on several machines.
On those machines I have now tried update, clean install, everything. I have tried every known trick to bypass driver signing. viBoot does not work for me at the moment due the before mentioned error.
Could you tell me the exact version of Windows that are running on the machines?
Windows 10 Education and Pro, Build 14390, although I don't understand what difference it makes.