{"_id":"5695917dfcb1032d0089e035","user":"55d535835082980d0009c965","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"},"parentDoc":null,"project":"55d535ca988e130d000b3f5c","version":{"_id":"55d535cb988e130d000b3f5f","__v":13,"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","5a613b28da07540012e8ca4a"],"is_deprecated":false,"is_hidden":false,"is_beta":false,"is_stable":true,"codename":"","version_clean":"1.0.0","version":"1.0"},"__v":13,"githubsync":"","updates":["582608d0af422e0f00a9022c","59efb8e48fa369002e2e5fc6"],"next":{"pages":[],"description":""},"createdAt":"2016-01-12T23:51:25.376Z","link_external":false,"link_url":"","sync_unique":"","hidden":false,"api":{"results":{"codes":[]},"settings":"","auth":"required","params":[],"url":""},"isReference":false,"order":12,"body":"A Utility Server is a stand-alone, general purpose Windows server (running Windows Server 2012 R2) that can be added to your account by submitting a request to our support team. This feature is useful for a variety of use cases including:\n\n* **License server**: Install a network licensing manager for your software on a Frame Utility Server. Your production instances can then connect to this server to get the licenses.\n\n* **Backend for a client-server application**: Host a database or other backend function in the utility server directly on your Frame account. Essentially, your entire system can be hosted in the cloud.\n\n* **Shared file server**:  Store files that can be accessed by all of your users.\n\n[block:image]\n{\n  \"images\": [\n    {\n      \"caption\": \"\",\n      \"image\": [\n        \"https://files.readme.io/86916d4-utilityserver2.PNG\",\n        \"utilityserver2.PNG\",\n        1047,\n        406,\n        \"#091322\"\n      ]\n    }\n  ]\n}\n[/block]\nSimilar to your Sandbox, the Utility Server is accessed from the Frame Dashboard, where you can power it on and connect to install applications. However, unlike the Sandbox, **the Utility Server will NOT power off automatically**.  It is typically used for cases where you need the server to run 24x7.  \n\nBy default, the Utility server is configured as a relatively low-powered machine (ideal for being a license server). If you wish to use this for a database or another more demanding back-end function, contact Frame Support to discuss options including high-CPU, high-memory, and SSD-backed instances.\n\nThe Utility Server will be available to the rest of your instances within the VPC/VNet. After setting up your Utility Server, you'll need to open any necessary ports in your Utility Server's Windows Firewall. \n[block:callout]\n{\n  \"type\": \"info\",\n  \"body\": \"Though we typically recommend using the utility server for client-server applications, we understand that connections to on-prem servers might be needed. Getting your application working with an established server from your own network will require one of two scenarios: \\n\\n1. Configure your network to allow outside connections to the server. At that point, you'd configure the application to connect to whatever domain or IP address information you want to use for establishing the connection, and it should work without issue. By default, Frame doesn't restrict outbound connections from our sessions, only inbound ones.\\n\\n2. Configure a VPN tunnel from the instances to your network. This requires the use of a VPN client that allows you to configure the traffic routing rules. For more information on using a VPN with Frame, check out our documentation [here](https://docs.fra.me/docs/setting-up-vpn).\",\n  \"title\": \"Connecting to an on-prem server\"\n}\n[/block]\nYou also have the ability to perform scheduled and manual backups on your Utility Server, just like you would with your Sandbox instance. Check out our documentation [here](https://docs.fra.me/docs/image-backup-and-recovery) for more information.","excerpt":"Setup network licensing manager, client--server apps, and more","slug":"utility-server","type":"basic","title":"Add a utility server"}

Add a utility server

Setup network licensing manager, client--server apps, and more

A Utility Server is a stand-alone, general purpose Windows server (running Windows Server 2012 R2) that can be added to your account by submitting a request to our support team. This feature is useful for a variety of use cases including: * **License server**: Install a network licensing manager for your software on a Frame Utility Server. Your production instances can then connect to this server to get the licenses. * **Backend for a client-server application**: Host a database or other backend function in the utility server directly on your Frame account. Essentially, your entire system can be hosted in the cloud. * **Shared file server**: Store files that can be accessed by all of your users. [block:image] { "images": [ { "caption": "", "image": [ "https://files.readme.io/86916d4-utilityserver2.PNG", "utilityserver2.PNG", 1047, 406, "#091322" ] } ] } [/block] Similar to your Sandbox, the Utility Server is accessed from the Frame Dashboard, where you can power it on and connect to install applications. However, unlike the Sandbox, **the Utility Server will NOT power off automatically**. It is typically used for cases where you need the server to run 24x7. By default, the Utility server is configured as a relatively low-powered machine (ideal for being a license server). If you wish to use this for a database or another more demanding back-end function, contact Frame Support to discuss options including high-CPU, high-memory, and SSD-backed instances. The Utility Server will be available to the rest of your instances within the VPC/VNet. After setting up your Utility Server, you'll need to open any necessary ports in your Utility Server's Windows Firewall. [block:callout] { "type": "info", "body": "Though we typically recommend using the utility server for client-server applications, we understand that connections to on-prem servers might be needed. Getting your application working with an established server from your own network will require one of two scenarios: \n\n1. Configure your network to allow outside connections to the server. At that point, you'd configure the application to connect to whatever domain or IP address information you want to use for establishing the connection, and it should work without issue. By default, Frame doesn't restrict outbound connections from our sessions, only inbound ones.\n\n2. Configure a VPN tunnel from the instances to your network. This requires the use of a VPN client that allows you to configure the traffic routing rules. For more information on using a VPN with Frame, check out our documentation [here](https://docs.fra.me/docs/setting-up-vpn).", "title": "Connecting to an on-prem server" } [/block] You also have the ability to perform scheduled and manual backups on your Utility Server, just like you would with your Sandbox instance. Check out our documentation [here](https://docs.fra.me/docs/image-backup-and-recovery) for more information.