Skip to main content

Azure RemoteApp (Day 26 of 31)

List of all posts from this series: http://vunvulearadu.blogspot.ro/2014/11/azure-blog-post-marathon-is-ready-to.html

Short Description 
Azure RemoteApp gives us the possibility to use Microsoft RemoteApp functionality over Azure infrastructure. A part of services available on Remote Desktop can be used using Azure RemoteApp.


Main Features 
Storage
You are not limited anymore on your on-premises storage. You can use as much space you need when you are using Azure RemoteApp.
Scalability
The hardware limitation generated by your infrastructure is removed. You can use as many resources you need.
Global Reach 
From any point of the glob users can connect to RemoteApp over Azure infrastructure over a secure and reliable channel.
Cross Platform
Users can connect to RemoteApp using any operating system from Windows to iOS to Mac OS and Android.
Hybrid Collections
Allow users to use resources that are hosted on Azure and on-premises backend. In this way you can store resources and data in different locations, based on you needs.
For this kind of connection you will need a Virtual Network between Azure infrastructure and on-premises backend.
Cloud Collection
All the programs and data related to this programs are hosted on Azure.
Office 365 ProPlus or Office 2013 Preinstalled
 Office is preinstalled and ready to be used by all Azure RemoteApp users.
On-premises Active Directory integration
Azure RemoteApp can be integrated with your own AD. In this way users can be managed very easily.
Custom Template Image
If you need custom RemoteApp installed you need to create a custom template image. This can be used to support custom LoB (Line of Business) applications.
Compatibility
Almost all applications that are working with on-premises version of RemoteApp will work with Azure RemoteApp.
Peripheral devices
All peripheral devices like USB, printers or clipboard sharing are supported when you are using Azure Remote App.
Security
In this moment there are two authentication methods supported using Microsoft Accounts and Azure Active Directory.
Windows Embedded
You should be aware that not all versions of Windows Embedded are supported. The fallowing versions of Windows Embedded are supported:

  • Windows Embedded Standard 7 SP1 
  • Windows Embedded 8.1 Industry
  • Windows Embedded POSReady7 
  • Windows Embedded Thin PC 


Limitations 
The only limitations that I can see in this moment is related to Hybrid Collections that requires a Virtual Networked Connection between Azure and your on-premises systems.

Applicable Use Cases 
Below you can find some uses when I would use Azure Remote App.
Remote access to application
I would use Azure Remote App when uses need access to different application remotely.
Custom LoB
When users needs to access LoB application that are complicated to configure.
Multiple versions of programs
Having on the same machine multiple versions of a program can create a lot of issues. Using Azure Remote App this problem can be very easily mitigated.
Hoteling Workspaces
When your company have users that don’t have their own workspaces, Azure RemoteApp can help users to have their own workspaces with all application that are needed.
Remote Desktop Protocol supported
The standard Remote Desktop Protocol is supported by Azure Remote App.

Code Sample 
-

Pros and Cons 
Pros

  • Scalable
  • No hardware dependencies
  • Supports on-premises Active Directory integration 

Cons
-

Pricing 
When you calculate the costs of Azure RemoteApp you need to take into account the following:

  • Type of applications you will run
  • Storage size (per user)
  • Number of hours


Conclusion
Azure RemoApp can be a good solutions for companies that don’t have a dedicated PC for employees or for companies that need to let users to access LoB application from any place from the globe. This is a service that can be used by any company, from the small one to the big one.

Comments

Popular posts from this blog

Windows Docker Containers can make WIN32 API calls, use COM and ASP.NET WebForms

After the last post , I received two interesting questions related to Docker and Windows. People were interested if we do Win32 API calls from a Docker container and if there is support for COM. WIN32 Support To test calls to WIN32 API, let’s try to populate SYSTEM_INFO class. [StructLayout(LayoutKind.Sequential)] public struct SYSTEM_INFO { public uint dwOemId; public uint dwPageSize; public uint lpMinimumApplicationAddress; public uint lpMaximumApplicationAddress; public uint dwActiveProcessorMask; public uint dwNumberOfProcessors; public uint dwProcessorType; public uint dwAllocationGranularity; public uint dwProcessorLevel; public uint dwProcessorRevision; } ... [DllImport("kernel32")] static extern void GetSystemInfo(ref SYSTEM_INFO pSI); ... SYSTEM_INFO pSI = new SYSTEM_INFO(

Azure AD and AWS Cognito side-by-side

In the last few weeks, I was involved in multiple opportunities on Microsoft Azure and Amazon, where we had to analyse AWS Cognito, Azure AD and other solutions that are available on the market. I decided to consolidate in one post all features and differences that I identified for both of them that we should need to take into account. Take into account that Azure AD is an identity and access management services well integrated with Microsoft stack. In comparison, AWS Cognito is just a user sign-up, sign-in and access control and nothing more. The focus is not on the main features, is more on small things that can make a difference when you want to decide where we want to store and manage our users.  This information might be useful in the future when we need to decide where we want to keep and manage our users.  Feature Azure AD (B2C, B2C) AWS Cognito Access token lifetime Default 1h – the value is configurable 1h – cannot be modified

What to do when you hit the throughput limits of Azure Storage (Blobs)

In this post we will talk about how we can detect when we hit a throughput limit of Azure Storage and what we can do in that moment. Context If we take a look on Scalability Targets of Azure Storage ( https://azure.microsoft.com/en-us/documentation/articles/storage-scalability-targets/ ) we will observe that the limits are prety high. But, based on our business logic we can end up at this limits. If you create a system that is hitted by a high number of device, you can hit easily the total number of requests rate that can be done on a Storage Account. This limits on Azure is 20.000 IOPS (entities or messages per second) where (and this is very important) the size of the request is 1KB. Normally, if you make a load tests where 20.000 clients will hit different blobs storages from the same Azure Storage Account, this limits can be reached. How we can detect this problem? From client, we can detect that this limits was reached based on the HTTP error code that is returned by HTTP