• [1:58] What has improved in System Center 2012 Configuration Manager to support new devices running Windows 8?
• [3:38] Can Configuration Manager manage non-Windows based devices as well?
• [4:25] How does System Center 2012 better support the mobile user?

Download the Windows 8 Enterprise Evaluation today and test your applications, hardware and deployment strategies with Windows 8.

Resources:

• Windows 8 Enterprise
• Windows 8 Licensing
• The Springboard Series Blog
• Windows 8 Resources for IT Pros on Springboard
• Resources for Developers to Build Windows 8 Apps
• Windows 8 resources for partners on Microsoft Partner Network

Service Bus Notification Hubs are an intrinsic feature of Windows Azure Service Bus and are different from other push notification services in four key areas:

• Complete client registration management. Your backend application does not need to worry at all about device-ids or channels or other particulars of push notifications and doesn't need to cooperate in management. It doesn't even have to be a web app that's publicly accessible.  
• Platform independence. Service Bus Notification Hubs allow cross-platform push notifications so that iOS Alerts and Windows Live Tiles can be targeted with a single event message. 
• Broadcast and tag-based Multicast - Service Bus Notification Hubs are optimized around automatic notification broadcast to many thousand devices with low latency. One message in, thousands of notifications out.
• Mass customization - Notification Hub notification templates allow for customization of notification delivery for each individual registration, allowing each instance of a client App to choose how it wants to receive events.

In this preview, Notification Hubs are able to push notifications to Windows Store apps and iOS apps from .NET back-ends. Support for Android and Windows Phone, along with additional back-end technologies (including Windows Azure Mobile Services) will be added soon.

And here are all the key links

• Feature guide (Windows Store Apps) - http://go.microsoft.com/fwlink/?LinkID=275828
• Feature guide (iOS) -  http://go.microsoft.com/fwlink/?LinkId=275829
• Fundamentals - http://go.microsoft.com/fwlink/?LinkId=277072
• Tutorial (Windows Store Apps) - http://go.microsoft.com/fwlink/?LinkId=277073
• Tutorial (iOS) - http://go.microsoft.com/fwlink/?LinkId=277074

 SDKs:

• Windows 8 Managed Client Library - http://go.microsoft.com/fwlink/?LinkID=277160
• iOS Client Library - http://go.microsoft.com/fwlink/?LinkID=277161
• Preview client NuGet - http://nuget.org/packages/ServiceBus.Preview

Like Cloud Cover on Facebook!

Follow @CloudCoverShow
Follow @cloudnick
Follow @ntotten
Follow @ElioDamaggio

Fast forward to the present day, and Iguazu has become a real thing, thanks to an enormously engaged team who built a brand new service from scratch and plugged it into the Service Bus infrastructure. Today we're taking the wraps off the Service Bus Notification Hubs preview.

Service Bus Notification Hubs are an intrinsic feature of Windows Azure Service Bus and are different from other push notification services in four key areas:

• Complete client registration management. Your backend application does not need to worry at all about device-ids or channels or other particulars of push notifications and doesn't need to cooperate in management. It doesn't even have to be a web app that's publicly accessible.  
• Platform independence. Service Bus Notification Hubs allow cross-platform push notifications so that iOS Alerts and Windows Live Tiles can be targeted with a single event message. 
• Broadcast and tag-based Multicast - Service Bus Notification Hubs are optimized around automatic notification broadcast to many thousand devices with low latency. One message in, thousands of notifications out.
• Mass customization - Notification Hub notification templates allow for customization of notification delivery for each individual registration, allowing each instance of a client App to choose how it wants to receive events.

In this preview, Notification Hubs are able to push notifications to Windows Store apps and iOS apps from .NET back-ends. Support for Android and Windows Phone, along with additional back-end technologies (including Windows Azure Mobile Services) will be added soon.

If you can't wait to see teh codez check out the docs and bits below or watch my walkthrough.

