VeeamON 2024 - Use Code "COMMUNITY10" for 10% Off!
Warum lässt du Veeam die Mail nicht direkt über einen ISP versenden.Lässt die Firewall keinen Mailversand vom Client direkt zu?Dann ev. da die Firewall aufbohren.Nur so als Hinweis.Wenn du über Strato versenden willst nimm Port 587. 465 geht mit Veeam nicht.
Just checked it.Latest Veeam Community Version rolls out identical Windows client and identical ISO Creation Tool.I do not think that using this way willl be a game changer.
Other idea is to install the community edition in latet build in a vm and create recovery image in community edition.Is this worth a try, cause agent from community edition seems to have a slightly higer build than the pure Veeam Free Windows Agent which is 6.0.2.1090 at the moment.
Server DL345 Gen11 type is brand new from the factory and has lots off compoents i never used before. MR Controller, Broadcom NICs, AMD Chipset …So i am afraid i have to create the ISO with this server to have the needed drivers embeded.
So did you solve the issue? Also are you using V6 of the agent to create the ISO? If not try creating the recovery image from a lower version OS as there were issues with the latest ones and I am sure the next update will work. The problem is solved to 50%. There is a solution, but the solution is somehow bad.The VEEAM Recovery Image ISO is created by the server. The server is freshly installed with OS 2022. I will not go back to 2016 just to create a recovery ISO.The ISO seems to be somehow to be non standard. It will not boot from ILO nor from Ventoy Stick, NOR as VM.Copying to USB stick with Rufus 4.2 works. So Rufus seems to modify something within EFI.Recovery fires up. Network adapters are functioning. So what could go wrong :-)Converting this stick back to ISO with Imageburn did not do the trick for me. Booting from ISO still fails.I need a working ISO boot, because in case of emergency the server will be recovered using ILO Adapter from Remote.
Can anyone explain, how i can edit my own original Question. I would like to remove some missspellings and add some Updates:Updates:I said i testeted with Rufus. In fact it was a Test with Ventoy, which works fine for me in most other cases. Copying the Veeam Image with Rufus 4.2 to a new 32 GB USB Stick solved the problem. The stick boots. So RUFUS seems to modify the image.BTW: Original .ISO will not boot in virtual enviroments too.
Same Issue on HP Elitedesk 705 G5. All latest Build OS Windows 11 22H2 and Veeam EnvironmentWorked fine on Windows 10 latest Build / with coexisting Linux on 2nd NVME.Failure:Boots to the cmd screen.Fix:Booting from a stick created with “Create Recovery Media) on different PC (HP Workstation) running Windows 10 starts the Recovery Environment. Luckily HP Drivers are compatible and i can access the Backup in the LAN. PS: removing the Recovery Partition from Disk and Replacing the Recovery Environment from Current ISO Image WINDOWS 11 did not change the unsuccessful boot.
Already have an account? Login
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.