AWS AppStreaming a Quick Test Drive

It makes complete sense, why do I want to have a Windows Desktop for? Answer: It depends on the role and profile, ex:

  • Office Worker, with all the traditional tools: Office, Web Browser, Instant Messaging, etc.
  • Knowledge Worker
  • Floor Workers, Assistants, Customer Services, and many others.

 

 

There are many other scenarios where this makes sense in the practical and the economical perspective, I can use the service anywhere I am: At the Office, while on the road and on a Mobile Device.

What I find surprising is that Microsoft didn’t come with this offering, but AWS did. Recently they (Microsoft) cancelled their Remote Desktop Services, which was similar to this, one created the base service, with applications and publish it as a Service, it was very neat and convenient. I wrote some posts about it, here and here

What is Microsoft going to do to substitute it? I don’t know, they mentioned some alternatives, but they were not really appealing in my opinion, using Citrix, with around 6-7 VMs? Not for me.

I believe in SaaS first then PaaS and if nothing else fits the requirement then IaaS.

A Quick Test Drive

On my AWS tenant, I setup an AppStream, I had a $50 Dollar voucher, don’t believe this one qualifies for the free tier. Which brings me again to the point, part of the price component goes to the Remote Desktop License to Microsoft!

There were a couple of pre-configured images, when I tested it there was no option to create one’s own image.

 

Then the size to use to stream application, in reality this is a Remote Desktop Services farm provisioned on demand.

 

 

 

Now, this was a little bit confusing, there’s the Stack and there’s the Fleet. The way I understand it:

  • Stack is the set of application(s)
  • Fleet is the actual instance number to service the requests.

The Fleet has to be provisioned in order to connect to it, it took about 20 minutes to get it ready.

Once running, I assigned a user (roberto)

With a session expiration of 30 minutes

 

The user created gets a URL to connect into:

 

Once authenticated this is how it looks. The published applications shown:

I created a Hello Word file and saved it to the X: session folder

 

The files saved in the Session Folder, are only kept as long as the Fleet is running, I stopped the Fleet and goodbye files.

Ok, I pasted it

I ran Firefox and and Notepad++ at the same time, there’s not full access to the Desktop, but there was access to the file Explorer, and the session is completely lost if the Fleet is stopped, even if the file was saved.

The Good

  • Fast provisioning
  • Quickly accessible from anywhere
  • Users are already familiar with this scenario, seamless for them

What could be better or much better

  • Active Directory Integration. Why would I need to manage a new set of users? Much better to extend my AD, and assign the users from it.
  • Provide Persistent Storage for the user sessions, again if AD is in place, permission would be easy, mapping My Folder to S3, why not.
  • Documentation, is not thaaat bad, but could be improved

 

That is it.