{"_id":"59fba6b477dc0a0010fff864","project":"55d535ca988e130d000b3f5c","version":{"_id":"55d535cb988e130d000b3f5f","__v":12,"project":"55d535ca988e130d000b3f5c","hasDoc":true,"hasReference":false,"createdAt":"2015-08-20T02:04:59.052Z","releaseDate":"2015-08-20T02:04:59.052Z","categories":["55d535cc988e130d000b3f60","55d6b238d2a8eb1900109eef","55d6b4f3250d7d0d004274cd","55d7967960fc730d00fc2852","55da9804e835f20d009fc5d0","55e75b1de06f4b190080dbfd","55e75b39e06f4b190080dbfe","55e75b7ae06f4b190080dbff","564f5a4e33082f0d001bb709","570fb64aa38d470e0060cbff","586d0dd89a854123001acd65","586d0e3b9a854123001acd66"],"is_deprecated":false,"is_hidden":false,"is_beta":false,"is_stable":true,"codename":"","version_clean":"1.0.0","version":"1.0"},"category":{"_id":"55e75b39e06f4b190080dbfe","project":"55d535ca988e130d000b3f5c","__v":10,"pages":["56959043fe18811700c9c09e","569590bfcb14e11700f8a877","569590f7fcb1032d0089e033","5695917dfcb1032d0089e035","5695964a77ba0d2300cf3912","5695967edcaf0d1700cb8752","569618eccb14e11700f8a910","56961d937596a90d0014e571","5696ba13480534370022a37a","56dd002ee5c8570e00a79865"],"version":"55d535cb988e130d000b3f5f","sync":{"url":"","isSync":false},"reference":false,"createdAt":"2015-09-02T20:25:29.622Z","from_sync":false,"order":3,"slug":"frame-for-business","title":"Frame for Business"},"user":"5910f1a2657bf91b00bf9d41","__v":0,"parentDoc":null,"updates":[],"next":{"pages":[],"description":""},"createdAt":"2017-11-02T23:13:56.046Z","link_external":false,"link_url":"","githubsync":"","sync_unique":"","hidden":false,"api":{"results":{"codes":[]},"settings":"","auth":"required","params":[],"url":""},"isReference":false,"order":3,"body":"In addition to running individual applications in a browser, you can enable your users to access a complete Windows desktop running on Frame. By running a full desktop, your users have access to all of the applications installed on your Sandbox, whether or not you've onboarded them. \n[block:image]\n{\n  \"images\": [\n    {\n      \"image\": [\n        \"https://files.readme.io/81b5a4e-desktopmode1.png\",\n        \"desktopmode1.png\",\n        1446,\n        740,\n        \"#3a3d4a\"\n      ],\n      \"caption\": \"A Frame session running in desktop mode\"\n    }\n  ]\n}\n[/block]\nIn desktop mode, users can see and access the C: drive, install software, run Windows Explorer, use the Windows taskbar and system tray, place icons on their desktop, and more. While this results in an environment that is not as locked-down as when you are presenting a select set of apps, you are still running on stateless instances that will return to their original state after the end of a session. It's therefore important that your users know that they are running on a stateless environment to set expectations properly.  Of course, you can persist user preferences and configurations for authenticated users, provided you configure which registries, files, and folders to persist (see [this article](https://docs.fra.me/docs/persist-user-preferences) for more details). \n\nPresenting a full desktop to your users is beneficial for a variety of use cases ranging from training to complex multi-app workflows to simply presenting a familiar environment.\n\n# Enabling Desktop mode\n\nDesktop mode must first be enabled at the account level. If you have access to your account settings (e.g. you have a Frame Platform Ultimate tier account with Super Admin access), you can enable the desktop feature by going to your account page and turning on the slider called \"Show desktop option\" as shown below:  \n[block:image]\n{\n  \"images\": [\n    {\n      \"image\": [\n        \"https://files.readme.io/148dc0b-Screen_Shot_2017-12-29_at_3.49.09_PM.png\",\n        \"Screen Shot 2017-12-29 at 3.49.09 PM.png\",\n        350,\n        195,\n        \"#d1d6d9\"\n      ]\n    }\n  ]\n}\n[/block]\nIf you do not have a Frame Platform Ultimate account, you can contact [support:::at:::fra.me](mailto:support@fra.me) and request that they enable the desktop option for your account.\n\nOnce enabled on your account, you can simply enable the \"Desktop\" slider in your Launchpad's gear menu. It's just like selecting another application to present in your Launchpad.\n[block:image]\n{\n  \"images\": [\n    {\n      \"image\": [\n        \"https://files.readme.io/624e0e4-desktopenable.png\",\n        \"desktopenable.png\",\n        366,\n        284,\n        \"#2f4e66\"\n      ]\n    }\n  ]\n}\n[/block]\nThe icon for launching a full desktop session will then show up and will look like this:\n[block:image]\n{\n  \"images\": [\n    {\n      \"image\": [\n        \"https://files.readme.io/6606d19-Screen_Shot_2017-12-29_at_4.01.39_PM.png\",\n        \"Screen Shot 2017-12-29 at 4.01.39 PM.png\",\n        131,\n        126,\n        \"#445b6e\"\n      ]\n    }\n  ]\n}\n[/block]\n## Using Desktop mode\n\nUsing desktop mode is overall very similar to using Frame by launching an application, but there are a few things you should know before getting started. \n\nDesktop mode and application launch mode cannot be used together in the same user's Launchpad. So in general, you should not have the desktop icon and other application icons visible in your Launchpad. \n[block:callout]\n{\n  \"type\": \"warning\",\n  \"title\": \"Do not enable the desktop mode with application launch mode in the same Launchpad\",\n  \"body\": \"When enabling desktop mode for your users, you must hide any onboarded applications from their Launchpad. This is important, because desktop mode and application mode apply different settings to the session.\"\n}\n[/block]\nIf your use case requires that some users in an account have access to a desktop while others will just use the application launch mode, you can create separate application groups for the two user groups within the same account as in the example below.  \n[block:image]\n{\n  \"images\": [\n    {\n      \"image\": [\n        \"https://files.readme.io/2d847b3-appgroups2.png\",\n        \"appgroups2.png\",\n        477,\n        233,\n        \"#3f5667\"\n      ],\n      \"caption\": \"An example of two separate application groups -- \\\"Desktop\\\" and \\\"Browsing.\\\"\"\n    }\n  ]\n}\n[/block]\nYou can read more on how to set up different application groups [here](https://docs.fra.me/docs/manage-app-groups). \n\nSeveral other differences between application launch and desktop modes include:\n\n- With desktop mode, your users have direct access to the C: drive so they can see any files/data that you may have stored in your Sandbox image. As a best practice, you should remove any installers that you downloaded to the Sandbox after installation - especially if you wish to prevent access to them. \n\n- Desktop users will have administrative privileges on the machine. This means that they could install applications - although they would not persist past their session.  \n\n- Unlike in application mode, where a web link is set to open in the user's local browser by default, when running in the desktop, links will open within the default browser (Chrome) inside the Frame instance.\n\n- When running in application mode, the Frame application switcher (ALT + TAB on Mac or ALT +  ~ on PC) is invoked to toggle between applications. In desktop mode, the native Windows application switcher is used but still uses the same key combinations. \n\nWhile you don't have to onboard individual applications with desktop mode, you still have to install and manage the version of your apps on your Sandbox and publish updates as needed. Other than the items above, though, managing your desktop deployment on Frame is just as easy as managing applications.","excerpt":"Give users access to a familiar Windows desktop environment","slug":"run-desktops","type":"basic","title":"Run full desktops"}

