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

How to check in AngularJS if a service was register or not

There are cases when you need to check in a service or a controller was register in AngularJS.
For example a valid use case is when you have the same implementation running on multiple application. In this case, you may want to intercept the HTTP provider and add a custom step there. This step don’t needs to run on all the application, only in the one where the service exist and register.
A solution for this case would be to have a flag in the configuration that specify this. In the core you would have an IF that would check the value of this flag.
Another solution is to check if a specific service was register in AngularJS or not. If the service was register that you would execute your own logic.
To check if a service was register or not in AngularJS container you need to call the ‘has’ method of ‘inhector’. It will return TRUE if the service was register.
if ($injector.has('httpInterceptorService')) { $httpProvider.interceptors.push('httpInterceptorService&#…

ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded

Today blog post will be started with the following error when running DB tests on the CI machine:
threw exception: System.InvalidOperationException: The Entity Framework provider type 'System.Data.Entity.SqlServer.SqlProviderServices, EntityFramework.SqlServer' registered in the application config file for the ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded. Make sure that the assembly-qualified name is used and that the assembly is available to the running application. See http://go.microsoft.com/fwlink/?LinkId=260882 for more information. at System.Data.Entity.Infrastructure.DependencyResolution.ProviderServicesFactory.GetInstance(String providerTypeName, String providerInvariantName) This error happened only on the Continuous Integration machine. On the devs machines, everything has fine. The classic problem – on my machine it’s working. The CI has the following configuration:

TeamCity.NET 4.51EF 6.0.2VS2013
It seems that there …

Run native .NET application in Docker (.NET Framework 4.6.2)

Scope
The main scope of this post is to see how we can run a legacy application written in .NET Framework in Docker.

Context
First of all, let’s define what is a legacy application in our context. By a legacy application we understand an application that runs .NET Framework 3.5 or higher in a production environment where we don’t have any more the people or documentation that would help us to understand what is happening behind the scene.
In this scenarios, you might want to migrate the current solution from a standard environment to Docker. There are many advantages for such a migration, like:

Continuous DeploymentTestingIsolationSecurity at container levelVersioning ControlEnvironment Standardization
Until now, we didn’t had the possibility to run a .NET application in Docker. With .NET Core, there was support for .NET Core in Docker, but migration from a full .NET framework to .NET Core can be costly and even impossible. Not only because of lack of features, but also because once you…