Cant use onpremises groups after upgrade to V5

[marcusv]

Hello!

After i upgraded to V5 it seems my onprem groups used in backupjobs, that worked in v4, fails. If i sync the groups used in the backupjobs to o365 everything starts to work again.
My onprem groups don't have an officeid just onpremises id, seems like that's the problem.

Do i need to sync all my onpremises groups to o365 or is there any other way to get this working?

Best regards,
Marcus

[Polina]

Hi Marcus and welcome to Veeam Forums!

First, following the rules of this forum, please provide your case ID for this issue.

Next, it's difficult to suggest any solutions without knowing your setup at least. Is it a hybrid organization? Do you see any specific errors in the UI? Which version specifically you upgraded from?

Thanks!

[marcusv]

Thanks for the welcome.

I have a case with ID: #02251181

My setup is a hybrid organization with modern auth and legacy protocols.
The jobs based on groups in Azure is working since they have an OfficeID attribute. Groups based on onprem groups not synced to Azure is the ones failing.
They do not have an OfficeID insted they have OnPremID but the jobs fails with error "Cannot convert value "00000000-0000-0000-0000-000000000000" to type "Microsoft.Exchange.Configuration.Tasks.DynamicGroupIdParameter" That value "000-00..." is the OfficeID so the job seems to fail when a OfficeID has the value 000-00..

The groups used is Mailenabled security groups.

/Marcus

[Polina]

Hi Marcus,

Your case ID must be a valid ticket opened for this specific issue. Without it, I can't check your logs and suggest any solutions. At this point, I'd assume that there's some misconfiguration in your organization or job settings.

Thanks!

[marcusv]

Sorry, it's Case #04544404