Windows 10 support on Hyper-V

by Shijaz Abdulla on 13.08.2015 at 10:23


Q: I want to deploy Windows 10 within Hyper-V VMs. What Hyper-V host is required?

A: From a support standpoint, Microsoft uses a consistent support policy for guest operating systems that are newer than the Host OS. Specifically, Microsoft supports a guest operating system (N) on an N-1 HOST. Thus, Windows Server 2012 R2 is supported as a guest on a Windows Server 2012 Hyper-V HOST, but it is not supported on a Windows Server 2008 R2 -SP1 Hyper-V HOST (N-2).

Here are a couple examples of supported configurations:

1. Windows 10 Client is supported as a guest on Windows Server 2012 R2 Hyper-V host.

2. Windows Server 2012 is supported as a guest on Windows Server 2008 R2 SP1 Hyper-V host.

3. Windows Server 2012 R2 is supported as a guest on Windows Server 2012 Hyper-V host.

Since there’s so much interest in Windows 10, here are further details:

Hypervisor version Windows 10 supported as guest?
Windows 8.1 Hyper-V Yes
Windows 8.0 Hyper-V No
Windows Server 2012 R2 Hyper-V Yes
Windows Server 2012 Hyper-V No


Finally, from a best practices standpoint, Microsoft recommends deploying the latest, up-to-date version of Hyper-V as host.


Q: I want to deploy Windows Server 2016 within Hyper-V VMs. What Hyper-V host is required?

A: Windows Server 2016 is still under development and thus production support isn’t available yet. However, based on our consistent support policy, you can expect Windows Server 2016 to be supported as a guest operating system on Windows Server 2012 R2 Hyper-V.

Windows Server 2003 End-of-Life

by Shijaz Abdulla on 24.05.2014 at 06:30

Who remembers Windows Server 2003?

Just in case you’re still running Windows Server 2003 – here’s a reminder – Windows Server 2003 will be “end-of-life” on July 14, 2015. Here’s a countdown timer!

Microsoft Premier Services

by Manoj Chandrasenan on 09.05.2011 at 20:55

My first post, thanks Shijaz for helping me out with setting this up. Thought where else to start than to write about the team wherein I work in Microsoft, that is the Microsoft Premier Services.

Microsoft Premier Services is a highly customizable support offering from Microsoft, encompassing a comprehensive selection of support resources to choose from, including proactive prevention resources, infrastructure support, workshops, problem resolutions, IO capability and IT process maturity assessment and roadmap.

With Premier Support, you gain a dedicated resource who is your eyes, ears and voice within Microsoft; the Technical Account Manager (TAM). Working with you, your TAM will:

  • Develop an understanding of your Business and Technology requirements and design a unique service delivery plan.
  • Proactively facilitate support services and resources to help mitigate issues in  your unique Business applications and IT Infrastructure.
  • Engage appropriate knowledge transfers and workshops by Microsoft resources to increase the skills of your IT staff on the current and upcoming technologies to help them better manage and monitor in your IT infrastructure.
  • Assess your IO maturity and help move move up the IT capability ladder.
  • Assess the IT process maturity of your organization and plan to improve your processes around ITIL and MOF.

Predominantly the focus of Microsoft Premier Services is to identify and address potential problems before they occur, thus reducing the risk of downtime and interruption to your business.  This in turn benefits you with increased system availability and uptime that keeps you end users productive and make IT a strategic asset to your business than a cost center or liability.

The result? Lower risk to your IT infrastructure, higher productivity and maximum benefits from your existing IT investments and better alignment of IT to business capabilities.

Vista RTM support has ended

by Shijaz Abdulla on 14.04.2010 at 13:35

If you or your customers are running Windows Vista RTM version (without any service pack), please note that support for it has ended yesterday, April 13, 2010.

To continue receiving support for Windows Vista, you must install Service Pack 1 or Service Pack2, which is available as a free download from the Microsoft Download Center.

Follow this link, for information on how to obtain the latest service pack.

Windows XP SP2, Windows 2000 no longer supported

by Shijaz Abdulla on 18.01.2010 at 00:15

