Wait... so you say "right away", but in reality (according to what you have just explained) it was after they had you reproduce the issue without Veeam in the picture by running the WMI query against the affected server manually? And if that is the case, the next step would indeed be to troubleshoot the malfunctioning API issue with Microsoft, as Veeam does not have access to the WMI source code and so we are unable to debug this WMI call to understand where exactly it fails in your environment and why.HHo wrote:I was browsing the forum to see if I can find a solution to my Veeam replication issue, and stumble on this thread. I have a support case open on this issue. The initial reply from Veeam was after hours, which is fine since this is not an urgent case. The initial reply have me go through a wmi query. My query came back with permission issue, which I email back to Veeam support.
The next response from Veeam is to contact Microsoft to fix this problem first. My initial reaction is "this is bad". They have not even look at the environment, and already blame the problem on Microsoft. I've seen some bad customer service before. This is one of those rare time that I see the vendor blame on someone else right away.
Now, of course if it was a known issue with the verified solution available based on earlier support cases, trust me they would have just told you immediately what to do to fix your issue, as they maintain internal KB on all commonly reported problems and solutions for all issues which may prevent our product from functioning.