Instal the new The Sandbox2/5/2024 We recommend increasing the Sandbox Time Limits for this work to prevent your Sandbox session from ending prematurely.Īs a best practice, specific timeout settings to consider increasing are: This is particularly important when Frame admins need ample time to install/configure applications, update their operating system/applications, or to test specific features. You will then be allowed to edit the settings. To override the account settings, simply disable the Use account settings slider. Sandbox Session Settings įrame admins can change the behavior of the session by overriding the default account-level session settings. Increasing the size of the disk should be used with caution as this operation is irreversible. It can be helpful to switch to a GPU-based instance type and then back to a CPU-only instance type for installation/update tasks that don't require a GPU. For example, an admin may wish to install a CAD application that requires a GPU. Install or update applications that require a specific instance type.Test your applications and configuration on Sandbox VMs with a different instance type.Changing the Sandbox instance type can be helpful if you wish to: The Sandbox instance type is defined by the administrator during account creation, however, this can be changed (provided the Sandbox VM is powered off) at any time. Sandbox - Reboot Options Change Instance Type The force reboot option will immediately close the active session and reboot the Sandbox. Choosing reboot will ensure the Sandbox is rebooted once the active Sandbox session is closed. If an administrator chooses to reboot the Sandbox while another admin is accessing it, the system will prompt the admin to choose whether to reboot or force reboot the Sandbox. When the Sandbox is powered on, the admin can power off or reboot the Sandbox by clicking on the kebab menu. Publish your Sandbox changes to be made available to your users. Then, once it's all configured, it's time to deploy or Publish the Sandbox as a disk image to your instances. With your Sandbox in place, you can install apps and customize your experience. Sandbox - Start Session Installing and Publishing If the Sandbox is currently being used by an admin, the system will first prompt you to confirm that you wish to close the existing session. Once the Sandbox is powered on, you can start a session by clicking on the Start Session option. From this page you can power it on, start the Sandbox session, and make desired changes to your operating system and applications. The Sandbox is accessed from the Frame Dashboard menu ( Dashboard > Sandbox). Refer to Persistent Desktop Lifecycle for more details. Already assigned persistent desktops will not receive those Sandbox changes. ![]() For non-persistent Frame accounts, any changes made to the Sandbox image (e.g., updating Windows OS or Linux OS, installing or updating applications) will be served to your users as soon as you Publish.įor persistent desktop Frame accounts, any changes made to the Sandbox image (e.g., updating Windows OS or Linux OS, installing or updating applications) will be made available to new users after you Publish and the new users are assigned to their persistent desktop. ![]() The Sandbox image acts as a template for the rest of your workload VMs. Each Frame Account has a Sandbox - a virtual machine provisioned specifically to allow you to manage the operating system and applications for the Frame account.
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |