Windows Support Lifecycle

Microsoft Support Lifecycle policy provides consistent and predictable guidelines for product support availability at the time of product release. Microsoft will offer a minimum of 10 years support (5 years of Mainstream support and 5 years of Extended) at the supported service pack level for Business and Developer products

Product Name General Availability Mainstream Retirement (1) Extended Retirement (2) Service Pack Level Service Pack Availability Service Pack Retired (3)(4)
Windows 2000 Family 3/31/2000 6/30/2005 7/13/2010 SP3 8/1/2002 6/30/2005
Windows 2000 Family SP4 6/26/2003 7/13/2010
Windows XP 12/31/2001 4/14/2009 4/8/2014 RTM 12/31/2001 9/17/2004
Windows XP SP1 8/30/2002 10/10/2006
Windows XP SP2 9/17/2004 7/13/2010
Windows XP SP3 4/21/2008 Review Note (4)
Windows XP Professional 64-bit Edition 4/24/2005 4/14/2009 4/8/2014 RTM 4/24/2005 4/14/2009
Windows XP Professional 64-bit Edition SP2 3/13/2007 Review Note (4)
Windows Vista 1/25/2007 4/10/2012 4/11/2017 RTM 1/25/2007 4/13/2010
Windows Vista SP1 2/4/2008 7/12/2011
Windows Vista SP2 5/26/2009 Review Note (4)
Windows 7 10/22/2009 1/13/2015 1/14/2020 RTM 10/22/2009 4/9/2013
Windows 7 SP1 2/22/2011 Review Note (4)
Windows 8 10/26/2012 1/9/2018 1/10/2023 RTM 10/26/2012 1/12/2016
Windows 8.1 11/13/2013 8.1 11/13/2013 Review Note (4)
Surface Pro 5/10/2013 7/10/2017 n/a RTM 5/10/2013 n/a
Surface Pro 2 1/20/2014 4/10/2018 n/a RTM 1/20/2014 n/a
Windows Server 2003 5/28/2003 7/13/2010 7/14/2015 RTM 5/28/2003 4/10/2007
Windows Server 2003 SP1 3/30/2005 4/14/2009
Windows Server 2003 SP2 3/13/2007 Review Note (4)
Windows Server 2003 R2 3/5/2006 RTM 3/5/2006 4/14/2009
Windows Server 2003 R2 SP2 3/13/2007 Review Note (4)
Windows Server 2008 5/6/2008 1/13/2015 1/14/2020 SP1 5/6/2008 7/12/2011
Windows Server 2008 SP2 5/26/2009 Review Note (4)
Windows Server 2008 R2 10/22/2009 RTM 10/22/2009 4/9/2013
Windows Server 2008 R2 SP1 2/22/2011 Review Note (4)
Windows Server 2012 10/30/2012 1/9/2018 1/10/2023 RTM 10/30/2012 Review Note (4)
Windows Server 2012 R2 11/25/2013 RTM 11/25/2013 Review Note (4)
Windows XP Embedded 1/30/2002 1/11/2011 1/12/2016 RTM 1/30/2002 10/22/2004
Windows XP Embedded SP1 10/22/2002 4/10/2007
Windows XP Embedded SP2 1/18/2005 1/11/2011
Windows XP Embedded SP3 11/14/2008 Review Note (4)
Windows Embedded Standard 12/14/2008 1/14/2014 1/8/2019 RTM 12/14/2008 Review Note (4)
Windows Embedded Standard 7 7/29/2010 10/13/2015 10/13/2020 RTM 7/29/2010 4/9/2013
Windows Embedded Standard 7 SP1 2/28/2011 Review Note (4)
Windows Embedded for Point of Service 6/6/2005 4/12/2011 4/12/2016 RTM 6/6/2005 10/12/2010
Windows Embedded for Point of Service SP3 10/7/2008 Review Note (4)
Windows Embedded POSReady 2009 3/10/2009 4/8/2014 4/9/2019 RTM 3/10/2009 Review Note (4)
Windows Embedded POSReady 7 9/10/2011 10/11/2016 10/12/2021 RTM 9/10/2011 Review Note (4)
Windows CE 4.2 6/1/2003 7/8/2008 7/9/2013 RTM 6/1/2003 Review Note (4)
Windows CE 5.0 8/31/2004 10/13/2009 10/14/2014 RTM 8/31/2004 Review Note (4)
Windows Embedded CE 6.0 11/30/2006 4/9/2013 4/10/2018 RTM 11/30/2006 Review Note (4)
Windows Embedded Compact 7 3/15/2011 4/12/2016 4/13/2021 RTM 3/15/2011 Review Note (4)
Windows Mobile 6.0 12/5/2007 1/8/2013 n/a n/a n/a n/a
Windows Mobile 6.1 7/1/2008 n/a n/a n/a
Windows Mobile 6.5 9/11/2009 n/a n/a n/a
Windows Phone 7.8 2/9/2013 9/9/2014 n/a n/a n/a n/a
Windows Phone 8 12/14/2012 1/12/2016 n/a n/a n/a n/a
Software Update Services 1.0 8/26/2005 n/a 7/10/2007 SP1 8/26/2005 7/10/2007
Windows Server Update Services 2.0 3/22/2005 n/a 4/30/2009 RTM 3/22/2005 ENDED
Windows Server Update Services 2.0 SP1 5/31/2006 4/30/2009
Windows Server Update Services 3.0 4/30/2007 n/a n/a RTM 4/30/2007 4/17/2009
Windows Server Update Services 3.0 SP1 4/17/2008 10/12/2010
Windows Server Update Services 3.0 SP2 8/25/2009 Review Note (3)
Windows Server Update Services for Windows Server 2012 10/30/2012 1/9/2018 1/10/2023 RTM 10/30/2012 Review Note (3)
(1)  Mainstream support will end 5 years after the general availability date or 2 years after the next version of the product is released, whichever period is longer.
(2)  Extended support will end five years after mainstream support ends.
(3)  Support ends either 12 months after the next service pack releases or at the end of the product’s support lifecycle, whichever comes first.
(4)  Support ends either 24 months after the next service pack releases or at the end of the product’s support lifecycle, whichever comes first.
Posted in Windows Server | Leave a comment

