What is Extended Hotfix Support?

What is Extended Hotfix Support?
As I mentioned in an earlier posting, during the Extended Support phase we no longer provide non-security hotfixes without enrollment in the Extended Hotfix Support program.  Simply put, the Extended Hotfix Support program provides the ability to request non-security hotfixes for products that are in the Extended Support phase.

Remember, Extended Hotfix Support (EHS) only provides the opportunity to request a non-security hotfix for a new bug discovered during the Extended Support phase.  It has no impact on a customer’s ability to request support, security updates, or other non-security hotfixes created during the Mainstream Support phase.

To enroll in EHS, customers must already have Premier Support.  In addition, enrollment in the program must occur within the first 90 days of the product entering the Extended Support phase.  If the customer misses this deadline, there may not be an opportunity to enroll in EHS again Microsoft MCITP Certification.

The only exception to the 90 day enrollment rule is for customers with Software Assurance (SA).  Customers with Software Assurance on select products are eligible for a benefit which includes the program fee for Extended Hotfix Support and allows enrollment at any time.  Essentially, this means that the SA customers only need to sign the appropriate paperwork and pay the per hotfix fee.  The products that are included in this benefit are: Microsoft Office Professional, Microsoft Windows Client, Microsoft Exchange Server, Microsoft MCTS Training Operations Manager (MOM), Microsoft SQL Server, Microsoft Systems Management Server (SMS), and Microsoft Windows Server.

Pricing for Extended Hotfix Support consists of an annual program fee, plus an additional fee for each non-security hotfix they receive.  Non-security hotfixes produced during the Extended Support phase will not be made available to other customers in the program, without enrollment in EHS or the per hotfix fee.  This is to ensure that all customers are treated equal and are being charged the same fees for each hotfix.

Whew…  That’s a lot of stuff to cover.  I hope it makes the program easier to understand, though.  🙂

End of Support for Visual Basic 6.0

End of Support for Visual Basic 6.0
I wanted to take a moment to remind everyone that public support for Visual Basic 6 came to an end on April 8th, 2008.  If you already subscribe to our quarterly newsletter you probably already know the details behind this.  If not, here is a quick explanation of what’s happening on the second Tuesday of April…

Visual Basic 6 (VB6) can basically be divided into three main deliverables…

* Visual Basic 6 IDE — the Integrated Development Environment (IDE) used to develop VB 6.0 applications
* Visual Basic 6 Runtime — the base libraries and execution engine used to run VB 6.0 applications
* Visual Basic 6 Runtime Extended Files — select ActiveX control OCX files, libraries, and tools shipping with the IDE media and as an online release

Support for the VB6 IDE came to an end on April 8th.  This means that Microsoft MCTS Training will no longer provide any additional assisted support, security updates or development assistance on the IDE or the VB6 language.  However, online information (such as MSDN articles and the Knowledge Base) will remain online for at least the next 12 months.

Support for the VB6 Runtime will continue.  Generally, the VB6 Runtime is shipped as a component of the operating system and will be supported with the product that it shipped with.  For example, since the VB6 Runtime shipped as a component of Windows XP, the runtime will continue to be supported for the life of Windows XP.  The VB6 Runtime has shipped on all of our OS releases and will continue to be supported with all those OSes.

Since the VB6 Runtime is supported with the OS, customers will be able to open support cases and request assistance if the VB6 Runtime is not operating as expected or is causing problems with their application.  In addition, we will continue to provide security updates for the VB6 runtime.  We will not provide any development assistance or support for the IDE, however.

The VB6 Runtime Extended Files are generally installed by the IDE or from Microsoft MCITP Certification and are redistributed by developers with their application.  This redistribution is often required to ensure the functionality of the application.  The product team will be releasing a new, supported set of these tools online in the coming weeks.  To obtain support, customers will need to ensure they are running the supported versions of these files.

More information on how the Visual Basic 6 runtime will be supported can be found in the MSDN Visual Basic 6 Resource Center.  On this site, the product team has detailed a number of the support scenarios and files, especially as they pertain to Windows Vista and Windows Server 2008.   It’s a great resource if you have any outstanding questions.