And here are all the key links (if they're not yet active/current they will soon be)....

• Feature guide (Windows Store Apps) - http://go.microsoft.com/fwlink/?LinkID=275828
• Feature guide (iOS) -  http://go.microsoft.com/fwlink/?LinkId=275829
• Fundamentals - http://go.microsoft.com/fwlink/?LinkId=277072
• Tutorial (Windows Store Apps) - http://go.microsoft.com/fwlink/?LinkId=277073
• Tutorial (iOS) - http://go.microsoft.com/fwlink/?LinkId=277074

 SDKs:

• Windows 8 Managed Client Library - http://go.microsoft.com/fwlink/?LinkID=277160
• iOS Client Library - http://go.microsoft.com/fwlink/?LinkID=277161
• Preview client NuGet - http://nuget.org/packages/ServiceBus.Preview

 Your App Adventure Starts here. Build your Windows Store and Windows Phone Apps and games here.

Try Windows Azure for free with no cost or obligations, and use any OS, language, database or tool. FREE Download

To try mobile services for free, sign up for the Free Trial and www.windowsazure.com - you'll get 10 mobile services for free.

For more information on setting up APNS with Mobile Services, check out our tutorials at:

• Get started with push notifications in Mobile Services
• Push notifications to users by using Mobile Services

Follow @joshtwist

In this interview that starts at [05:20] , we cover:

• [07:30] Demo - Adding iOS, Android, Windows 8 Applications to SCCM 2012
• [08:33] Demo - Deploying Windows 8 Application in SCCM 2012
• [10:08] Demo - Client install of Windows 8 Enterprise App via self-service app portal
• [11:43] Demo - Windows 8 management for User data and profiles in SCCM 2012

• [14:23]- Windows 8 enhancements with power management, metered connections, deployment
• [16:04]- Demo - Windows 8 deployment enhancements: bitlocker, data migration
• [18:25] - Windows to Go management using SCCM 2012 SP1

Download a copy of SCCM 2012 SP1 Beta: http://aka.ms/sccmsp1

News:

• Acquisition of StorSimple and available Windows Azure Online Backup
• Windows Surface RT available for pre-order!
• Windows 8 Launch / general available Oct 26th
• Xbox Music

Connect with the Edge Team:

Facebook – Twitter

 You get can get the toolkit—and all the source code—on github:

• https://github.com/microsoft-dpe/watoolkitios-lib
• https://github.com/microsoft-dpe/watoolkitios-samples
• https://github.com/microsoft-dpe/watoolkitios-doc

For details on how to get started, see Wade Wegner's post on Getting Started with the Windows Azure Toolkit for iOS.

Reader JenST responds to my recent analysis of "smartphone carnage", saying:

"See BT purchased Ribbit.  This could be the first move of the carriers to take control from Google, Microsoft, Apple."

JP Rangaswami, the guy at BT responsible for this acquisition, is one of my favorite bloggers, so I have followed this story with interest.  Although he doesn't talk about work on his blog, he is an extremely lucid and enjoyable thinker who understands this new world deeply.  And the news stories provide enough additional details to start forming opinions.

In short, I think JenST is right.  While it's too early to paint this as a direct assault on Google (or other carriers, for that matter), this is a really strategic acquisition.

The key thing to realize here is that BT is trying to do for carriers (and particularly, voice) what Facebook did for social networks, and what Amazon did for hosting.  This was BT's strategy prior to the Ribbit acquisition, and Ribbit was pursuing this strategy independently.  The essence of this strategy is to open up your platform, and let your developers evolve the difficult parts and edge cases organically.  Rather than trying to design a complex and monolithic platform speculatively before signing up a single developer, you define just the core pieces, and let the platform grow and adapt to real-world needs.

I respectfully disagree with Om, when he speculates that it will be *harder* for Ribbit to attract developers under the BT mantle.  When pursuing a Facebook/Amazon strategy, Ribbit had to convince developers that their network had critical mass -- a key value proposition of Facebook development is the millions of people already on the network.  With the BT partnership, Ribbit is instantly associated with a massive global network.  Now that the backing network is more than a toy (and a carrier with a real business model), Ribbit is a lot more interesting to serious developers.

Sam Dean expresses a slightly different concern, worrying that BT will squash the "openness" of Ribbit.  To be honest, I can't make heads or tails of this.  What exactly was so "open" about Ribbit in the first place?  It certainly wasn't "open source", and if all of the IP were entirely unencumbered, it's hard to imagine what the $105 million acquired.  Furthermore, the SDK currently supports only Flash, which is rather proprietary last I checked.  I am reminded of the recent controversy on FriendFeed over the promiscuous use of the word "open".  Let's just agree that Ribbit has some characteristics of "openness", just like the Facebook API and Amazon EC2/S3; and that this quasi-openness can add a lot of value to BT's walled garden just as Facebook's social graph and Amazon's physical infrastructure derive value from their controlled openness.

So ... will this move be the gasoline that lights a fire in the heretofore controlled world of telco platforms?  I don't know.  BT is clearly hoping to force the hand of other telcos and VOIP providers, just as Facebook and Amazon forced their larger competitors to follow suit.  So long as they nurture their developer community and show some measurable gains, other telcos will certainly need to pay attention.

But it seems that BT wish more to pre-empt a Google, Microsoft, or Apple move as much as disrupt their carrier competitors.  The money quote is JP saying:

"What we expect the competition to do – and we think it will much more likely be the Apples and Googles of the world – is to start positioning around a device [such as the iPhone] or an approach to connectivity [such as Google’s ad-based Web model"

Now, that is strategic thinking.  I am pleased (or am I?) that JP cannot imagine Microsoft being a player in this space.

All of the recent hype about iPhone 3G would make you think that the Smartphone market is Apple’s to win (from RIMM).  Heck, much of the coverage makes it sound as if the iPhone is the first phone to have a popular developer ecosystem.  CNET even went so far as to predict that the iPhone would replace Facebook and MySpace as the preferred social network targeted by widget vendors and advertisers!  As in the past, the popular consensus is bound to look myopic in hindsight.

In this industry, there are 4 types of players who compete and cooperate:

·         Carriers – companies like AT&T or Orange who sell you communications bandwidth for your phone.  They own spectrum, and lease that spectrum to you.  They want you to A) pay as much as possible for as long as possible, B) not cost them a lot in customer support.  Carriers have the control, since spectrum is a scarce physical resource.  This is why everyone else is interested in “network neutrality” legislation.

