Skip to main content
Question

V13 workgroup support

  • March 18, 2026
  • 8 comments
  • 29 views

Forum|alt.badge.img+1

Does anyone know if the issues with adding a workgroup (non-domain) host is limited just to VSA? Or are the same requirements in the Windows version of v13?

8 comments

Chris.Childerhose
Forum|alt.badge.img+21

Workgroup or Domain is good with VSA and Windows version of 13.  No issues there.


Forum|alt.badge.img+1
  • Author
  • Influencer
  • March 18, 2026

Workgroup or Domain is good with VSA and Windows version of 13.  No issues there.

I have seen the user guide -Linux‑based backup servers do not support Hyper‑V workgroup clusters… this configuration is available only for Microsoft Windows‑based backup servers.

https://helpcenter.veeam.com/docs/vbr/userguide/hv_server_before_begin.html?ver=13


Chris.Childerhose
Forum|alt.badge.img+21

Workgroup or Domain is good with VSA and Windows version of 13.  No issues there.

I have seen the user guide -Linux‑based backup servers do not support Hyper‑V workgroup clusters… this configuration is available only for Microsoft Windows‑based backup servers.

So are you using Hyper-V?  The help also says this -

[For Linux-based backup servers] Both the Hyper-V nodes and the backup server must be joined to the same Active Directory domain. If they are not joined to the same Active Directory domain, additional manual configuration of the krb5.conf file is required. For more information, see Performing Maintenance Tasks


Chris.Childerhose
Forum|alt.badge.img+21

I am unsure if that sentence you mentioned is just about Hyper-V Clusters or domain/WG related it is hard to tell.  The statement above it is clear that I quoted.


Forum|alt.badge.img+1
  • Author
  • Influencer
  • March 18, 2026

I am unsure if that sentence you mentioned is just about Hyper-V Clusters or domain/WG related it is hard to tell.  The statement above it is clear that I quoted.

Sorry for the confusion. I am checking for domain/workgroup


Chris.Childerhose
Forum|alt.badge.img+21

I am unsure if that sentence you mentioned is just about Hyper-V Clusters or domain/WG related it is hard to tell.  The statement above it is clear that I quoted.

Sorry for the confusion. I am checking for domain/workgroup

No worries.  I think that statement you are referring to has to do with the Hyper-V Cluster not specifically for VBR for workgroup.


Forum|alt.badge.img+1
  • Author
  • Influencer
  • March 18, 2026

I am unsure if that sentence you mentioned is just about Hyper-V Clusters or domain/WG related it is hard to tell.  The statement above it is clear that I quoted.

Sorry for the confusion. I am checking for domain/workgroup

No worries.  I think that statement you are referring to has to do with the Hyper-V Cluster not specifically for VBR for workgroup.

So it means no issues with vbr for workgroup?

 


Chris.Childerhose
Forum|alt.badge.img+21

I am unsure if that sentence you mentioned is just about Hyper-V Clusters or domain/WG related it is hard to tell.  The statement above it is clear that I quoted.

Sorry for the confusion. I am checking for domain/workgroup

No worries.  I think that statement you are referring to has to do with the Hyper-V Cluster not specifically for VBR for workgroup.

So it means no issues with vbr for workgroup?

 

Precisely.  VBR for Workgroups is good and so is domain if done right. 😁