Hi everyone!
I have new Vms window 2019 serve. it is new and I don’t understand why it complete with Warning. on the same Veeam application I have more than 12 other Vms which have larger file and alot programs. but all of the completed success. but this new VM show warning:
6/26/2023 12:38:44 PM :: Unable to perform guest file system indexing: Failed to install via Deployment Svc
Best answer by coolsport00
In other words, the account you're using for indexing probably doesn't have enough permissions on your VM to index. Check the Indexing section of the User Guide for more info.
+20Hi
+22I remembering off the top of my head so please take with a grain of salt :). As I understand file indexing needs to inject a runtime into the VM. So this would require vmware tools and use of a windows account with admin privileges. Also I think a certain amount of space is needed on the c:\.
Again some of the better vmware and windows experts might have info.
As
+20In other words, the account you're using for indexing probably doesn't have enough permissions on your VM to index. Check the Indexing section of the User Guide for more info.
+7My understanding is that File System Indexing is good for self-service restore (via Enterprise Manager?), but I’ve never used it otherwise. I’m not sure that it’s terribly useful beyond use on maybe a file server? I believe it does make for a searchable index, so good if you don’t know exactly where a file is, but beyond that I don’t see a lot of use for it. Generally you’re going to know exactly where a file resides if you need to restore it, so guest file system indexing is not required in most scenarios in my experience.
+7I remembering off the top of my head so please take with a grain of salt :). As I understand file indexing needs to inject a runtime into the VM. So this would require vmware tools and use of a windows account with admin privileges. Also I think a certain amount of space is needed on the c:\.
Again some of the better vmware and windows experts might have info.
The screenshot indicates Hyper-V backups, so I don’t know know how Indexing works on a Hyper-V although I’m assuming it’s not too different?
+22I remembering off the top of my head so please take with a grain of salt :). As I understand file indexing needs to inject a runtime into the VM. So this would require vmware tools and use of a windows account with admin privileges. Also I think a certain amount of space is needed on the c:\.
Again some of the better vmware and windows experts might have info.
The screenshot indicates Hyper-V backups, so I don’t know know how Indexing works on a Hyper-V although I’m assuming it’s not too different?
That would use VSS but I think the same type of thing but HyperV integration tools
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