HP Network Configuration Utility – Shows Degraded

This could happen when 2 difference model of network card are configure with Nic Teaming function


From the Nic Teaming properties, it shown that the status is Degraded (Rx Path). Even though it is Nic Teaming, both NICs transfer at the same time but only the one Nic will receive data. The other NIC is  not able to receive any packets because of the heartbeat is fail


After Disabling Enable receive path validation and saving settings, Nic teaming shows healthy with a green status.


Posted in HP | Leave a comment

Backup Exec 2010 and 2012 new Service Packs Generally Available

Great news

Symantec just announces the general availability of the two Service Packs for BE2010 and BE2012 that bring support for Windows Server 2012 (via an agent), vSphere 5.1 and a host of quality improvements.

You can download the service pack from the weblink as below or you can wait for the availability via LiveUpdate in a few weeks time.

Posted in Backup Exec, Symantec | Leave a comment

HostId: The length of the value must fall within the range “0” (Inclusive) – “32” (Inclusive).

According to Symantec, there is no solution yet to this method which is related to IPv6.

However my server is configure with IPv4, I was confuse what is that IPv6 issue.

Firstly type ipconfig in command prompt to check what is the IPv6 address and which network adapter is it attach to.

I found the IPv6 is attach with tunnel pseudo interface

In backup exec server, you can also verify the IPv6 address details in “Backup and restore” tab’s server details

After verify all the things, disable the network adapter of tunnel pseudo interface and try to configure the backup policy.

Things should be working fine



Posted in Backup Exec, Symantec | Leave a comment

Backup Exec new release Announcement from Director of Marketing, Backup Exec

Symantec announce the expected general release of Backup Exec 2010 R3 SP3 and Backup Exec 2012 SP2 shall be this coming July.

The focus of this release will include support for the following:

