Rockford Lhotka's Blog

Home | Lhotka.net | CSLA .NET

 Thursday, April 03, 2014
« “Mobile” devices | Main | Visual Studio Live Chicago 2014 »

Microsoft has substantially improved the story around side loading of Windows 8 WinRT (Windows Runtime or Windows Store) apps for the enterprise and business environments.

I’ve blogged pretty extensively in the past about the costs of the two steps necessary to side load apps:

  1. Unlock your devices for side loading
  2. Actually side load (install) your various business apps

Microsoft has now radically changed the cost of step 1. This blog post from Microsoft contains the following statement:

Enterprise Sideloading– In May, we will grant Enterprise Sideloading rights to organizations in certain Volume License programs, regardless of what product they purchase, at no additional cost. Other customers who want to deploy custom line-of-business Windows 8.1 apps can purchase Enterprise Sideloading rights for an unlimited number of devices through Volume Licensing at approximately $100. For additional information on sideloading licensing, review the Windows Volume Licensing Guide.

Basically what this means is the following (as I understand it):

For developers/testers things are unchanged – you still use a free dev unlock key to install apps for development and testing.

For organizations with an Enterprise Agreement (EA) you’ll be able to get a side loading unlock key that you can use on all your Windows 8 Pro and Windows 8 Enterprise devices, regardless of whether they are domain joined or not. As before, you can also get ‘companion device’ keys to unlock Windows RT devices if you have a Windows 8 Enterprise device too.

For smaller organizations that don’t have an EA you might have (or can get) one of a number of ‘Open’ or ‘Select’ license agreements with Microsoft. Once you have one of these you can buy a side loading key for around $100 that will unlock any number of Windows 8 Pro or Windows 8 Enterprise devices.

When compared to the old model of buying keys for $30/device this is a major change in the right direction. For a maximum of around $100 virtually every organization (small to huge) can get a side loading unlock key for all their devices.

Now this still doesn’t address the need to actually install your apps onto your devices.

Microsoft offers InTune, which is a full MDM (mobile device management) product. If you find the value proposition of an MDM compelling then InTune is probably the right answer for you – though there’s a per device/per month cost (ranging from $6/device/month to $11/device/month) so you don’t get MDM for free of course.

Screenshot (5)I’ve been coordinating an open source project called OrgPortal that you can use to (relatively) easily create an app store for your organization.

There’s another open source project called CompanyStore that is very similar.

Alternately you can have your users manually run a PowerShell to install and update each app manually over time.

I think Microsoft has taken a substantial step in the right direction with the changes to the cost and availability of side loading keys. Couple this with the increasing maturity of projects like OrgPortal and CompanyStore and I think we’re getting to the point where WinRT is something to consider for business app development.

Thursday, April 03, 2014 3:49:27 PM (Central Standard Time, UTC-06:00)
Some time ago I had to tell my own boss that it was hard to envision advocating for WinRT...