·         Handset makers – these are companies like Nokia who make phones and want to get a profit on the hardware sale.

·         Phone OS providers – companies like Microsoft who try to license their software to handset makers.

·         Service providers – companies like Google who make profit when people use their service from a mobile phone.

I won’t take the risk of making predictions that could come back to bite me, but it’s safe to predict that the carnage is far from over.  For the next 5 years at least, the following 5 companies will all be very relevant with significant share.  For each one, I talk a bit about the business model and strategy to help understand how things might play out:

Google

Google Android aims to be an open-source operating system for Smartphones; free to all handset makers.  Google like to say that they “do everything out in the open”, so it was fun to see them get caught being secretive.  But it’s all a bit unfair, since Google is more open than Apple, Microsoft, or RIMM – and in fact that openness may be their downfall.

You see, Android is basically a strategic hedge by Google, to ensure that nobody can tie up the mobile platform with a closed, proprietary system.  Google benefits when everyone develops using web standards and targeting Google services.  Google’s business model is to profit on the services (like search) and use that profit to subsidize the phone user experience.  This is a really strong strategy; and Google’s absolutely dominant ability to monetize their services will make them relevant on all mobile phones, regardless of how many Android units have shipped in 5 years.

Google’s weakness is that their strategy is fundamentally opposed to the strategy of the carriers.  Phone Carriers want you to keep paying your bill, and to use data plans that are more profitable.  They don’t want you calling them with an expensive support call about some 3^rd party application that they didn’t even write.  Carriers may not mind open source, but they want a controlled developer ecosystem.

