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.

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(

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.51 EF 6.0.2 VS2013 It see

Navigating Cloud Strategy after Azure Central US Region Outage

Looking back, July 19, 2024, was challenging for customers using Microsoft Azure or Windows machines. Two major outages affected customers using CrowdStrike Falcon or Microsoft Azure computation resources in the Central US. These two outages affected many people and put many businesses on pause for a few hours or even days. The overlap of these two issues was a nightmare for travellers. In addition to blue screens in the airport terminals, they could not get additional information from the airport website, airline personnel, or the support line because they were affected by the outage in the Central US region or the CrowdStrike outage. But what happened in reality? A faulty CrowdStrike update affected Windows computers globally, from airports and healthcare to small businesses, affecting over 8.5m computers. Even if the Falson Sensor software defect was identified and a fix deployed shortly after, the recovery took longer. In parallel with CrowdStrike, Microsoft provided a too

Cloud as a Story - Vunvulea Radu

Search This Blog