Tag Archives: microsoft

What to do if SkyDrive disappears from Windows 8.1 Explorer?

Here is the scenario. You are working away in Windows 8.1 and want to save a document to SkyDrive. You look for the SkyDrive link in Windows Explorer but it is not there.

image

Don’t panic; your documents are most likely fine and you can get to them in the web browser via http://skydrive.live.com

Still, that is inconvenient. How can you restore the Explorer link, other than by rebooting and hoping it reappears?

The solution is to open a command prompt (press Start button and type command) and then type:

%systemdrive%\windows\system32\skydrive.exe

and press Enter. You don’t need to run the command prompt with administrator rights.

All going well, SkyDrive will reappear:

image

What if it doesn’t? Now you have to check the logs or event viewer and look for specific errors. But the simple technique described first has always worked for me.

Microsoft proves resilience with bumper quarter, but is not yet a devices and services business

Microsoft delivered record revenue of $18.53 billion in the quarter ended September 30th 2013 – which might come as a surprise if you have been focusing on the companies failings in tablets and smartphones versus Apple and Android, the steep decline in PC sales, and its small market share in search versus Google, but less so if you have been watching the advance of products like Office 365, Windows Azure, SQL Server and Windows Server, all of which have been making good progress.

In its report, the company says the Windows OEM revenue declined 7% (reflecting PC malaise) but Surface revenue grew to $400 million. Search advertising revenue grew 47% reflecting some degree of success for Bing.

SQL Server “grew double digits”, as did “Lync, SharePoint and Exchange.”

Commercial cloud revenue grew 103%, though bear in mind that Microsoft is not telling us the absolute figures; you can easily grow fast if you start from a small number.

Microsoft has changed the way it segments its revenue, making it difficult to track, especially with large sums of money ($1.6 billion) reported as “Commercial Other”. Here is how the new segments look:

Quarter ending September 30th 2013 vs quarter ending September 30th 2012, $millions

Segment Revenue Change Profit Change
Devices and Consumer Licensing 4343 -335 3925 -178
Devices and Consumer Hardware 1485 +401 206 -242
Devices and Consumer Other 1635 +235 352 -10
Commercial Licensing 9594 +645 8801 +618
Commercial Other 1603 +355 275 +170

Now, how to make sense of this? The segment changes are detailed here (Word document). In summary:

Devices and Consumer Licensing: non-volume and non-subscription licensing of Windows, Office, Windows Phone, and “ related patent licensing; and certain other patent licensing revenue” – all those Android royalties?

Devices and Consumer Hardware: the Xbox 360, Xbox Live subscriptions, Surface, and Microsoft PC accessories.

Devices and Consumer Other: Resale, including Windows Store, Xbox Live transactions (other than subscriptions), Windows Phone Marketplace; search advertising; display advertising; Office 365 Home Premium subscriptions; Microsoft Studios (games), retail stores.

Commercial Licensing: server products, including Windows Server, Microsoft SQL Server, Visual Studio, System Center, and Windows Embedded; volume licensing of Windows, Office, Exchange, SharePoint, and Lync; Microsoft Dynamics business solutions, excluding Dynamics CRM Online; Skype.

Commercial Other: Enterprise Services, including support and consulting; Office 365 (excluding Office 365 Home Premium), other Microsoft Office online offerings, and Dynamics CRM Online; Windows Azure.

From this you can see that despite 103% growth, Azure and Office 365 remain relatively small, many times exceeded by the on-premise software licensing which is mainly in “Commercial Licensing”. However Microsoft is reporting a contribution to profits from this segment, though with smaller margins than from software licensing.

Simple addition also tells us that consumer revenue ($7,463 million) is less than business revenue ($11,197 million).

Overall it is obvious that Microsoft is not yet a “devices and services” company even if it has set that as its goal. Most of its revenue comes from traditional software licensing. Can it ever make that transition without shrinking in the process? A good question, and despite excellent figures, one that will ensure Microsoft’s future remains the subject of intense debate.

First thoughts on Surface 2

After a day or two with Surface 2 and the Touch 2 keyboard, a few thoughts.

image

First, I am typing this on my desktop PC. I would have used the Surface 2, as I like to match the tool to the review, but no Live Writer on Surface (my favoured blog authoring tool) and no, Word is not as good for this.

