sfpp wrote:And another two:
my old #00803552 (2015-Feb-19 !!!)
and a new #00963441 (today)
sfpp wrote:This is strange but I have never seen anything implemented by Veeam about reports and problems
sfpp wrote:support/fix/implementation is not efficient for me.
This case is a simple example or check my other case
Gostev wrote:Well, one thing you do have to understand is that this software is not developed for you specifically (or anyone else in particular). We don't do custom development
Gostev wrote:In other words, yes - you should not expect that YOUR specific requests will be immediately addressed
Gostev wrote:Now, regarding this specific case. As I've already mentioned earlier in this topic, this specific request simply did not generate enough support cases to be considered for inclusion in the update.
sfpp wrote:But this issue was introduced with Veeam 8!
Version 7 work correcty.... and in this case this is not a "special development but a FIX request".
Gostev wrote:Immediately? ..Sure, i know.. this post/case was open about 1 Year ago! Check it.
Gostev wrote:Looking at the code i'm sure this is a simple fix (about 1 minutes for disable warning or about 10 min for introduce a "special flag/variable" for disable/fix it).
Added ability to convert "VMware Tools not found" job warning to informational event. To enable this behavior, set DisableVMwareToolsNotFoundWarning (REG_DWORD) registry value to 1.
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\Veeam Backup and Replication]
Users browsing this forum: Google [Bot] and 27 guests