Symbian (Nokia)

Symbian is the dominant smartphone platform outside of the USA.  The big news recently was that Nokia has purchased Symbian and will open-source the platform. 

Unlike Google, who makes money from the services, the handset makers get their profit from selling the hardware.  An open-source Symbian means that they don’t see a sustainable business model in licensing the handset OS.  While open-source Symbian and Android are a blow to Microsoft’s Windows Mobile strategy (at a minimum, creating some pricing pressure), open-source Symbian is also blow to Google’s Android plans.  The handset makers are wary of Google and want to keep their options open.

RIMM

RIMM owns a proprietary handset, operating system, and services.  Because they control everything except the carrier, they can offer seamless end-to-end experience.  This is why BlackBerries are so strong in the USA.  RIMM knows how to work with carriers, too.

Apple

Apple is essentially copying RIMM’s strategy, controlling a proprietary handset, operating system, and services.  Just like RIMM, they provide a seamless end-to-end experience.  Just like RIMM, they make carriers happy by providing a sexy device that makes it easier for the carrier to sell expensive contracts.

Much has been made about how “innovative” the iPhone SDK and store is, but people apparently forget that Windows Mobile, Palm, and even RIMM have had additional applications available for a long time.  The sort of applications, and the download trends, look a lot like other platforms.  When people mention that Facebook is the #3 download from the App Store, they forget that Facebook released an app (web-based) for iPhone long before the SDK was released, and it was immensely popular.  Windows Mobile recently got two Facebook apps, and installs of the Facebook app for BlackBerry still outnumber iPhone.

What Apple is doing differently is important, though.  By centrally controlling the application store, they give an improved user experience.  And more importantly, they provide a visible brand where people wanting support can call *instead* of calling the carrier.  Apple’s app store will certainly increase expense for the carriers, but less so than the more open strategies of Google or Microsoft.

Apple business model is to profit up-front on the hardware, and break even on the services.  They take a 30% cut of app store revenues and charge a subscription for mobile me, but their primary strategy is to profit on hardware.  This gives them the free cash flow up front.

Microsoft

Microsoft’s business model historically has been to make money licensing our proprietary operating system.  As a platform, we offer C++, .NET, or Silverlight, as well as AJAX.

As the entire company moves toward a software plus services strategy, our mobile strategy combines operating system with services.  This is what the Danger acquisition was about, and it is no mistake that the Live Search app is one of the most popular applications for Windows Mobile.

Search is the Lever

Common wisdom says that this is about Apple and RIMM, but I think this is actually about Google and Microsoft.  It’s true that Google hasn’t shipped a single unit yet, and Microsoft’s primary revenue stream (licensing the OS) seems threatened by open-source Symbian and Android.  And neither company sells a sexy handset to drive cash flow-positive revenue.

But both companies control search engines, and search service is far more monetizable than any of the other services.  The end-to-end experience using the WLS app on Windows Mobile is the sort of experience Google would love to have on all mobile handsets, and you can bet that they will.  Apple getting $0.30 every time someone installs the “Flash Light” application is cool, but the revenues and margins of app store and iTunes store won’t be able to compete with search.  Like iTunes and app store, the Mobile Me service is an attempt by Apple to protect their high hardware margins.

Search will be a critical component of RIMM or Apple experience anyway.  Search is a really hard market to enter, and none of the other contenders will be able to afford the infrastructure necessary.

"Why a stand-alone converter application? We chose this route because it supports both Office 2004 and Office v.X for Mac users, while providing some bonus functionality such as batch conversion... The user interface for the converter actually began life as an internal test tool (where you can imagine the batch processing comes in handy) - it was so slick it quickly became obvious that it was a great solution for the converter. You can drag and drop files onto the converter icon or application of course, but can also simply double-click .docx files to invoke it."