That neatly demonstrates the app issue on Windows RT; but despite that I expect to use Surface 2 frequently in the coming months. It is an excellent tablet, with its chief advantages over the older Surface being performance and Windows 8.1, which includes Outlook.

Performance on Surface 2 is around 4 times faster for graphics – see previous post – and more than twice as fast in general.

The touch keyboard, now with backlighting, is also much improved.

I know I am in a minority here, but to me the Windows RT concept makes good sense. A locked-down version of Windows that is almost legacy-free, though it is still Windows and capable of throwing up mystifying dialogs and hiding settings in strange places.

It seems to me that if there is any hope for the Windows 8 app ecosystem, then it will be driven by tablets like this one, and Nokia’s new Lumia 2520 which also runs Windows RT. Desktop users are mostly ignoring the app platform. There are a few signs of life, like the new Facebook app, and things like Xbox Music are now decent. MediaMonkey, which I like for its Flac support, runs nicely on Surface 2.

Isn’t an iPad Air better? In some ways for sure. Usability, performance, size and weight, and rich app availability are all in the iPad’s favour, and price is similar. The reason you might get a Surface though is for Office, USB 3.0, HDMI out, SD card, and the clever keyboard cover. I also like having more than one app to view, whether that is Word and Excel on the desktop, or Word and Caculator, or the split view that works in the new app world.

I’ve hit a few snags with Surface 2. Sound is less good than on Surface RT, tending to be thin and reedy, unless you use headphones or external speakers. The Touch 2 keyboard sometimes stops responding, which I hope is a driver issue (perhaps the update downloaded this morning will fix it).

I also suspect that build quality on Surface 2 falls short of Surface RT. It is still “Vapor Mg” but I already have a slight dent in the bezel on mine whereas on my old RT it is still perfect and I wonder if it is thinner.

The extra price for the 64GB vs 32GB SSD is absurd. Why not make them all 64GB and increase the price by a fraction?

Is Microsoft serious about selling Surface 2? There does not seem to be much stock around, and it is not yet listed on Amazon.co.uk, although it has been on sale since yesterday.

Those that do discover it will like it, provided they understand the difference between Windows RT and Windows x86, something which – bizarrely – Microsoft still seems keen to disguise.

FutureMark graphics benchmark: Surface RT vs Surface 2

We know that the new Surface 2 (Nvidia Tegra 4) is faster than the old Surface RT (Tegra 3) but by how much?

I came across the FutureMark 3D Benchmark for Windows RT in the Windows Store and tried it on both.

I could see this was going to be a wipeout from the off. The first test saw a frame rate of 12.9 FPS on RT versus 59.9 on Surface 2. Surface RT first:

image

Then Surface 2:

image

Surface 2 reported “Maxed out” on the scores. However, on the next test, Ice Storm Extreme, I got a result.

Surface RT: 2065

image

Surface 2: 8577

image

3D Mark RT says my score is “low for this device” on Surface RT, but “a great score for this device” on Surface 2. Maybe the impact of Windows RT 8.1?

Bottom line: on these tests Surface 2 is around 4 times faster. No wonder it feels snappier to use.

Review: Surface Touch Cover 2

Windows tablets present a design challenge because they include desktop applications which are designed for keyboard and mouse, rather than touch – not least Microsoft Office, which for some of us accounts for a significant proportion of the time spent using the device. So far there has been consensus therefore that Windows tablets need some easy way of using a keyboard and mouse or trackpad. How to achieve this without losing the benefits of a tablet  is not easy. Bluetooth is one solution, but means three devices rather than one in your bag. Screens that twist over to form tablets are another, but the devices tend to be heavy and the twisting action inconvenient. Detachable keyboard/trackpads are the favoured solution, but leave you the problem of a loose keyboard to look after once you have detached it. If it stays always attached, perhaps you should have bought a laptop.

Microsoft’s Surface tablet has the most elegant solution I have seen. When it was launched a year ago, it included two optional keyboard covers. The Type cover is a thin keyboard with real clacky keys.  The touch keyboard is almost flat, though the keys are slightly raised. You can detach them, but they fold back behind the device, automatically disabling the keys, at which point they are unobtrusive.

Many people liked the idea of the touch keyboard, but found typing frustrating with more errors than they normally make. For this reason, the Type keyboard is more popular among Surface users. It is possible that more Touch keyboards were sold, since they are slightly cheaper and more often bundled with the device, but in actual use I see more Type keyboards.

