{"id":14724,"date":"2020-05-28T10:20:20","date_gmt":"2020-05-28T08:20:20","guid":{"rendered":"https:\/\/www.praim.com\/?p=14724"},"modified":"2020-05-29T14:42:11","modified_gmt":"2020-05-29T12:42:11","slug":"how-to-deploy-thinman-in-azure-for-your-remote-working","status":"publish","type":"post","link":"https:\/\/www.praim.com\/en\/news\/how-to-deploy-thinman-in-azure-for-your-remote-working\/","title":{"rendered":"How to deploy ThinMan in Azure for your remote working"},"content":{"rendered":"

With most businesses now supporting the majority of their workforce from home, it requires that organizations use the tools and solutions that allow and empower their business to support the remote workforce effectively and securely.<\/strong> Praim\u2019s solutions including the updated ThinMan Server, ThinOX and Agile products allows businesses to easily and seamlessly support the remote workforce who make use of managed solutions (either thin clients, laptops or personal computers) for accessing business-critical resources.<\/p>\n

With little effort, your business can stand up a ThinMan Server in the cloud, install a trusted certificate and connect\u00a0devices\u00a0to ThinMan in only a few steps. In this walkthrough, we will take a look at just how easy it is to provision your Praim infrastructure in the cloud<\/strong> and support the remote workforce with centralized management and administration of endpoints.<\/p>\n

Recent Praim Updates Streamline the Process<\/strong><\/h3>\n

Praim has drastically simplified the steps required to provision end user clients with Praim solutions with recent updates to the product portfolio. With ThinMan Server 8.0 and higher, a new connectivity architecture was introduced called\u00a0Web Socket Secure.<\/strong>\u00a0What is this?<\/p>\n

With the new web socket secure architecture, the number of network ports that are required for communicating back to the ThinMan Server is reduced down to only needing\u00a0TCP port 443<\/strong>. This helps to greatly simplify the management configuration of the network connections that are needed for remote workers.<\/p>\n

When managing remote workers who are working from home, administrators have to deal with the wide range of home networks that exist for remote employees. End users may not have the technical skills needed to troubleshoot network connectivity or provision the network requirements needed for connecting back to thin client infrastructure.<\/p>\n

Reducing the connectivity requirement down<\/strong> to TCP port 443 helps to ensure that connectivity can be easily established between remote work environments at home and the corporate infrastructure using Praim solutions since TCP port 443 is generally a default outbound port that is open on most networks.<\/p>\n

This simplification provides the connectivity needed to give your organization the flexibility to stand up a ThinMan Server anywhere, including the cloud and managing end user environments, even in home networks.<\/p>\n

Deploying ThinMan in Azure<\/h3>\n

Let\u2019s take a look at the example of deploying a ThinMan Server in Azure. This is as simple as deploying a Windows Server in Azure and then installing the ThinMan Server installation. First, let\u2019s deploy a Windows Server in our Azure environment.<\/p>\n

\"Deploying

Deploying a Windows Server VM in Microsoft Azure as a ThinMan host<\/em><\/p><\/div>\n

Once you have a virtual machine provisioned in Azure, it is as simple as installing the ThinMan Server on the virtual machine. Note the ports that are configured by default. With secure SSL traffic, this is port 443.<\/p>\n

\"Installing

Installing ThinMan Server on an Azure virtual machine<\/em><\/p><\/div>\n

With a simple \u201cnext, next, finish\u201d installer, ThinMan Server is installed quickly and easily.<\/p>\n

\"ThinMan

ThinMan Server is successfully installed on the Azure virtual machine<\/em><\/p><\/div>\n

With Microsoft Azure, you have to add ports in the \u201cnetwork security group\u201d configuration<\/strong> for the virtual machine for allowing ingress traffic into the virtual machine. This is a simple process with ThinMan Server since we only have to allow port 443 inbound for connections from clients. This also streamlines the management of network security group inbound rules for your ThinMan Server.<\/p>\n

As mentioned earlier, this makes things extremely simple and straightforward from the client connection side since there is only a single port that needs opened for outbound traffic. Below, we are adding the required TCP port 443 inbound to the ThinMan Server in the Azure IaaS environment. This is found in\u00a0Networking > Inbound port rules<\/strong>\u00a0of the Azure virtual machine properties.<\/p>\n

\"Azure

Adding the required Azure network security group inbound port rule for communicating with ThinMan<\/em><\/p><\/div>\n

Adding end user clients to ThinMan Server housed in Azure<\/h3>\n

Once the inbound rule is in place for your ThinMan Azure virtual machine, end user clients can now successfully connect to the ThinMan Server hosted in Azure.<\/p>\n

While installing\u00a0Agile<\/a><\/strong>\u00a0on the device, in order to activate the product, the user will be requested to insert the ThinMan address.<\/p>\n

\"Agile\"<\/p>\n

As you can see below, hitting the ThinMan Server with the Azure-assigned public IP address is successful.<\/p>\n

\"Agile

Client successfully connects to the Azure-hosted ThinMan Server<\/em><\/p><\/div>\n

Once you test the server connection to the ThinMan Server, you will see the client device register with the ThinMan Server as seen below.<\/p>\n

\"ThinMan

After testing the connection to the ThinMan Server, the end user client is registered with the ThinMan Server<\/em><\/p><\/div>\n

Once the end user client is registered with the ThinMan Server, you can perform all the common management actions<\/strong> to control the endpoint from ThinMan Server including:<\/p>\n