{"__v":17,"_id":"55d537895082980d0009c96b","category":{"__v":10,"_id":"55e75b39e06f4b190080dbfe","pages":["56959043fe18811700c9c09e","569590bfcb14e11700f8a877","569590f7fcb1032d0089e033","5695917dfcb1032d0089e035","5695964a77ba0d2300cf3912","5695967edcaf0d1700cb8752","569618eccb14e11700f8a910","56961d937596a90d0014e571","5696ba13480534370022a37a","56dd002ee5c8570e00a79865"],"project":"55d535ca988e130d000b3f5c","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"},"parentDoc":null,"project":"55d535ca988e130d000b3f5c","user":"55d535835082980d0009c965","version":{"__v":12,"_id":"55d535cb988e130d000b3f5f","hasDoc":true,"hasReference":false,"project":"55d535ca988e130d000b3f5c","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"},"updates":[],"next":{"pages":[],"description":""},"createdAt":"2015-08-20T02:12:25.042Z","link_external":false,"link_url":"","githubsync":"","sync_unique":"","hidden":false,"api":{"results":{"codes":[]},"settings":"","auth":"required","params":[],"url":""},"isReference":false,"order":0,"body":"Onboarding an application for the team of users with your account registers the application with the Frame backend and prepares it for sharing via a browser. The process for Frame for Business/Education and Frame Platform is slightly different from onboarding in a Frame Personal account, so follow the steps below closely: \n[block:api-header]\n{\n  \"type\": \"basic\",\n  \"title\": \"1.  Launch the sandbox from your Dashboard\"\n}\n[/block]\nLaunch your account's sandbox desktop from your Dashboard view. If you are in the Launchpad view, click \"Go to Dashboard\" from the admin menu in the upper left corner:\n[block:image]\n{\n  \"images\": [\n    {\n      \"image\": [\n        \"https://files.readme.io/TjzDnx7RQulOLJc3caOA_Open%20Dashboard.gif\",\n        \"Open Dashboard.gif\",\n        \"355\",\n        \"479\",\n        \"#244a6e\",\n        \"\"\n      ]\n    }\n  ]\n}\n[/block]\nFrom the \"Apps\" section of your Dashboard, check that you are in the \"Sandbox\" tab and scroll to the bottom, where you will see your Sandbox:   \n[block:image]\n{\n  \"images\": [\n    {\n      \"image\": [\n        \"https://files.readme.io/EZlsgjyqSuu5Q2BAl5Ed_Screenshot%202016-01-13%2000.46.02.png\",\n        \"Screenshot 2016-01-13 00.46.02.png\",\n        \"1236\",\n        \"838\",\n        \"#3b7ab3\",\n        \"\"\n      ]\n    }\n  ]\n}\n[/block]\nClick on \"Power on\" on the image of the sandbox desktop (this takes about 2-3 minutes) -- and then click on \"Open Desktop:\"\n[block:image]\n{\n  \"images\": [\n    {\n      \"image\": [\n        \"https://files.readme.io/8phe4e15RFbnCaw3pvBQ_Screenshot%202016-01-13%2000.30.50.png\",\n        \"Screenshot 2016-01-13 00.30.50.png\",\n        \"672\",\n        \"140\",\n        \"#75b0aa\",\n        \"\"\n      ]\n    }\n  ]\n}\n[/block]\n\n[block:callout]\n{\n  \"type\": \"warning\",\n  \"title\": \"IMPORTANT\",\n  \"body\": \"If your applications require a GPU to install and run, you need to make sure that you set your Sandbox system to at least a Pro 16GB instance (with NVIDIA GRID GPU). To do this:\\n\\n1. Check that your Launchpad is set to connect to your Sandbox (from Dashboard/Settings page and General tab, make sure that the first setting \\\"Connect launchpad apps to:\\\" is set to \\\"Sandbox\\\").\\n\\n2. Go to your Launchpad and scroll down to the \\\"System\\\" section and make sure your current system is the Pro 16GB (or higher).\"\n}\n[/block]\n\n[block:api-header]\n{\n  \"type\": \"basic\",\n  \"title\": \"2.  Upload your installer\"\n}\n[/block]\nIf your installer is available online, you can download it directly using the browser (Chrome) in your sandbox desktop -- this will be the fastest method for large installers since your sandbox typically has a network bandwidth of over 500 Mbps. \n\nIf your installer is not available online, and you have it on your local machine, you can upload it to a cloud storage account (e.g., Dropbox, Google Drive, or Box) and then access that account from the browser in your Sandbox. Additionally, you can opt to connect your cloud storage account to your Frame account, which would enable you to see the files in a virtual drive in your Sandbox (e.g., Box = X: drive). You can connect your cloud storage accounts from the Dashboard (to the right of the Sandbox image) or from within your desktop/sandbox session by clicking on the icons at the bottom right corner of your desktop session.  \n[block:api-header]\n{\n  \"type\": \"basic\",\n  \"title\": \"3.  Install and onboard your application\"\n}\n[/block]\nIf you downloaded your installer using the browser in the sandbox, simply launch the setup file from the downloads folder.\n\nIf you used a cloud storage account, navigate to \"Computer\" and open the appropriate drive (e.g., X: drive for Box).\n[block:callout]\n{\n  \"type\": \"warning\",\n  \"title\": \"IMPORTANT\",\n  \"body\": \"Copy your setup file(s) from the original drive to the C: drive, and then run the installation of your app as you would on a PC from the C: drive.\"\n}\n[/block]\nAccept the Frame prompts to onboard your application. \n\nNote that if you did not see the onboarding dialog, have skipped this step earlier, or wish to onboard an existing application, simply right-click on the application in the program menu or directly on the application's .exe file in its install folder and select \"Onboard to Frame.\"\n\n\n[block:image]\n{\n  \"images\": [\n    {\n      \"image\": [\n        \"https://files.readme.io/X67gb3zUTCqvqqRpURPb_onboard.jpg\",\n        \"onboard.jpg\",\n        \"367\",\n        \"581\",\n        \"#7494cc\",\n        \"\"\n      ]\n    }\n  ]\n}\n[/block]\nOnce you've installed the application, be sure to delete the installer from the C: drive to conserve space on your system.\n[block:api-header]\n{\n  \"type\": \"basic\",\n  \"title\": \"4.  Test your application\"\n}\n[/block]\nFirst, run your application from within the Sandbox desktop to make sure everything is functioning as expected (e.g., if you need to enter a license code, or load a license file, do so now).\n\nNow disconnect (\"Disconnect\" or \"Quit\") from your desktop/sandbox, and you'll see a new app icon in your Dashboard. Test your app again by clicking on its icon in the Sandbox tab. This time you'll confirm that the app runs in your browser without the full desktop being shown.\n\nYou can also test the app running in the Sandbox from the Launchpad. To do so, take these steps:\n\n  * Make sure your Launchpad is set to run apps in the Sandbox (only do this while in development and NOT when you already have production users on your system). Set this from the Settings page/General tab: \n[block:image]\n{\n  \"images\": [\n    {\n      \"image\": [\n        \"https://files.readme.io/h3p09worRXaxSh2KdHIp_Screenshot%202016-01-13%2001.01.38.png\",\n        \"Screenshot 2016-01-13 01.01.38.png\",\n        \"526\",\n        \"340\",\n        \"#4371a0\",\n        \"\"\n      ]\n    }\n  ]\n}\n[/block]\nThen set the application to show in the Launchpad by switching the \"Show App?\" slider for the app to the on position in the Launchpad settings:\n[block:image]\n{\n  \"images\": [\n    {\n      \"image\": [\n        \"https://files.readme.io/P0x7xa5GRDaUkDa5f96g_Screenshot%202016-01-12%2022.16.13.png\",\n        \"Screenshot 2016-01-12 22.16.13.png\",\n        \"370\",\n        \"203\",\n        \"#5e7b90\",\n        \"\"\n      ]\n    }\n  ]\n}\n[/block]\nNow, if all worked well in launching your app from within the Sandbox desktop, from the Dashboard, and from the Launchpad, you're ready to proceed to the next steps: setting production capacity and publishing.\n[block:callout]\n{\n  \"type\": \"warning\",\n  \"body\": \"Note that Frame uses hours in increments of one hour. Booting a Sandbox or Production instance will consume one hour of usage, even if you shut it down after just a few minutes. Also, anytime you publish - you will incur one hour of usage for each of the instances in your production \\\"pool\\\" -whose size is determined by your \\\"maximum\\\" capacity setting.  (Our instances currently run on Amazon Web Services, which bills in one hour increments).\",\n  \"title\": \"Usage calculations are in one hour increments\"\n}\n[/block]","excerpt":"Learn how to install and onboard applications for your team","slug":"onboarding-applications","type":"basic","title":"Onboard apps for your team"}

