Windows 10 – First thoughts

I have been using Windows 10 enterprise tech preview for a few days now – and here are my initial thoughts

  • The new eval centre from where the eval is downloaded is odd. Apart from having to sign in multiple times, the download progress is not shown anywhere
  • A fresh install (which I opted for) is lightning fast
  • Skipping the “sign into your Microsoft account” still isn’t clear. You need to click on “create an account” then “use existing account”. Considering its meant to be the “enterprise” version, not wanting to sign in to a personal cloud account isn’t going to be an uncommon request
  • No option to skip the annoying “welcome” animation manually – but it is in group policy (and was with win8) – still, just be nice if it was available on non-policed machines
  • Option to boot to start menu or start screen is bleedingly obvious – hurrah!
  • Look and feel is still quite win-8-ish….
  • Still no option to include source files in the install. While I understand that doing so reduces the footprint, one of the nice things in win 7/2008r2 was that you didn’t have go searching for source media. Sure, the make the small footprint the default, but give us enterprise admins a setup option (/copylocalsource ?) to copy the local source, so we don’t need to perform steps in our SCCM builds
  • No media centre – at least for the moment – I hope MS realises that enterprise users like to use stuff like media centre while travelling – even if its a paid option, preventing it completely from being run like in 8/8.1 is a silly decision – and one that will hopefully be reversed
  • Client hyper-V – sure, nothing earth shatteringly different on the client side – but its just very nice to have it
  • The “multiple desktops” has potential – just might take a while to get used to it
  • The qtr screen snap can be useful on some occasions on large monitors, but not so much on laptops
  • Direct Access to a 2012 R2 DA server works with no modifications (yay)

All in all – its off to a good start. Its obviously early on in the dev cycle, lets hope that the rattling’s about win 10 being “enterprise focused” are true.

One thing I did initially leave off this list is “why oh why is there an x86 version”… surely its time to kill off x86 by now ? I understand there are still some applications which will not run on an x64 windows platform, but announcing the end of x86 Windows OS’ will, in some cases, help speed the transition of some applications – and for those that are no longer supported or have ludicrously long dev cycles, Win 7 and Win 8.1 offer supported x86 options for some time to come.


“Currently downloading…” call me whacky, but a % downloaded, current speed etc. might be handy here.

Windows 10 and SCCM

An announcement over at

3 things of note:

Windows 10 will be delivered in a way that allows for more choice and flexibility for businesses

Oh shit – here comes a product which is going to limit choice and flexibility and force me down a specific path for something I previously could make a choice about. (Sales speak hasn’t made me bitter and cynical)

  • The next version of System Center Configuration Manager will deliver full support for client deployment, upgrade, and management of Windows 10 and associated updates.

  • System Center 2012 R2 Configuration Manager or SP1 – we will provide an update to support Windows 10 deployment, upgrade and management with existing ConfigMgr features.

Some clarity on what the difference between “full support” and “support” would be good…. this could be anything between “2012 R2 will still do everything with Win 10” to “by support, we meant that if you applied 3 sccm patches in a specific order, that require 2 windows hotfixes to be uninstalled while chugging a beer, singing the national anthem and potting the 8 ball in the corner pocket on one leg, then yes, you can view inventory information only in 2012 r2”

Its a given that some version of SCCM will be able to deploy windows 10, but I question the value of posting such vague information. The implication is we will miss out on something if a client doesn’t go to SCCM 201? – which may well be fair enough.

as such we have decided not to ship a Configuration Manager preview at this time, and will do so in H1 CY15.

This is kind of useful-ish…. we now have a, relatively large, window of when we can expect to start testing windows 10 deployment with sccm.

Windows 10 announced

features etc. have been consistently leaked, so none are a surprise, the main quandary is – what was wrong with calling it Windows 9?

I was/am still keen for this, no matter what the name is. I was one of “those” who placed windows 8.1 in the “its a good OS under the covers – but I don’t like metro” bucket….. there were also some other fairly major issues, such as not effectively being able to manage marketplace apps with any enterprise tool – let alone SCCM and the lack of being able to set “boot to desktop” via group policy.

Keen to get my hands on Windows 10 – and even keener to get my hands on whatever version of SCCM will support Windows 10.