That is a shame, because the Touch keyboard is design-wise a better solution. It adds very little bulk to the Surface, and when folded back under the device for tablet use, it feels perfectly natural, whereas the Type keyboard feels odd because of the keys that are then on the underside.

When Microsoft announced the Touch Cover 2, it said that by adding more sensors (14 times as many apparently) and more intelligence to the cover and its drivers, it had improved the typing accuracy. As a Surface user I was excited to try the Touch Cover 2 and see if it lives up to these claims. If it does, I will happily ditch the Type cover.

image

The Touch Cover 2 is the same price as before, £99 in the UK or $120 in the US. It is compatible with every Surface, including the original Surface RT. It is also fractionally thinner, 2.5mm as opposed to 3mm. Third, it is now backlit, which makes a big difference on those odd occasions when you are typing in dim light, such as on an aircraft when the cabin lights are dim.

Looking at old and new side by side though, you would be forgiven for thinking not much has changed – the new one is the lower of the two, and note that my original is a US layout and the new one UK:

image

Here are a few more points of detail:

  • The new keyboard has function key labelling F1-F12. As is now common, the default is the non-Fn meaning, and you have to press Fn first to get the function key. The old keyboard also has an Fn key, but you have to work out which top key to press. The right Alt key is now labelled Alt Gr.
  • The purpose of two of the special keys has changed. The new keyboard no longer has volume keys, though it does have a volume mute. In their place are two keys controlling the brightness of the backlight.
  • The design of the trackpad has changed slightly. On the old touch cover, the left and right “buttons” are on the edge of the keyboard outside the etched area that represents the trackpad. On the new cover, these buttons are within the etched area, which means that the trackpad seems slightly bigger, but in reality is not.
  • The underside of the touch cover used to have a fabric finish. On Touch Cover 2 it is now smooth plastic. This is one detail where I prefer the older cover, though maybe it helps to get it that 0.5mm thinner.

The following picture shows the backs of the old and new keyboard covers side by side, with the new one on the left:

image

 

Touch cover 2 in use

Now for what really matters. How is the Touch Cover 2 in use?

My first thought was to try a speed test. I went along to this online test and tried it several times with the old touch cover, then with the new one. The results favoured the new cover, perhaps by around 20%, though how you evaluate it depends on the weighting you give to errors versus speed.

Then I sat down to write this review. This is where my opinion of the new Touch Cover began to swing in its favour. I find real-world typing on the Touch Cover 2 substantially more pleasant than with the earlier version. Measuring words per minute does not fully represent the improved experience. Of course this is a personal thing and your experience may vary.

The backlighting is low key (ha!) but improves usability. The way this works is that the white lettering on the keys is illuminated so it stands out more.

image

Note that if you think it is not working, you probably just need to increase the brightness using the special keys.

Is it as good as a real keyboard, or even a Type Cover? I doubt it ever will be, especially if you are someone who does not look at the keyboard while you type. The problem is that the slight etching round the keys makes it harder for your fingers to know where they are, though typing with audible key clicks helps.

Another factor is that if you are not at a desk, the lightness and thinness of the touch cover counts against it, since it flexes slightly on your lap.

That said, with practice you can get good speed and accuracy. As a cover, it is so much more elegant than the Type Cover that overall I might just prefer it, even though I still rate the Type Cover slightly better for typing.

One caveat though: I used the Touch Cover 2 with both Surface RT and Surface Pro, and had an annoying problem. If I stay typing in one app everything is fine, but if I switch apps than sometimes the keyboard stops responding. Oddly, opening Device Manager and pressing the up and down arrows a few times seems to fix it. Perhaps my Touch Cover 2 is faulty, but I suspect a driver issue, which means hope for a fix soon. I will be trying it soon with a Surface 2 and will be interested to see if the problem remains.

The keyboard also seems to mark easily. I have only had it for a day, but can already see slight fading of the black finish on the keys I type most often.

Mobility always involves compromise. If you want the very best keyboard for typing, it won’t be a touch cover. In fact, for best productivity I prefer a high quality Bluetooth or USB keyboard to either of the Type or Touch covers.

That does not detract from what Microsoft’s engineers have achieved with the Touch Cover 2. Flip it back, and you have a tablet; flip it forward, and you protect your screen; place it on a desk and you have a productive typing machine.