Backup Exec 2012

  • Protection of Windows Server 2012 servers using the Agent for Windows. This includes support for:
    • Microsoft data deduplication-enabled volumes (backs up and restores data in non-deduplicated data format)
    • New ReFS (Resilient File System)
    • Windows Recovery Volume (WinRE)
    • New Hyper-V version
    • Updated Failover Clustering (CSV)
    • Native 4K (Advanced Format) drives
    • Online restore of computer and system components
  • Updated protection of SQL to include:
    • SQL 2012 SP1
    • SQL 2008 R2 SP2
  • Protection of Exchange 2013 (Non-GRT only)
  • Support for Exchange 2010 SP3
  • Protection of SharePoint Server 2013 (Non-GRT only)
  • Support for VMware vSphere 5.1
    • ESX 5.1 and vCenter 5.1
Posted in Uncategorized | 2 Comments

SIP Trunking

SIP Trunking

A SIP trunk is an IP connection that establishes a SIP communications link between organization and an Internet telephony service provider (ITSP) beyond firewall. Typically, a SIP trunk is used to connect organization’s central site to an ITSP. In some cases, SIP trunking may opt use to connect your branch site to an ITSP.

SIP Trunk vs Direct SIP

Areas SIP Trunk Direct SIP
  • SIP trunks are connections between two separate SIP networks, the Microsoft Lync Server 2010 enterprise and the ITSP
  •  Direct SIP are SIP connections that do not cross the local network boundary (that is, they connect to a PSTN gateway or PBX within your internal network)
External Entity Connection
  • The External edge component (could be a SBC, router or gateway) of the ITSP gateway
  • IP PBX or PSTN Gateway
Connection Method
  • Multiprotocol Label Switching (MPLS)
  • A private connection with no other traffic—for example, a leased fiber-optic connection or T1 line
  • The Internet
  • IP-PBX  (Direct SIP deployment Option)
  • PSTN Gateway (PSTN Gateway deployment Option)

Implement SIP Trunking

To implement SIP trunking, connection must route through Mediation Server, which acts as a proxy for communications sessions between Lync Server clients and the service provider and transcodes media, when necessary.

Each Mediation Server has an internal network interface and an external network interface. The internal interface connects to the Front End Servers. The external interface is commonly called the gateway interface because it has traditionally been used to connect the Mediation Server to a public switched telephone network (PSTN) gateway or an IP-PBX. To implement a SIP trunk, you connect the external interface of the Mediation Server to the external edge component of the ITSP.

Centralized vs. Distributed SIP Trunking

Centralized SIP trunking routes all VoIP traffic, including branch site traffic, through central site. The centralized deployment model is simple, cost-effective, and generally the recommended approach for implementing SIP trunks with Lync Server 2010.

Distributed SIP trunking is a deployment model in which implement a local SIP trunk at one or more branch sites. VoIP traffic is then routed from the branch site directly to a service provider without going through the central site.

Distributed SIP trunking is required only in the following cases:

  • The branch site requires survivable phone connectivity (for example, if the WAN goes down).
  • Resiliency is required between two central sites.
  • The branch site and central site are in different countries/regions.

Supported SIP Trunking Connection Types

Lync Server supports the following connection types for SIP trunking:

  • Multiprotocol Label Switching (MPLS) is a private network that directs and carries data from one network node to the next. The bandwidth in an MPLS network is shared with other subscribers, and each data packet is assigned a label to distinguish one subscriber’s data from another’s. This connection type does not require VPN. A potential drawback is that excessive IP traffic can interfere with VoIP operation unless VoIP traffic is given priority.
  • A private connection with no other traffic—for example, a leased fiber-optic connection or T1 line—is typically the most reliable and secures connection type. This connection type provides the highest call-carrying capacity, but it is typically the most expensive. VPN is not required. Private connections are appropriate for organizations with high call volumes or stringent security and availability requirements.
  • The Internet is the least expensive connection type, but it is also the least reliable. Internet connection is the only Lync Server SIP trunking connection type that requires VPN.
Posted in Lync | 1 Comment

Lync Server 2010 Voice Topology

Just come out with this diagram, kindly comment so I can enhance it

If you need the visio file, kindly drop a message and email address so that I can send out.

Lync Server 2010 Voice Topology

Posted in Lync | 6 Comments