By now, you are familiar with the Windows 10 conversation that reached a new peak a week ago Tuesday with a public-facing webinar. Shouts out included product features and function, such as the Start button, and a conversation about Windows as a Service (think in some ways how Google Chromebooks works). I’d implore you to read this PC Magazine article for your Win10 speeds and feeds fix.
What I want to do with this blog is provide more context.
First, about the Tuesday 9AM Pacific webinar on January 20th. Simply stated, it was oversubscribed and the delivery mechanism was overwhelmed. That’s because the topic is hot, and it was broadcast from Building 92 in Redmond (where the Microsoft Store and Museum are located). So the “choppiness” of the webinar stream might be attributed to the available bandwidth in that building. In the future, I’d recommend that this type of webinar event be hosted at the Microsoft Conference Center in Building 33, where I know that the bandwidth is sufficient.
An interesting factoid about the Win10 webinar is that it was primarily marketed to consumers and not partners or commercial accounts. In speaking with my sources at Microsoft, that decision to have a customer-facing webinar is a hope and desire to have a “win” with Win10, which I guess you’d call a Win-Win. I predict future webinars will be marketed to MSPs, partners and commercial accounts (e.g. Enterprise), as the product further develops.
I can provide context concerning the HaloLens conversation at the end of the Webinar. This was essentially inserted as “eye candy” and a bit of a reward for those staying until the end of the presentation. This product, found here, is not central to the Win10 experience.
My own opinion? I roll with what was thrown at me. After watching the Win10 webinar and downloading the latest preview update to my test machine (more information here), my existing Windows 8.1 laptop crashed (see the pic). Must be jealous.
In the next Win10 blog, I interview Onuora Amobi, the founder of the Windows 10 Update site. Standby.
