Frame Guest Agent (FGA) has native support for proxy servers. Customers may configure the FGA to use an outbound proxy server if a proxy server is required for outbound HTTPS and Secure WebSocket traffic to the Internet. Windows administrators must explicitly set the FGA proxy settings and have those settings persist:
- After a sysprep (during publishing of workload VMs that must be joined to a Windows domain),
- After the domain-joined workload VMs are powered on, or
- When an end user logs into their Windows domain (changes to UEM policy or GPOs).
The FGA proxy configuration does not affect the Windows OS, user, or third-party application proxy settings.
Using the FrameProxyHelper tool which is available in
C:\ProgramData\Nutanix\Frame\Tools, configure all required fields and verify the configuration by clicking the "Start test" button. The images below show a successful proxy test.
Depending on your environment, you can test predefined Commercial or Government endpoints. You can also use custom endpoints by clicking on the “Custom” button, adding your endpoints to the list and confirming with the green check mark button.
Lastly, save your settings by clicking the "Save Settings" button. Reboot the VM in order for your changes to take effect.
For AHV, we recommend this proxy server configuration be done in the Windows template images. If sysprep removes the proxy server settings, you will have to connect into the Sandbox using RDP, after the Frame account is created, to update the FGA's proxy server settings.
To remove the Frame Guest Agent proxy server configuration to troubleshoot, go to the Sandbox and (using regedit) delete the contents of: