Hi all,
While working with a customer on this matter, we realized that it would be very useful to integrate the bypass functionality documented in the KB4174 directly into the VBO proxy settings panel of the GUI.
The same is also applicabile to the proxy settings of the Backup Proxies.
https://www.veeam.com/kb4174
-
iDeNt_5
- Service Provider
- Posts: 76
- Liked: 25 times
- Joined: Feb 09, 2024 5:34 pm
- Full Name: Matteo Fringuelli
- Contact:
-
Mildur
- Product Manager
- Posts: 12041
- Liked: 3434 times
- Joined: May 13, 2017 4:51 pm
- Full Name: Fabian K.
- Location: Switzerland
- Contact:
Re: Feature request: Add KB4174 feature to the VBO GUI
Hi Matteo,
If we see that such “hidden” settings are used a lot, we can consider adding them to the UI.
However, since VB365 has many other feature requests with much higher priority and customer demand, this request is unlikely to be added in the foreseeable future.
That said, I can provide a workaround using Set-VBOConfigurationParameter on the controller/backup server. With this cmdlet, you can centrally configure the bypass address for the controller and each Windows-based proxy server. There is no need to manually connect to each proxy and configure the setting with a text editor.
I put together a sample script. It worked in my lab, but please still make sure you have a backup of the Config.xml and Proxy.xml files before running this script for the first time.
Best,
Fabian
If we see that such “hidden” settings are used a lot, we can consider adding them to the UI.
However, since VB365 has many other feature requests with much higher priority and customer demand, this request is unlikely to be added in the foreseeable future.
That said, I can provide a workaround using Set-VBOConfigurationParameter on the controller/backup server. With this cmdlet, you can centrally configure the bypass address for the controller and each Windows-based proxy server. There is no need to manually connect to each proxy and configure the setting with a text editor.
I put together a sample script. It worked in my lab, but please still make sure you have a backup of the Config.xml and Proxy.xml files before running this script for the first time.
Code: Select all
# ============================================================
# Automate KB4174: https://www.veeam.com/kb4174
# Author: Mildur
# Date: 2027/07/29
# ============================================================
# Variables
$BypassValue = ".+\.local;veeam\.com" # regex list of bypass hosts/fqdn
$XPath = "/Veeam/InternetProxy"
$Key = "BypassHosts"
# Credentials for the Windows proxies (for remote Proxy server)
$Cred = Get-Credential -Message "Windows credentials for the backup proxies"
# --- 1) Config.xml on the controller (VBO365 server) ---
Set-VBOConfigurationParameter -XPath $XPath -Key $Key -Value $BypassValue -Controller
# --- 2) Update Proxy.xml only on Windows-based backup proxies ---
$WindowsProxies = Get-VBOProxy | Where-Object { $_.OperatingSystemKind -eq "Windows" }
foreach ($Proxy in $WindowsProxies) {
Write-Host "Setting bypass rule on Windows proxy: $($Proxy.Hostname)"
Set-VBOConfigurationParameter -XPath $XPath -Key $Key -Value $BypassValue `
-Proxy $Proxy -WindowsCredential $Cred -Restart
}
Write-Host "Done. Bypass rule '$BypassValue' has been written to Config.xml and all Windows Proxy.xml files."Fabian
Product Management Analyst @ Veeam Software
Who is online
Users browsing this forum: No registered users and 11 guests