Glitch aside, I recommend the Touch Cover 2 as a good option with a new Surface and a worthwhile upgrade from the first Touch cover.

Visual Studio 2013 is released. What’s new?

Microsoft released Visual Studio 2013 yesterday:

VS 2013 can be installed side by side with previous versions of Visual Studio or, if you have a VS 2013 pre-release, it can be installed straight over  top of the pre-release.

I installed over the top of the pre-release and I’m happy to say that this worked without incident. This is how it should be.

image

Oddly, the launch of Visual Studio 2013 is not until November 13th, proving that in Microsoft’s world products can “launch” before, at or after general release.

So what’s new in Visual Studio 2013? Tracking Visual Studio is difficult, because many important features show up as updates and add-ons. After all, at heart Visual Studio is just a shell or platform in which development sit. The Visual Studio LightSwitch HTML client, for example, which made LightSwitch into a strong tool for rapid application development of mobile web apps, appeared as part of Visual Studio 2012 Update 2. Now in Visual Studio 2013 we have LightSwitch support for Cloud Business Apps, though the new project type is shown under Office/SharePoint rather than under LightSwitch:

image

A Cloud Business App is an add-on for SharePoint typically running on Office 365. In the new model SharePoint apps do not really run on SharePoint, but are web apps that integrate with SharePoint. This is great in an Office 365 context, since you can write a web app that is accessible through the Office 365 site and which is aware of the logged-on user; in other words, it uses Azure Active Directory automatically. There’s more on the subject here.

What else is new? Here are some highlights:

  • Better ISO C/C++ compliance in Visual C++
  • Upgraded F# with language tweaks and improved performance
  • .NET Framework 4.5.1 with minor enhancements
  • Support for new Windows 8.1 controls and APIs in Windows Store apps – these are extensive.
  • “Just my code” debugging for C++ and JavaScript, and Edit and Continue for 64-bit .NET apps
  • Graphics diagnostics for apps running remotely
  • Sign into Visual Studio with a Microsoft account. Microsoft pulls developers further into its cloud platform.
  • Windows Azure Mobile Services – build a back end for an app running on Windows, Windows Phone, iOS, Android or web

Does that amount to much? Compared to the changes between Visual Studio 2010 and 2012, no. That is a good thing, since what we have is a refinement of what was already a capable tool, rather than something which gives developers a headache learning new ways to work.

7 types of Windows 8 users and non-users

When I was in Seattle earlier this month I visited the Microsoft Store in Bellevue. I nearly bought a Nokia Lumia 1020, but also observed an enthusiastic salesperson showing off Surface 2 (a pre-launch demo unit) to an older customer. She watched patiently while he showed how it handled pictures, SkyDrive, Office, Email, Facebook and more. At the end she said. “I don’t need any of that. Show me your cheapest laptop.”

image

Yes, it’s tough for Microsoft. The incident got me thinking about computer users today and whether or not they are in the market for Windows 8 (or the forthcoming Windows 8.1).

Here is a light-hearted at some categories of users. And yes, I think I have met all of them. For those that are saying no, what would change their minds?

1. The Apple fan.

Switched to Mac from Windows XP around 2007. Has Mac, iPhone, iPad. So much easier, no anti-virus nags, boots quicker, less annoying, always works smoothly. Occasionally runs a Windows app on Parallels but nothing non-nuclear would persuade them to switch back.

Buying Windows 8? No.

2. The Enterprise admin.

In latter stages of migration from Windows XP to Windows 7. Still a few XP machines running awkward apps or run by awkward people. Last holdouts should be gone by year end. Job done, won’t even think about another migration for 3-5 years. Next focus is on BYOD (Bring your own device); will be mostly iPhones and iPads with the occasional Android or Windows 8 tablet.

Buying Windows 8? Mostly no.

3. The older Windows user

Son thinks a Mac would be better, but Windows works fine, is well understood, and does all that is needed. No desire to upgrade but when PC conks out will look for the most familiar looking machine at a good price. Would prefer Windows 7 but may be forced into Windows 8 if those are the only machines on offer.

Buying Windows 8? Maybe reluctantly.

4. The PC guy