Having had a chance to learn about the universal applications at Build (covering one additional minor area - Windows Phone - our current roadmap wouldn't have covered), learning the positive news from your blog post regarding side-loading pricing as well as the potential private store code under development, and finally having a chance to talk to some of the fine people at Xamarin at their booth, I'm really starting to feel that the WinRT + Xamarin (iOS+Android) combination may actually turn out to be the most compelling one.

I was really interested to hear from one of Xamarin's folk that he uses MVVM across all three UIs, enabling the sharing of the view model code as well (perhaps requiring compiler directives at times). I recall asking in a prior post about whether iOS/Android uses MVVM and had the impression not only was MVC the traditional route but the most viable route. If I remember right Xamarin has certain connectors to make databinding more effective, maybe helping to enable this. (I still haven't even installed Xamarin but I believe that's what I recall).

So I find myself thinking that the unique code would in general terms really boil down to *part* of the UI now, correctly or incorrectly.

Anyway, kind of an exciting week so far. While I was disappointed (but not surprised) to hear anything about Silverlight, I had a generally good feeling about the route Microsoft is headed.
chris
Friday, April 04, 2014 9:03:23 AM (Central Standard Time, UTC-06:00)
Thanks for keeping this issue current. But I am still not sure if the changes apply to where it really matters "Windows RT"
So with the purchased keys, is it possible to deploy apps to Windows RT devices such as Surface at all? (even if it requires a relatively complicated process)
If not then this only seems to address problem for MS trying to attract users on desktop platforms who have the luxury to give RT apps a miss by using alternative technologies such as full .Net and WPF.
Syd
Monday, April 07, 2014 2:16:58 PM (Central Standard Time, UTC-06:00)
I agree with Syd's thoughts. I don't see how this addresses the problematic cost improvements for WinRT - specifically devices like the Surface/Surface 2 and Nokia 2520. Both are ARM based and run only WinRT. Prior to these announcements the cost was $30 per device (in packs of 1000 no less, drop that requirement and we are pretty far along). So, unless I am wrong we haven't moved much in the area of Win RT.
ed
Monday, April 07, 2014 11:00:50 PM (Central Standard Time, UTC-06:00)
I have a couple thoughts on the Windows RT question (as opposed to WinRT, which is the runtime for all flavors of Windows 8).

Windows RT only runs on ARM-based devices, and this edition of Windows 8 is the most restrictive because you can only install WinRT apps (the only Win32 apps allowed are from Microsoft).

If you have a Windows 8 Enterprise computer you can unlock your Windows RT device via a 'companion key'. In practice most companies with an EA will be running Win8 Enterprise and so will have unlock keys for Windows RT.

For smaller companies this is problematic, I agree. But I also think the total inability to unlock the 'Windows 8' (home) edition is a big problem. Virtually every normal consumer buying a computer from a retailer is likely to get 'Windows 8' (as opposed to 'Windows 8 Pro') and will have _no_ way to unlock their computer for side-loading. No more working from home in the evenings...


My other primary thought here though, is that ARM and thus Windows RT has done its job and is no irrelevant. I think the goal was to scare Intel into making low-heat, long-battery SOCs. And in that regard the goal has been met, because you can now get ATOM-based Intel devices with comparable battery life to ARM devices.

All the major manufacturers seem to agree with this view - the only place you can still get ARM-based Win8 devices is from Microsoft and Nokia (basically Microsoft).

Personally I can't see where I'd buy an ARM-based device at this point, when there are ATOM-based devices that are at least as good, and _those_ devices can run Windows 8 Pro.
Wednesday, April 09, 2014 11:32:20 PM (Central Standard Time, UTC-06:00)
Nice work on OrgPortal. I wonder if the new brokered apps means that you can get rid of the windows desktop service for installing the apps?
Monday, April 21, 2014 4:49:58 PM (Central Standard Time, UTC-06:00)
I think Microsoft needs to take another look at this subject as even thought they have relaxed some of the policies it is still onerous. For e.g., if an enterprise is creating apps for its dealer ecosystem and makes this available on the app store then according to the current policy it requires that each dealer must procure its own side loading license to install these apps. When you have a large contingent of dealers both large and small this makes it challenging. AFAIK, neither iOS or Android have this policy so Microsoft needs to review the current policy,
Ravi Tolani
Comments are closed.
On this page....
Search
Archives
Feed your aggregator (RSS 2.0)
July, 2014 (3)
June, 2014 (4)
May, 2014 (2)
April, 2014 (6)
March, 2014 (4)
February, 2014 (4)
January, 2014 (2)
December, 2013 (3)
October, 2013 (3)
August, 2013 (5)
July, 2013 (2)
May, 2013 (3)
April, 2013 (2)
March, 2013 (3)
February, 2013 (7)
January, 2013 (4)
December, 2012 (3)
November, 2012 (3)
October, 2012 (7)
September, 2012 (1)
August, 2012 (4)
July, 2012 (3)
June, 2012 (5)
May, 2012 (4)
April, 2012 (6)
March, 2012 (10)
February, 2012 (2)
January, 2012 (2)
December, 2011 (4)
November, 2011 (6)
October, 2011 (14)
September, 2011 (5)
August, 2011 (3)
June, 2011 (2)
May, 2011 (1)
April, 2011 (3)
March, 2011 (6)
February, 2011 (3)
January, 2011 (6)
December, 2010 (3)
November, 2010 (8)
October, 2010 (6)
September, 2010 (6)
August, 2010 (7)
July, 2010 (8)
June, 2010 (6)
May, 2010 (8)
April, 2010 (13)
March, 2010 (7)
February, 2010 (5)
January, 2010 (9)
December, 2009 (6)
November, 2009 (8)
October, 2009 (11)
September, 2009 (5)
August, 2009 (5)
July, 2009 (10)
June, 2009 (5)
May, 2009 (7)
April, 2009 (7)
March, 2009 (11)
February, 2009 (6)
January, 2009 (9)
December, 2008 (5)
November, 2008 (4)
October, 2008 (7)
September, 2008 (8)
August, 2008 (11)
July, 2008 (11)
June, 2008 (10)
May, 2008 (6)
April, 2008 (8)
March, 2008 (9)
February, 2008 (6)
January, 2008 (6)
December, 2007 (6)
November, 2007 (9)
October, 2007 (7)
September, 2007 (5)
August, 2007 (8)
July, 2007 (6)
June, 2007 (8)
May, 2007 (7)
April, 2007 (9)
March, 2007 (8)
February, 2007 (5)
January, 2007 (9)
December, 2006 (4)
November, 2006 (3)
October, 2006 (4)
September, 2006 (9)
August, 2006 (4)
July, 2006 (9)
June, 2006 (4)
May, 2006 (10)
April, 2006 (4)
March, 2006 (11)
February, 2006 (3)
January, 2006 (13)
December, 2005 (6)
November, 2005 (7)
October, 2005 (4)
September, 2005 (9)
August, 2005 (6)
July, 2005 (7)
June, 2005 (5)
May, 2005 (4)
April, 2005 (7)
March, 2005 (16)
February, 2005 (17)
January, 2005 (17)
December, 2004 (13)
November, 2004 (7)
October, 2004 (14)
September, 2004 (11)
August, 2004 (7)
July, 2004 (3)
June, 2004 (6)
May, 2004 (3)
April, 2004 (2)
March, 2004 (1)
February, 2004 (5)
Categories
About

Powered by: newtelligence dasBlog 2.0.7226.0

Disclaimer
The opinions expressed herein are my own personal opinions and do not represent my employer's view in any way.

© Copyright 2014, Marimer LLC

Send mail to the author(s) E-mail



Sign In