[RELEASE] Managed Hardened Repository ISO by Veeam

[HannesK]

Hello,
thanks, yes that behavior makes sense. We will also discuss internally whether we can make that "upload root CA certificate" easier in future versions.

Best regards
Hannes

[Gostev]

All, while Managed Hardened Repository ISO will remain available for adding hardened repositories to V12 installs, for V13 installs please use the new Veeam Infrastructure Appliance to provision new hardened repositories. This is available in the same place as the original ISO, under Additional Downloads > Extensions and Other.

[PCM-AndyW]

Is there an upgrade path from this ISO to the latest Veeam Infrastructure Appliance’s hardened repo?

[HannesK]

Hello,
the current version is "new deployments only". There is no upgrade path today.

For the future, we are working on an upgrade path, yes. Very likely it will be something like "repair installation".

Best regards
Hannes

[Gostev]

Repair is in the ideal world of a galaxy far far away though, as we have no resources to work on this capability in the next few months.

So I asked that QA to see if there's an approach that involves a few manual steps, and if exists they will validate and document it. Might be good enough considering we're talking about once in a life time migration.

[chris.childerhose]

I have tried adding a VHR from ISO 2.0 to my VBR v13 environment using the credentials method but it never works. Get errors like below -

Code: Select all

9/9/2025 4:54:50 PM Failed : Installing OpenSSL3 package Error: Error: Sorry, user veeamsvc is not allowed to execute '/bin/rpm --install /tmp/veeam-openssl3-3.0.0.31-1.x86_64.rpm' as root on server.domain.home.; Exit code: 1 (0:00:02)

9/9/2025 4:54:53 PM Failed : Installing OpenSSL3 package Error: Error: Sorry, user veeamsvc is not allowed to execute '/bin/rpm --install /tmp/veeam-openssl3-3.0.0.31-1.x86_64.rpm' as root on server.domain.home.; Exit code: 1 (0:00:02)

9/9/2025 4:54:53 PM Failed : Error: Sorry, user veeamsvc is not allowed to execute '/bin/rpm --install /tmp/veeam-openssl3-3.0.0.31-1.x86_64.rpm' as root on server.domain.home.; Exit code: 1

9/9/2025 4:54:53 PM Failed : Failed to save Linux server: Error: Sorry, user veeamsvc is not allowed to execute '/bin/rpm --install /tmp/veeam-openssl3-3.0.0.31-1.x86_64.rpm' as root on server.domain.home.; Exit code: 1

9/9/2025 4:54:53 PM Failed : Infrastructure item save failed Error: Error: Sorry, user veeamsvc is not allowed to execute '/bin/rpm --install /tmp/veeam-openssl3-3.0.0.31-1.x86_64.rpm' as root on server.domain.home.; Exit code: 1

So looks like I will need to start net new with the JeOS installs I did as I planned to migrate the data over from my old repos.

[Gostev]

@HannesK any comments?

[PCM-AndyW]

One thing I'd be interested to know is what support would be provided for the v12 ISO in a v13 environment, considering at the moment I beleive it's still experimental support.

[Gostev]

That will remain as is also in V13 environment as V12 ISO is no longer actively developed or improved.

Veeam Infrastructures Appliance is the future and it's fully supported.

[Gostev]

@chris.childerhose Hannes found an issue to be non-matching sudo command whitelist. We should be able to address this by pushing an update for veeam-hardened-repository-configurator package, if there will be much interest in registering V12 managed VHR with V13. But I'd like QA focus their effort on migration to VIA first, before they work on this.

[chris.childerhose]

@Gostev - great to hear you found the issue. If there is a way you can have me test this, I would be happy to, as I would really like to get these registered to move the data off to the new VHRs based on JeOS. I can see that many users would want this for sure.

If there is any way this can be done for me to test, please let me know; otherwise, I will hopefully wait (not for long, I hope) or just scrap the old VHRs and go with the new ones.

[dloseke]

Will this also affect the v13 Windows deployments as well with the v12 managed VHR's? I'm just trying to figure out the upgrade path as I don't plan on migrating the v12 Windows deployments to v13 appliances in most cases, but I do have some of the VHR 2.0 deployed in production so if it can upgrade the existing VHR's or if I need to redeploy/repair the currently VHR's with the v13 JeOS deployments, I can do that then, but I just want to be prepared for the best route on these as I'm looking at 4 VHR ISO's (and either 2 or 3 manual builds) currently deployed on v12.

[Gostev]

Yes as V13 Windows installable software is the same exact code as V13 appliance.