Article ID: 816916 - Last Review: November 5, 2007 - Revision: 6.4 Description of the new naming schema for Office software update packages For a Microsoft ISA Server version of this article,
see
822623
(http://support.microsoft.com/kb/822623/
)
. For a Microsoft Systems Management Server version of
this article, see
823419
(http://support.microsoft.com/kb/823419/
)
. For a Microsoft SQL Server version of this article,
see
822499
(http://support.microsoft.com/kb/822499/
)
. For a Microsoft Windows version of this article, see
816915
(http://support.microsoft.com/kb/816915/
)
. For a Microsoft Exchange version of this article, see
817903
(http://support.microsoft.com/kb/817903/
)
. For a Microsoft Visual Studio .NET version of this
article, see
822464
(http://support.microsoft.com/kb/822464/
)
. On This PageSUMMARYMicrosoft has adopted a standardized naming schema for all
software update packages for Microsoft Office that are created and distributed
by Microsoft. The new naming schema goes into effect for all software update
packages in May, 2003. For additional information about the standard terminology that Microsoft is adopting to describe software updates, click the following article number to view the article in the Microsoft Knowledge Base: 824684
(http://support.microsoft.com/kb/824684/
)
Description of the standard terminology that is used to describe Microsoft software updates
Microsoft has adopted the new naming schema for Office software update packages for the following reasons:
MORE INFORMATIONNew Schema for Naming Office Software Update PackagesOffice software update packages are named by using the following schema:ProductName-KBArticleNumber-Option-Language.exe
OfficeXP-KB123456-Client-ENU.exe Office2000-KB123456-FullFile-DEU.exe Visio2002-KB123456-Client-JPN.exe The following list provides information about each attribute in the new naming schema:
APPLIES TO
| Article Translations
|
Back to the top
