Maintain control of your Microsoft 365 data
matteu
Veeam Legend
Posts: 823 Liked: 128 times
Joined: May 11, 2018 8:42 am
Contact:
Post
by matteu » Jul 10, 2022 10:36 am
this post
Hello,
I would like to know how can I know with powershell the exact VBM build I have installed on the server ?
I actually find this method, but maybe there is something better :
Code: Select all
$VBMFilePath = (Get-ItemProperty "HKLM:SYSTEM\CurrentControlSet\Services\Veeam.Archiver.Service" -Name ImagePath).ImagePath
$VBMFilePath = $VBMFilePath -replace '"',''
(Get-ItemProperty $VBMFilePath).VersionInfo.FileVersion
Polina
Veeam Software
Posts: 3195 Liked: 774 times
Joined: Oct 21, 2011 11:22 am
Full Name: Polina Vasileva
Contact:
Post
by Polina » Jul 11, 2022 9:31 am
this post
Hi,
You can also use the (Get-Module Veeam.Archiver.PowerShell).nestedmodules
matteu
Veeam Legend
Posts: 823 Liked: 128 times
Joined: May 11, 2018 8:42 am
Contact:
Post
by matteu » Jul 11, 2022 10:34 am
this post
Hi,
Thanks for your answer
Your method is easier
I prefer it ^^
matteu
Veeam Legend
Posts: 823 Liked: 128 times
Joined: May 11, 2018 8:42 am
Contact:
Post
by matteu » Jul 12, 2022 7:16 am
this post
I didn't notice it but it's not what I really want...
I would like to know how can I do to find VBM365 version wich is : 6.0.0.385
These previous command return 11.0.0.385
Is there a way to find the 6.0.0.385 without REST API ?
Polina
Veeam Software
Posts: 3195 Liked: 774 times
Joined: Oct 21, 2011 11:22 am
Full Name: Polina Vasileva
Contact:
Post
by Polina » Jul 12, 2022 8:25 am
this post
Currently, it's not available via PowerShell.
In the 11.x.x.xxx versions, the first numbers follow the VBR version, and the last numbers after the dot are the VB365 build number itself. The same approach is used for Veeam Explorers which are shared between VB365 and VBR. Here you can find how VB365 build numbers and versions match:
https://www.veeam.com/kb4106
matteu
Veeam Legend
Posts: 823 Liked: 128 times
Joined: May 11, 2018 8:42 am
Contact:
Post
by matteu » Jul 12, 2022 9:14 am
this post
Thanks for your answer.
This will help me
Now I know what to do ! I will post my result here
matteu
Veeam Legend
Posts: 823 Liked: 128 times
Joined: May 11, 2018 8:42 am
Contact:
Post
by matteu » Jul 12, 2022 9:35 am
this post
I don't think it's necessary to check for v4 ans less. I only work with v5+
Code: Select all
$VBRbuild = (Get-Module Veeam.Archiver.PowerShell).nestedmodules.version.tostring()
switch ($VBRbuild)
{
"10.0.2.1061" {$VBM365Build = "5.0.0.1061"}
"10.0.2.1063" {$VBM365Build = "5.0.0.1063"}
"10.0.2.1070" {$VBM365Build = "5.0.0.1070"}
"10.0.3.179" {$VBM365Build = "5.0.1.179"}
"10.0.3.207" {$VBM365Build = "5.0.1.207"}
"10.0.3.225" {$VBM365Build = "5.0.1.225"}
"10.0.3.252" {$VBM365Build = "5.0.1.252"}
"10.0.4.22" {$VBM365Build = "5.0.2.22"}
"10.0.4.42" {$VBM365Build = "5.0.2.42"}
"10.0.5.1033" {$VBM365Build = "5.0.3.1033"}
"10.0.5.1035" {$VBM365Build = "5.0.3.1035"}
"10.0.5.1051" {$VBM365Build = "5.0.3.1051"}
"10.0.5.1060" {$VBM365Build = "5.0.3.1060"}
"10.0.5.1063" {$VBM365Build = "5.0.3.1063"}
"11.1.0.367" {$VBM365Build = "6.0.0.367"}
"11.1.0.379" {$VBM365Build = "6.0.0.379"}
"11.1.0.385" {$VBM365Build = "6.0.0.385"}
Default {$VBM365Build = "Unknown Value, script update is necessary"}
}
$VBM365Build
matteu
Veeam Legend
Posts: 823 Liked: 128 times
Joined: May 11, 2018 8:42 am
Contact:
Post
by matteu » Jul 12, 2022 9:36 am
this post
I use it on a "summary" function :
Code: Select all
function Get-DCVBMSummary
{
Write-host "$(get-date -Format HH:mm) - VBM365 Summary"
$VBM365ServerName = $env:COMPUTERNAME
$VBM365ServerOS = (Get-WmiObject win32_operatingsystem).caption
$OSBuild = Get-ItemPropertyValue -path "HKLM:\Software\Microsoft\Windows NT\CurrentVersion" -name 'UBR'
#No way to find version with powershell but associated version with VBR is available here : https://www.veeam.com/kb4106
$VBRbuild = (Get-Module Veeam.Archiver.PowerShell).nestedmodules.version.tostring()
switch ($VBRbuild)
{
"10.0.2.1061" {$VBM365Build = "5.0.0.1061"}
"10.0.2.1063" {$VBM365Build = "5.0.0.1063"}
"10.0.2.1070" {$VBM365Build = "5.0.0.1070"}
"10.0.3.179" {$VBM365Build = "5.0.1.179"}
"10.0.3.207" {$VBM365Build = "5.0.1.207"}
"10.0.3.225" {$VBM365Build = "5.0.1.225"}
"10.0.3.252" {$VBM365Build = "5.0.1.252"}
"10.0.4.22" {$VBM365Build = "5.0.2.22"}
"10.0.4.42" {$VBM365Build = "5.0.2.42"}
"10.0.5.1033" {$VBM365Build = "5.0.3.1033"}
"10.0.5.1035" {$VBM365Build = "5.0.3.1035"}
"10.0.5.1051" {$VBM365Build = "5.0.3.1051"}
"10.0.5.1060" {$VBM365Build = "5.0.3.1060"}
"10.0.5.1063" {$VBM365Build = "5.0.3.1063"}
"11.1.0.367" {$VBM365Build = "6.0.0.367"}
"11.1.0.379" {$VBM365Build = "6.0.0.379"}
"11.1.0.385" {$VBM365Build = "6.0.0.385"}
Default {$VBM365Build = "Unknown Value, script update is necessary"}
}
[PScustomObject]@{
Name = $VBM365ServerName
OS = $VBM365ServerOS
OSBuild = $OSBuild
VBM365Version = $VBM365Build
}
}
Users browsing this forum: No registered users and 4 guests