It sounds like Windows Intune is just about ready for prime time.
Microsoft’s new technology which it describes as “an end-to-end Microsoft solution that brings together Windows cloud services for PC management and endpoint protection” is set for commercial availability on March 23 – right smack dab in the middle of Microsoft Management Summit (MMS) 2011. A website dedicated to Intune is now up where folks can learn more about it before MMS and presumably test and purchase it once it ships.
You have to hand it to Quest Software CEO Doug Garn — the guy is a great sport.
Recently, my colleagues Brian Madden, Gabe Knuth and Bridget Botelho recorded a video for SearchVirtualDesktop.com. The purpose of the video was to preview what’s ahead for desktop virtualization in 2011, and the conversation touched on several different topics.
When Quest made its way into the convo, Brian (always willing to share his thoughts on … well … anything) made a crack about Quest’s logo being somewhat outdated (check in at about the 12:20 mark): “Can I say this directly to you, Quest? Can you change your logo and update it so it’s not a 1992 logo?”
Not one to take those kinds of remarks lying down, Garn and the folks at Quest put together a video of their own especially for Brian. Instead of ruining it for you, click play below to see Garn’s response. You have to respect folks that don’t take themselves too seriously these days.
It sounds like Microsoft is finally close to announcing RTM for both service packs soon, with MSDN availability set for Feb. 16, with a Feb. 22 release date for the Web.
ORIGINAL POST 2/02/2011
320 days. That’s how long it’s been since news first broke of the initial service packs for Windows 7 and Windows Server 2008 R2. Yet while general availability was expected for early Q1, January has come and gone with SP1 still officially under wraps.
So what’s going on? Back on January 14, a Russian Microsoft blog posted that both service packs had been shipped to OEMs, leading many to believe that a release to MSDN was imminent. Not long after the news spread like wildfire, the same Russian site posted an update stating that SP1 was in fact not released to OEMs, and that the original post included some “inaccuracies”. (Amusingly, the retraction is the only part of the entry that’s in English.)
ZDNet UK just posted some screenshots from the SCVMM 2012 demos last week, for anyone interested in a few visuals of the interface in action.
ORIGINAL POST 1/25/2011
Those who enjoyed Microsoft’s cloud push last year are really going to like 2011. Many of the technologies that have been discussed over the past year are slowly beginning to see the light of day, starting with next version of System Center Virtual Machine Manager (SCVMM).
During a live meeting this week, Microsoft product manager Kenon Owens demoed the yet-to-be released SCVMM 2012 (previously dubbed “v.Next” before TechEd Europe in November). Microsoft is positioning SCVMM as a key component for organizations looking to private clouds, and Owens broke down some of the ways the software can be used to control infrastructures and services in a cloud-based environment.
Is 5:00 p.m. on a Friday too late for a little Hyper-V-centric news? Nah.
Microsoft’s Michael Kleef just posted a short update on his personal TechNet blog about a new discovery involving Hyper-V R2 SP1. Apparently, the latest version of Hyper-V will now support up to 12 virtual machines per logical processor, up from the previous max of eight, but only for Windows 7 SP1 guests.
In other words, admins can host up to 12 guest operating systems per logical processor on a Hyper-V host as long as each of those guest OSes are running Windows 7 SP1. Otherwise, the ratio of VMs/logical processor remains at 8:1.
My colleague Bridget Botelho just posted a much more detailed follow-up to this story with insight from IT professionals and analysis of Microsoft’s past investments in the tablet market. Definitely worth a read.
ORIGINAL POST 12/22/2010
It was always going to come to this, wasn’t it? Reports have surfaced this week that Microsoft is set to change the Windows OS as you know it in an effort to make a bigger splash in the mobile device market.
Bloomberg (followed by several other news outlets) reported that Microsoft has begun work on a new version of Windows designed specifically for tablets and smartphones. Though plans for the OS are officially confidential, leaks have flooded the Internet with news that Microsoft will provide more details during next month’s Consumer Electronics Show (CES).
The Bloomberg report states that the “new Windows” will be built on architecture from ARM Holdings PLC in addition to the usual x86 chip technology from Intel and Advanced Micro Devices (AMD). The ARM design is a better fit for smaller mobile devices because the chips consume less power. In fact, many devices – including the iPad – already use it.
Microsoft released to manufacturing the final build for Windows Small Business Server 2011 Standard this week, the latest version of the company’s server OS for small- and medium-sized organizations. The Standard edition (formerly codenamed Windows SBS “7”) is only half the SBS story, however, as Microsoft is also set to put out an Essentials edition for the smallest of the small businesses as well.
Previously dubbed “Aurora”, SBS 2011 Essentials hasn’t RTM’d yet, though it’s expected in the first half of next year, with a new beta potentially dropping in January.
So what’s the difference between the two?
“Dynamic Memory for Hyper-V is Microsoft’s answer to VMware’s memory overcommit technology for ESX. “
“Dynamic Memory is in fact not the same as memory overcommit, and now that you mention it, VMware’s stuff is still way better.”
If you’ve paid any attention at all to server virtualization news this past year, you’ve likely heard some variation of those two statements. Ad nauseam. Over and over again.
The funny thing is, Dynamic Memory isn’t even officially out yet; even though the release candidate is now available, SP1 for R2 won’t officially ship until early next year. But ever since news of the feature first broke back in the spring, IT folks have debated the degree to which it will put Microsoft virtualization at equal footing with VMware.
Reaction to news this week that Microsoft has put the kibosh on Internet Explorer virtualization was … well … let’s say colorful. The issue is centered on Spoon.net, a company/website that (by way of virtualization) allows developers to run desktop applications over the Internet, thus providing an easy way to build and test apps on browsers like Firefox and IE. Well, until now that is.
As my colleague Bridget Botelho reported, Microsoft sent a letter to the folks at Spoon requesting that IE be removed from its list of virtualized apps. Essentially, Microsoft does not support the virtualization of IE because it’s a part of the Windows operating system. By providing virtualized IE on its site, the company claimed that Spoon was violating Microsoft’s “intellectual property rights”.
Spoon complied and removed IE from its list of options (though somewhat begrudgingly). Users and developers, however, haven’t gone so quietly. “There was an explosion of rage on Twitter from developers,” Spoon CEO Kenji Obata said in the story cited above. “I have never seen such a virulent response to something before. I have learned curse words in multiple languages.”
He wasn’t joking. Here ‘s an expanded list of some of the more telling (and entertaining) quotes from those in the Twitter-verse – at least the ones we could print:
It sounds like Microsoft has found another mountain to climb, and this one makes “Kilimanjaro” look … well, slightly closer to sea level.
The company announced the next version of SQL Server at PASS Summit 2010 this week, codenamed “Denali”. The moniker follows Yukon (SQL Server 2005) and Kilimanjaro (SQL Server 2008) as the latest Microsoft database server to be named after mountainous terrain. (Fun fact: Kilimanjaro stands at an elevation of 19,341 feet, while Denali – aka Mount McKinley – clocks in at just over 20,300 feet. Wouldn’t it have been funny if the next version of SQL Server was actually “shorter” than the last?)