Run full desktops

Give users access to a familiar Windows desktop environment

In addition to running individual applications in a browser, you can enable your users to access a complete Windows desktop running on Frame. By running a full desktop, your users have access to all of the applications installed on your Sandbox, whether or not you've onboarded them. [block:image] { "images": [ { "image": [ "https://files.readme.io/81b5a4e-desktopmode1.png", "desktopmode1.png", 1446, 740, "#3a3d4a" ], "caption": "A Frame session running in desktop mode" } ] } [/block] In desktop mode, users can see and access the C: drive, install software, run Windows Explorer, use the Windows taskbar and system tray, place icons on their desktop, and more. While this results in an environment that is not as locked-down as when you are presenting a select set of apps, you are still running on stateless instances that will return to their original state after the end of a session. It's therefore important that your users know that they are running on a stateless environment to set expectations properly. Of course, you can persist user preferences and configurations for authenticated users, provided you configure which registries, files, and folders to persist (see [this article](https://docs.fra.me/docs/persist-user-preferences) for more details). Presenting a full desktop to your users is beneficial for a variety of use cases ranging from training to complex multi-app workflows to simply presenting a familiar environment. # Enabling Desktop mode Desktop mode must first be enabled at the account level. If you have access to your account settings (e.g. you have a Frame Platform Ultimate tier account with Super Admin access), you can enable the desktop feature by going to your account page and turning on the slider called "Show desktop option" as shown below: [block:image] { "images": [ { "image": [ "https://files.readme.io/148dc0b-Screen_Shot_2017-12-29_at_3.49.09_PM.png", "Screen Shot 2017-12-29 at 3.49.09 PM.png", 350, 195, "#d1d6d9" ] } ] } [/block] If you do not have a Frame Platform Ultimate account, you can contact [support@fra.me](mailto:support@fra.me) and request that they enable the desktop option for your account. Once enabled on your account, you can simply enable the "Desktop" slider in your Launchpad's gear menu. It's just like selecting another application to present in your Launchpad. [block:image] { "images": [ { "image": [ "https://files.readme.io/624e0e4-desktopenable.png", "desktopenable.png", 366, 284, "#2f4e66" ] } ] } [/block] The icon for launching a full desktop session will then show up and will look like this: [block:image] { "images": [ { "image": [ "https://files.readme.io/6606d19-Screen_Shot_2017-12-29_at_4.01.39_PM.png", "Screen Shot 2017-12-29 at 4.01.39 PM.png", 131, 126, "#445b6e" ] } ] } [/block] ## Using Desktop mode Using desktop mode is overall very similar to using Frame by launching an application, but there are a few things you should know before getting started. Desktop mode and application launch mode cannot be used together in the same user's Launchpad. So in general, you should not have the desktop icon and other application icons visible in your Launchpad. [block:callout] { "type": "warning", "title": "Do not enable the desktop mode with application launch mode in the same Launchpad", "body": "When enabling desktop mode for your users, you must hide any onboarded applications from their Launchpad. This is important, because desktop mode and application mode apply different settings to the session." } [/block] If your use case requires that some users in an account have access to a desktop while others will just use the application launch mode, you can create separate application groups for the two user groups within the same account as in the example below. [block:image] { "images": [ { "image": [ "https://files.readme.io/2d847b3-appgroups2.png", "appgroups2.png", 477, 233, "#3f5667" ], "caption": "An example of two separate application groups -- \"Desktop\" and \"Browsing.\"" } ] } [/block] You can read more on how to set up different application groups [here](https://docs.fra.me/docs/manage-app-groups). Several other differences between application launch and desktop modes include: - With desktop mode, your users have direct access to the C: drive so they can see any files/data that you may have stored in your Sandbox image. As a best practice, you should remove any installers that you downloaded to the Sandbox after installation - especially if you wish to prevent access to them. - Desktop users will have administrative privileges on the machine. This means that they could install applications - although they would not persist past their session. - Unlike in application mode, where a web link is set to open in the user's local browser by default, when running in the desktop, links will open within the default browser (Chrome) inside the Frame instance. - When running in application mode, the Frame application switcher (ALT + TAB on Mac or ALT + ~ on PC) is invoked to toggle between applications. In desktop mode, the native Windows application switcher is used but still uses the same key combinations. While you don't have to onboard individual applications with desktop mode, you still have to install and manage the version of your apps on your Sandbox and publish updates as needed. Other than the items above, though, managing your desktop deployment on Frame is just as easy as managing applications.