AWS Workspaces vs Azure Virtual Desktop

There are not too many things more stressful than working in IT and hearing your manager tell your team that the company is going fully remote in a couple of weeks and your team needs to be ready to support that shift! Any of us that were working in the IT world in early 2020 can certainly relate! If you’re ever faced with this challenge, many things will probably race across your mind. How will we provide the hardware and software required for the employees to do their jobs?

Using a cloud provider to provide virtual desktop infrastructure (VDI) to your employees is a great way to solve many of these cloud enablement issues, so let’s take a look at Azure Virtual Desktop (formerly Windows Virtual Desktop) and AWS Workspaces to find the fit that’s best for you.

What’s a Virtual Desktop?

In short, we can utilize Azure, AWS or many other options to provide virtual desktops to users that have the applications they need either pre-installed or provided as needed. Now you could just deploy a virtual machine and call that a virtual desktop, but if you want scalability, security, ease of use, and more, you’ll want to go with a virtual desktop infrastructure solution.


Comparing Azure Virtual Desktop to AWS Workspaces

Let’s say you work at ABC Inc, a company that produces food products and garden designs. You just got word that the designers, call center employees, and finance departments are going fully remote. Thankfully, you’ve been keeping up to date with the cloud world and you know you can use either Azure VDI or AWS Workspaces to provide virtual desktops for your co-workers, but which one should you choose? Let’s take a look and help our little gnome friends out!

Comments

Post a Comment

Popular posts from this blog

Create a Public Load balancer

Image
Sign in to Azure Sign in to the Azure portal at   https://portal.azure.com . Create the virtual network: In this section, you'll create a virtual network and subnet. In the search box at the top of the portal, enter  Virtual network . Select  Virtual Networks  in the search results. In  Virtual networks , select  + Create . In  Create virtual network , enter or select this information in the  Basics  tab: TABLE 1 Setting Value Project Details Subscription Select your Azure subscription Resource Group Select  Create new . In  Name  enter  CreatePubLBQS-rg . Select  OK . Instance details Name Enter  myVNet Region Select  (Europe) West Europe Select the  IP Addresses  tab or select the  Next: IP Addresses  button at the bottom of the page. In the  IP Addresses  tab, enter this information: TABLE 2 Setting Value IPv4 address space Enter  10.1.0.0/16 Under  Subnet name , select the word  default . In  Edit subnet , enter this information: TABLE 3 Setting Value Subnet name Enter  myBacke
Read more

Configure Point-to-Site Connection

Image
 Configure Point-to-Site Connection Next step of this configuration is to configure the point-to-site connection. In here we will define client ip address pool as well. It is for VPN clients.   Click on newly created VPN gateway connection. Then in new window click on  Point-to-site configuration   After that, click on  Configure Now   In new window type IP address range for VPN address pool. In this demo I will be using  172.16.25.0/24 . For tunnel type use both  SSTP & IKEv2 . Linux and other mobile clients by default use  IKEv2  to connect. Windows also use  IKEv2  first and then try  SSTP . For authentication type use  Azure Certificates .     In same window there is place to define root certificate. Under root certificate name type the cert name and under public certificate data, paste the root certificate data ( you can open cert in notepad to get data).   Then click on  Save  to complete the process.     Note  : when you paste certificate data, do not copy -----BEGIN CERTIFI
Read more