> For the complete documentation index, see [llms.txt](https://kb.hostednetwork.com.au/support/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://kb.hostednetwork.com.au/support/services/cloud/infrastructure-as-a-service/vcloud-director-legacy/backup-and-restorations/setting-up-guest-processing.md).

# Setting up Guest Processing

This documents provides guidance on setting up guest processing within Veeam backup.

## **Introduction**

When setting up guest processing, it is important that the account used for it has the right permissions. Veeam uses two access methods to access guest operating systems on virtual machine:

* RPC (Remote Procedure Call) -  Uses network access from Veeam proxy
* VIX (Virtual Infrastructure eXtension) - Uses vmware tools from Veeam proxy

Due to the way in which the Veeam environment is set up, Veeam it is unable to use RPC for guest processing which automatically forces it to failover to VIX. The table below shows different options for guest processing account types and their use with each of the methods. 

![](https://3953723498-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LYYiX2aEcPAPdzrvDc4%2F-Lr7Q4AfTauX0CmUaTQo%2F-Lr7WYBoY6-_fljiaSGj%2Fimage.png?alt=media\&token=b4312f86-f553-4485-a6bf-8962ac2cf6d9)

In case you selected one of the options which requires LUA (UAC - User Access Control) disabled, it needs to be disabled in the registry. The information on the registry location is provided below. 

For **2012/2012 R2/2016**, you must change the “EnableLUA” DWORD to 0 in HKEY\_LOCAL\_MACHINE\Software\Microsoft\Windows\CurrentVersion\policies\system

Once the EnableLUA is set to 0, the OS needs to be restarted for change to take effect. Once done, guest procesing should run succesfully. 


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://kb.hostednetwork.com.au/support/services/cloud/infrastructure-as-a-service/vcloud-director-legacy/backup-and-restorations/setting-up-guest-processing.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.