Onboard apps for your team

Learn how to install and onboard applications for your team

Onboarding an application for the team of users with your account registers the application with the Frame backend and prepares it for sharing via a browser. The process for Frame for Business/Education and Frame Platform is slightly different from onboarding in a Frame Personal account, so follow the steps below closely: [block:api-header] { "type": "basic", "title": "1. Launch the sandbox from your Dashboard" } [/block] Launch your account's sandbox desktop from your Dashboard view. If you are in the Launchpad view, click "Go to Dashboard" from the admin menu in the upper left corner: [block:image] { "images": [ { "image": [ "https://files.readme.io/TjzDnx7RQulOLJc3caOA_Open%20Dashboard.gif", "Open Dashboard.gif", "355", "479", "#244a6e", "" ] } ] } [/block] From the "Apps" section of your Dashboard, check that you are in the "Sandbox" tab and scroll to the bottom, where you will see your Sandbox: [block:image] { "images": [ { "image": [ "https://files.readme.io/EZlsgjyqSuu5Q2BAl5Ed_Screenshot%202016-01-13%2000.46.02.png", "Screenshot 2016-01-13 00.46.02.png", "1236", "838", "#3b7ab3", "" ] } ] } [/block] Click on "Power on" on the image of the sandbox desktop (this takes about 2-3 minutes) -- and then click on "Open Desktop:" [block:image] { "images": [ { "image": [ "https://files.readme.io/8phe4e15RFbnCaw3pvBQ_Screenshot%202016-01-13%2000.30.50.png", "Screenshot 2016-01-13 00.30.50.png", "672", "140", "#75b0aa", "" ] } ] } [/block] [block:callout] { "type": "warning", "title": "IMPORTANT", "body": "If your applications require a GPU to install and run, you need to make sure that you set your Sandbox system to at least a Pro 16GB instance (with NVIDIA GRID GPU). To do this:\n\n1. Check that your Launchpad is set to connect to your Sandbox (from Dashboard/Settings page and General tab, make sure that the first setting \"Connect launchpad apps to:\" is set to \"Sandbox\").\n\n2. Go to your Launchpad and scroll down to the \"System\" section and make sure your current system is the Pro 16GB (or higher)." } [/block] [block:api-header] { "type": "basic", "title": "2. Upload your installer" } [/block] If your installer is available online, you can download it directly using the browser (Chrome) in your sandbox desktop -- this will be the fastest method for large installers since your sandbox typically has a network bandwidth of over 500 Mbps. If your installer is not available online, and you have it on your local machine, you can upload it to a cloud storage account (e.g., Dropbox, Google Drive, or Box) and then access that account from the browser in your Sandbox. Additionally, you can opt to connect your cloud storage account to your Frame account, which would enable you to see the files in a virtual drive in your Sandbox (e.g., Box = X: drive). You can connect your cloud storage accounts from the Dashboard (to the right of the Sandbox image) or from within your desktop/sandbox session by clicking on the icons at the bottom right corner of your desktop session. [block:api-header] { "type": "basic", "title": "3. Install and onboard your application" } [/block] If you downloaded your installer using the browser in the sandbox, simply launch the setup file from the downloads folder. If you used a cloud storage account, navigate to "Computer" and open the appropriate drive (e.g., X: drive for Box). [block:callout] { "type": "warning", "title": "IMPORTANT", "body": "Copy your setup file(s) from the original drive to the C: drive, and then run the installation of your app as you would on a PC from the C: drive." } [/block] Accept the Frame prompts to onboard your application. Note that if you did not see the onboarding dialog, have skipped this step earlier, or wish to onboard an existing application, simply right-click on the application in the program menu or directly on the application's .exe file in its install folder and select "Onboard to Frame." [block:image] { "images": [ { "image": [ "https://files.readme.io/X67gb3zUTCqvqqRpURPb_onboard.jpg", "onboard.jpg", "367", "581", "#7494cc", "" ] } ] } [/block] Once you've installed the application, be sure to delete the installer from the C: drive to conserve space on your system. [block:api-header] { "type": "basic", "title": "4. Test your application" } [/block] First, run your application from within the Sandbox desktop to make sure everything is functioning as expected (e.g., if you need to enter a license code, or load a license file, do so now). Now disconnect ("Disconnect" or "Quit") from your desktop/sandbox, and you'll see a new app icon in your Dashboard. Test your app again by clicking on its icon in the Sandbox tab. This time you'll confirm that the app runs in your browser without the full desktop being shown. You can also test the app running in the Sandbox from the Launchpad. To do so, take these steps: * Make sure your Launchpad is set to run apps in the Sandbox (only do this while in development and NOT when you already have production users on your system). Set this from the Settings page/General tab: [block:image] { "images": [ { "image": [ "https://files.readme.io/h3p09worRXaxSh2KdHIp_Screenshot%202016-01-13%2001.01.38.png", "Screenshot 2016-01-13 01.01.38.png", "526", "340", "#4371a0", "" ] } ] } [/block] Then set the application to show in the Launchpad by switching the "Show App?" slider for the app to the on position in the Launchpad settings: [block:image] { "images": [ { "image": [ "https://files.readme.io/P0x7xa5GRDaUkDa5f96g_Screenshot%202016-01-12%2022.16.13.png", "Screenshot 2016-01-12 22.16.13.png", "370", "203", "#5e7b90", "" ] } ] } [/block] Now, if all worked well in launching your app from within the Sandbox desktop, from the Dashboard, and from the Launchpad, you're ready to proceed to the next steps: setting production capacity and publishing. [block:callout] { "type": "warning", "body": "Note that Frame uses hours in increments of one hour. Booting a Sandbox or Production instance will consume one hour of usage, even if you shut it down after just a few minutes. Also, anytime you publish - you will incur one hour of usage for each of the instances in your production \"pool\" -whose size is determined by your \"maximum\" capacity setting. (Our instances currently run on Amazon Web Services, which bills in one hour increments).", "title": "Usage calculations are in one hour increments" } [/block]