This is the guy who understands PCs back to front. Never saw the point of Macs, overpriced, fewer apps, and little different in functionality. First thing to do with a new PC is either spend 3 hours removing all the crapware, or reinstall Windows from scratch. The Windows 8 user interface took some adjustment at first but fine with it now, likes the slightly better performance, and even uses a few Metro apps on the Surface Pro tablet.

Buying Windows 8? Yes, best Windows yet.

5. The tablet family

Used to update the family PC every few years, but mum got an iPad, son got an Android tablet, then dad went Android too, and now they spend so much time doing email, games, web browsing, YouTube, Facebook and BBC iPlayer on the tablets that the PC gets little use. It’s still handy for household accounts but it won’t be replaced unless it breaks.

Buying Windows 8? Not soon, and maybe not ever.

6. The tried it once never again person

It was embarrassing. Used Windows for years, then a friend brought over a Windows 8 laptop. Clicked on desktop, but with no Start button how do you run anything? Clicked around, right-clicked, pressed ESC, pressed Ctrl-Alt-Del, but nothing doing. Friend was laughing. Now the sight of Windows 8 evokes a chill shudder. Never, just never.

Buying Windows 8? No way.

7. The “Make it like 7” person

Windows 8? No problem, it’s just like 7 really. Installed Start8, got the Start menu back, set it to boot to desktop, set file associations for PDF and images to desktop apps, and never sees the Metro environment.

Buying Windows 8? Kind-of, but will never run a Metro app.

Usability: Microsoft’s big weakness

The iPhone, or maybe the iPod, was the beginning of the era of usability. Make something nice to use, reasoned Apple, and users will come flocking.

After the iPhone came the iPad; and then Android which while lacking the polish of iOS, mostly has the same characteristics of appliance rather than computer in its user interface.

What about Microsoft? It has learned to some extent. Windows Phone is a user-friendly operating system. The touch interface in Windows 8, although a shock to existing Windows users, shows obvious effort towards usability and sometimes succeeds. Navigating the weather app, for example, is a pleasure.

There are times though when Microsoft seems to have learned nothing. Take the new SkyDrive integration in Windows 8.1 for example. It is foundational in Microsoft’s effort to wrest Windows into being a cloud-centric operating system, where you could lose your device, buy a new one, log in, and find all your stuff. I’ve posted about its progress here.

But then you are on a train, say, with a poor internet connection, and you double-click a file in SkyDrive that has not been downloaded to your PC. This is the dialog you see (at least, it is the one I just saw):

image

There is so much wrong with this dialog that I don’t know where to start. But I will have a go.

First, I doubt the error is really unexpected. If my internet connection is poor, problems downloading stuff from SkyDrive are expected, not unexpected. You would think that the client could figure out, “It looks like I have a poor connection to SkyDrive” and inform the user accordingly.

Second, the error number. The dialog invites me to search for help using this number; however to do so I would have to copy it manually as it is unselectable. The number of course is in hexadecimal, so there is a high chance of copying an O instead of a zero as the difference is not obvious other than to programmers. Nor is it clear where I should search. Should I bang the number into Bing and hope for the best? Such searches can be fruitful, but they can also go badly wrong when you hit sites that tell you to download their utility to clean your registry, or some such nonsense.

Third, there is space for a human-understandable description of the error, but it is says “No error description available”. Lazy programming somewhere. Maybe in a code base the size of Windows it is too much to expect helpful messages for every error but this is not something users should normally see.

Fourth, there are three choices: Try Again, Skip and Cancel. Bearing in mind that I double-clicked only one document, what is the difference between Skip and Cancel?

Fifth, there is a More details button but it is disabled. Why, if no more details are available, does this More details button appear at all? Though I’d suggest that Error 0x80040A41 is a great candidate for “More details” rather than being something non-technical users are expected to make sense of.

What should happen? First, SkyDrive and/or its client should work better. This is a critical feature; but users are complaining (yes, I found this by searching for the error code) and it seems that problems persist in Windows 8.1 RTM. Microsoft has been working on file sync for decades, yet upstarts like Dropbox work more smoothly.

Second, when bad things happen, I am all in favour of plain English. I don’t see any reason ever to confront users with error numbers in hex. Put it in a technical details option by all means. In this particular case, why not something like, “Windows is having problems downloading from SkyDrive. You may have a poor internet connection; please try again later, and if the problem persists, contact support.”

Getting this right is not easy; but for as long as ordinary users see this kind of dialog in day to day use of Windows, the flight to iPad and Android will continue.