In case you didn’t notice, Microsoft will end support for Windows 2000 (Client and Server) and Windows XP SP2 on July 13, 2010. Customers will no longer be able to call Microsoft for support or receive free security updates from Microsoft unless they move to a supported version of the operating system.


For the record, Windows 2000 was released almost 10 years ago, back in February 2000. Windows XP was released more than 8 years ago, in August 2001.


Update (18-Jan-2010): Windows XP SP3 is going into extended support till April 2014 meaning that you can get hotfixes if you enter into a (paid) Extended Hotfix Support agreement, which is not included by default in a Premier Support agreement.


This post (as with all other posts on, is provided “as is” and confers no rights.

Which Microsoft applications can I virtualize?

by Shijaz Abdulla on 24.10.2009 at 20:29

For a list of Microsoft servers and products that are tested and supported in virtualized environments, see the Microsoft KB article 957006.

Be sure to bookmark this article, as the page is regularly revised as new products are supported. As of writing this post, the page is at Revision 10.0.

The Future of Windows XP

by Shijaz Abdulla on 04.01.2009 at 07:33

January 4, 2009


After having tirelessly served the world for more than eight years, Windows XP is fast being replaced by its younger brother, Windows Vista.

Most of us are curious to know what exactly is the future of Windows XP. Most of us have seen it in retail stores, and even seen it being shipped with new computers even after the launch of Windows Vista.

So what does the future hold for Windows XP? What if you can’t run Vista, and you really must use Windows XP? How long can you use Windows XP? To get an answer to all these questions, and much more – read what Microsoft has to say: Windows XP: The facts about the future.

Exchange 2003: Support ending April 2009

by Shijaz Abdulla on 10.11.2008 at 09:35

Mainstream support for Exchange Server 2003 will end on April 14, 2009. This means that you cannot contact PSS for supporting problems on Exchange Server 2003 after this date, unless you sign up for ‘extended’ support at an additional cost.

Maybe this is a good time for organizations to seriously start thinking about upgrading to Exchange Server 2007 and make use of the new, advanced features.

For those who have made it to Exchange Server 2007 SP0, here is a shocker: Mainstream support for Exchange Server 2007 SP0 (i.e. Exchange Server 2007 with NO service pack installed) will end on January 13, 2009. Yes, that’s about two months from now.

For those who are still wary of installing SP1 on Exchange Server 2007, it’s time to take a call on the chicken-and-egg upgrade dilemma between Windows Server 2008 and Exchange Server 2007 SP1.

Some more information:

  • Windows Server 2003 and Windows Server 2003 R2 will go out of mainstream support on July 2010.
  • Windows XP will go out of mainstream support on April 14, 2009.

End of support: Exchange Server 2003

by Shijaz Abdulla on 15.04.2008 at 16:29

Microsoft will pull the plug on Exchange Server 2003 support in April 2009.

Unless another service pack is released for Exchange Server 2003 (which is unlikely), the mainstream support for the product will end on 14th April 2009.

If you’re still running Exchange Server 2003, its time to start thinking of upgrading to Exchange Server 2007. One year from today, you will not receive support from Microsoft if you face problems on your Exchange 2003 installation, unless you purchase the ‘extended support’ option, which is available till August 2014.

More information on the Microsoft Support Lifecycle website.

How to bulk edit an Active Directory attribute

by Shijaz Abdulla on 29.01.2008 at 18:08

Everybody knows that if you want to manually edit the value for an attribute in Active Directory, you ought to be using ADSIEDIT.

But what if you just realized that you have to modify a particular attribute for a large number of Active Directory users, if not all users? Would this mean opening up each user object in ADSIEDIT and modifying the required attribute?

Thankfully, there is the ADModify tool from Microsoft PSS that lets you bulk-edit Active directory. You simply set the filter on what users should be affected, and then specify the attribute that needs to be changed and the value to which it should be changed. You can even make the values to by typing the word null as the value.

A word of caution here – Bulk edits can be really, really painful if you do it wrong. You can seriously mess up your Active Directory if you’re not careful!

< Previous posts