VBR 13.1.1.18 standard - unable to restore single AD users anymore

[RGijsen]

Case #08233502
We are using VBR Standard, we never needed Enterprise features. Until 13.1.1.18 we were able to restore single users using Active Directory Explorer, or through PowerShell. I've recently upgraded to 13.1.1.18, from 13.0.2.29 and now I run into the issue when I restore a single user, either from AD Explorer or Powershell, it reports

Code: Select all

WARNING: Container restore is only available in Veeam Backup and Replication Enterprise Edition or higher.

From V6 or V7 or so when we started with Veeam, all the way up to 13.0.2.29 we were able to restore SINGLE users. Not containers, GPO's or anything in bulk. But single users were fine. Since 13.1.1.18 users are seemingly handled as containers which they aren't. This is a huge issue for us, breaking our daily operations. Support replied quickly with 'For container restore you need Enterprise' and some ways to upgrade or trial that. However, that's not what we asked, the issue is about single item restore. I asked support again about single item restore, but didn't get a reply anymore, even after requesting updates. Some years ago I remember Veeam support really stand out above the rest.

Do others with Standard licensing run into the same issues? How to circumvent this?

[david.domask]

Hi RGijsen,

Please continue with Support on the case, as I'm not aware that there was a change on standard user restore as per our Socket Licensing guide.

If there are concerns on the handling of the case, use the Talk to a Manager button, as this is the correct way to get attention to your case; this button will put you in contact with Support Management, and they will review the case and allocate additional resources as required.

If there is an urgent need for restoring a user while the case is being investigated, you can temporarily install an evaluation license or discuss this with Support Management and they may be able to provide a temporary license while the case is being reviewed.

[RGijsen]

I will and I just used that button, although I'm usually really reluctant to push things. My main question here was not to get attention to the ticket, but to get other standard-users to check wheter this issue is in their environments too.

[david.domask]

Understood on both points, but with regards to the case main idea is to ensure you're connected with right people to help advance the situation. It's not a bother, the button is there for exactly a situation like this where there are concerns on the case handling.

And understood on awareness, I'm not sure how many standard socket licenses are still out there however, and at first blush this seems more like a technical issue that needs to be resolved, but let's wait for the conclusion of the support case as per the forum rules.