Update: the error fixed itself when I found a better connection

Getting up and running with Workplace Join

A key part of Microsoft’s strategy for supporting tablets and smartphones in the enterprise is Workplace Join, which lets devices register with Active Directory:

When you join your personal device to your workplace, it becomes a known device and will provide seamless second factor authentication and single-sign-on to workplace resources and applications. When a device is Workplace-Joined, attributes of the device can be retrieved from the directory to drive conditional access for the purposes of authorizing issuance of security tokens for applications.

Devices currently supported are Windows 8.1 (RT or x86) and Apple iOS, with Android in preparation. It is a kind of lite version of domain join, enabling single sign-on but not group policy (centralised control of device settings). In order to control device settings, you can use ActiveSync (limited but includes password requirements and remote wipe) or device management through the cloud-based InTune.

I set myself the task of implementing Workplace Join on my test network, mainly using the guide here. It was somewhat arduous. Here are a few points to note.

Workplace Join is also called Device Registration and is a feature of Active Directory in Windows Server 2012 R2. It depends on Active Directory Federation Services (ADFS).

I wasted some time juggling with certificates and Service Principal Names (SPNs). On my test network I have Active Directory, Certificate Server and ADFS on the same virtual machine, which is not recommended. Here are some things to note.

You need a Server Authentication certificate which includes a Subject Name and two Subject Alternative Names, one of which is enterpriseregistration.yourdomain.com In order to get this out of Certificate Server I ended up copying and modifying a template to allow this additional data to be entered when the certificate is requested. I did not need to purchase any certificates; it all works as long as the Enterprise CA (Certification Authority) certificate is trusted by the device.

IIS will need this certificate as the default web site must accept secure connections to enterpriseregistration.yourdomain.com.

I got into difficulty when configuring ADFS. Initially I used the same name for the Federation Service Name as the computer name. This in turn caused a conflict with the registration of an SPN for the ADFS service account, probably because I have too much installed on one box. SPNs are used by Kerberos for secure communications and each SPN must be unique. The solution was to remove ADFS and re-install, using a different Federation Service Name. Then I modified DNS so that all three names – computer name, Federation Service Name, and enterpriseregistration – resolve to the same box.

I have not published my ADFS to the internet so mine is only an intranet solution for now.

Once all this was resolved I was able to run the PowerShell scripts to enable the Device Registration Service, and to check Enable device authentication in ADFS:

image

Of course my first efforts at actually using Workplace Join on a device (I used Surface RT and Surface Pro) failed with a generic error.

image

Confirm you are using the correct sign-in info, and that your workplace uses this feature. Also, the connection to your workplace might not be working right now. Please wait and try again.

The first thing to check is that your device can access the device registration service over HTTPs. Open a browser and go to this URL:

https://enterpriseregistration.[yourdomain.com]/EnrollmentServer/Contract?api-version=1.0

If this does not resolve, or returns a certificate error, you need to fix this before registration will work. Possible reasons:

  • Your device does not trust the certificate
  • IIS has the wrong certificate
  • A necessary service is not running on the server (check ADFS and the Device Registration Service as well as IIS)
  • The device cannot access the Certificate Revocation List for your domain

There is also an event log for workplace join, buried in the Applications and Services section, even on Windows RT.

Once fixed, I was successful and saw my devices show up in Active Directory under Registered Devices.

image

Sunspider JavaScript Benchmark on 4 models of Microsoft Surface

Today I got my first sight of Microsoft’s new models of Surface, its Windows tablet, on display at the Microsoft Store in Bellevue.

image 

I ran the Sunspider JavaScript benchmark on the new models, and then on the old ones for comparison.

  • Surface RT 1.0: 922ms
  • Surface 2.0 (RT): 397ms
  • Surface Pro: 127ms
  • Surface Pro 2.: 114ms

No surprises; but what this confirms is that Surface 2.0 RT, which has an NVIDIA Tegra 4 chipset, is substantially faster than the earlier Tegra 3 model; whereas Surface Pro which has an updated Intel Core i5 processor is only a little faster on this particular test.

Microsoft is attempting to continue selling Surface RT alongside Surface 2.0 RT, at $349 vs $449 for the 32GB model. However the new one is a better buy and I imagine the price of the earlier model will fall further, given that Microsoft appears still to have substantial stocks.