Support for Windows Vista Service Pack 1 (SP1) ends on July 12, 2011. To continue receiving security updates for Windows, make sure you're running Windows Vista with Service Pack 2 (SP2). For more information, refer to this Microsoft web page: Support is ending for some versions of Windows
After you install this update on a computer that is running the System Center Configuration Manager 2007,
Service Pack 1 (SP1) client or the System Center Configuration Manager 2007 Service Pack 2 (SP2) client, a user state migration may fail.
For more information about how to resolve this issue, click the following article number to view the article in the Microsoft Knowledge Base:
User state migration fails on a System Center Configuration Manager 2007 Service Pack 1 client or on a System Center Configuration Manager 2007 Service Pack 2 client after you install security update 974571
Services that are required by Communications Server are not started after you install this update and then restart a computer that is running any of the following versions of Communications Server:
Live Communications Server 2005 (LCS)
Live Communications Server 2005 SP1
Office Communications Server 2007 Enterprise edition (OCS)
Office Communications Server 2007 Standard edition
Office Communications Server 2007 R2 Enterprise edition
Office Communications Server 2007 R2 Standard edition
Office Communicator 2007 Evaluation version only*
Office Communicator 2007 R2 Evaluation version only*
Office Communicator 2005
*The licensed production version of this application is not affected by this known issue. Only Office Communicator clients that are in their 180-day evaluation period are affected by this issue.
When this problem occurs, the following error events are logged in the Application logs in the Event Viewer of the affected servers:
Live Communications Server 2005
Event Type: Error
Event Source: Live Communications Server
Event Category: (1000)
Event ID: 12290
Date: Date
Time: Time
User: N/A
Computer: Computer
Description:
The evaluation period for Microsoft Office Live Communication Server 2005 has expired. Obtain the released version of this product and upgrade to the non-evaluation version by running setup.exe.
Office Communications Server 2007
Log Name: Office Communications Server
Source: OCS Server
Date: Date
Event ID: 12290
Task Category: (1000)
Level: Error
Keywords: Classic
User: N/A
Computer: Computer
Description:
The evaluation period for Microsoft Office Communications Server 2007 R2 has expired. Please upgrade from the evaluation version to the full released version of the product.
Log Name: Office Communications Server
Source: OCS Server
Date: Date
Event ID: 12299
Task Category: (1000)
Level: Error
Keywords: Classic
User: N/A
Computer: Computer
Description:
The service is shutting down due to an internal error.
Error Code: C3E93C23 (SIPPROXY_E_INVALID_INSTALLATION_DATA)
Cause: Check the previous entries in the event log for the failure reason.
Resolution:
Check the previous event log entries and resolve them. Restart the server. If the problem persists, contact Product Support Services.
When this problem occurs, the required services behave as if an expired trial version of the product is installed. This behavior affects the whole Communications Server enterprise that is hosted by the affected server or servers.
Customers who are not running OCS or LCS server are not affected by this known issue, and can safely ignore this issue.
Customers who have deployed the OCS or LCS product on a server should assess the risk that is involved to decide whether to install the security update on that server. These customers should revisit this Knowledge Base article often, because this article will be updated as soon as more information and a resolution are available.
When you deploy the Standard Edition role on a new installation of any version of Office Communications Server, activation fails if security update 974571 is installed. To resolve this problem, apply this fix, and then run the activation again.
When activation fails, the following warning event is logged in the Office Communications Server log in the Event Viewer of the affected servers.
Office Communications Server 2007 R2
Log Name: Office Communications Server
Event Type: Warning
Event Source: OCS Setup
E vent Category: (1007)
Event ID: 30502
Date: Date Time: Time User: N/A
Computer: Computer Description:
Failed to activate Office Communications Server Standard Edition Server on machine R2-SE.NWTraders.com.
Error: C3EC78D8
Description: Failed to read the Office Communications Server version information. This can happen if the computer clock is not set to correct date and time.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
This same event is also shown as a failure in the Activate Standard Edition Server log:
[0xC3EC78D8] Failed to read the Office Communications Server version information. This can happen if the computer clock is not set to correct date and time.
Issues with Windows 2000 Certificate Services and MS09-056
Smartcard certificates that are issued by a Windows 2000 CA where the userPrincipalname (UPN) of the user is empty may include an incorrectly-formatted Subject Alternate Name (SAN) that contains an additional NULL character embedded.
After MS09-056 is installed on domain controllers in the domain, those smartcards will be rejected during logon attempts. The domain controllers start rejecting their SAN after they have MS09-056 installed.
To resolve the issue, reissue the affected users' smartcards. If a Windows 2000 CA will be used to reissue the new smartcard certificates, the UPN of the affected users must be populated before reissuing the smartcards.
A fix that resolves this issue is available for download from the Microsoft Download Center. To obtain the fix, visit the following Microsoft Web page:
The fix (OCSASNFix.exe) is governed by the Microsoft Software License Agreement for Office Communications Server 2007 R2, Office Communications Server 2007, Live Communications Server 2005, Office Communicator 2007 R2, Office Communicator 2007, and Office Communicator 2005.
This fix works for both clients and servers, and it is applicable to the following roles for all versions of Office Communications Server and Live Communications Server 2005 SP1 and for evaluation versions of Office Communicator:
Standard Edition Server
Director server role
Enterprise Edition Consolidated
Enterprise Edition Distributed – Front End
Edge Server
Proxy server role
Office Communicator 2007 Evaluation version only
Office Communicator 2007 R2 Evaluation version only
Office Communicator 2005 Evaluation version only
To run the fix, type the following command at a command prompt, and then press ENTER:
ocsasnfix.exe
When you run the command on a computer that is running Office Communication Server 2007, Office Communication Server 2007 R2, or Live Communications server 2005 Service Pack 1, you receive a message that resembles the following:
Checking OCS/LCS Server installation...Fixing registry data
Checking Office Communicator 2007 Eval installation...not installed.
Checking Office Communicator 2005 Eval installation...not installed.
When you run the command on a computer that is running an evaluation version of Office Communication Server 2007, Office Communication Server 2007 R2, or Live Communications server 2005, you receive a message that resembles the following:
Checking OCS/LCS Server installation...not installed.
Checking Office Communicator 2007 Eval installation...Fixing registry data
Checking Office Communicator 2005 Eval installation...not installed.
This fix can be applied either before or after you install security update 974571. If you apply the fix after you install security update 974571, we recommend that you apply the fix before you restart the computer. If you already restarted the computer after you installed security update 974571, this fix can still be applied. However, the Office Communication Services must be started manually.
If all services start without any issues, this indicates that this fix has been applied and is working correctly.
This fix sets the OCSASNFIX DWORD value to 1 for the following registry subkey on the OCS 2007/R2 and LCS 2005-SP1 Server:
When you deploy the Standard Edition role on a new installation of any version of Office Communications Server, activation fails if security update 974571 is installed. To resolve this problem, apply the fix that is described in the "Resolution for these known issues" section, and then run the activation again.
The English (United States) version of this software update installs files that have the attributes that are listed in the following tables. The dates and times for these files are listed in Coordinated Universal Time (UTC). The dates and times for these files on your local computer are displayed in your local time and with your current daylight saving time (DST) bias. Additionally, the dates and times may change when you perform certain operations on the files.
Windows 2000 file information
For all supported editions of Microsoft Windows 2000 Service Pack 4
Collapse this tableExpand this table
File Name
Version
Date
Time
Size
msasn1.dll
5.0.2195.7334
05-Sep-2009
06:36
55,056
Windows XP and Windows Server 2003 file information
The files that apply to a specific service branch (QFE, GDR) are noted in the "Service branch" column.
GDR service branches contain only those fixes that are widely released to address widespread, critical issues. QFE service branches contain hotfixes in addition to widely released fixes.
In addition to the files that are listed in these tables, this software update also installs an associated security catalog file (KBnumber.cat) that is signed by using a Microsoft digital signature.
For all supported x86-based versions of Windows XP
Collapse this tableExpand this table
File Name
Version
Date
Time
Size
Service branch
msasn1.dll
5.1.2600.3624
04-Sep-2009
08:15
58,880
SP2GDR
msasn1.dll
5.1.2600.3624
04-Sep-2009
08:06
58,880
SP2QFE
msasn1.dll
5.1.2600.5875
04-Sep-2009
08:33
58,880
SP3GDR
msasn1.dll
5.1.2600.5875
04-Sep-2009
08:27
58,880
SP3QFE
For all supported x64-based versions of Windows Server 2003 and of Windows XP Professional x64 edition
Collapse this tableExpand this table
File Name
Version
Date
Time
Size
CPU
Service branch
msasn1.dll
5.2.3790.4584
09-Sep-2009
16:32
159,744
X64
SP2GDR
wmsasn1.dll
5.2.3790.4584
09-Sep-2009
16:32
58,880
X86
SP2GDR\wow
msasn1.dll
5.2.3790.4584
09-Sep-2009
16:29
159,744
X64
SP2QFE
wmsasn1.dll
5.2.3790.4584
09-Sep-2009
16:29
58,880
X86
SP2QFE\wow
For all supported x86-based versions of Windows Server 2003
Collapse this tableExpand this table
File Name
Version
Date
Time
Size
Service branch
msasn1.dll
5.2.3790.4584
04-Sep-2009
08:58
58,880
SP2GDR
msasn1.dll
5.2.3790.4584
04-Sep-2009
10:01
58,880
SP2QFE
For all supported IA-64-based versions of Windows Server 2003
Collapse this tableExpand this table
File Name
Version
Date
Time
Size
CPU
Service branch
msasn1.dll
5.2.3790.4584
09-Sep-2009
16:29
188,928
IA-64
SP2GDR
wmsasn1.dll
5.2.3790.4584
09-Sep-2009
16:29
58,880
X86
SP2GDR\wow
msasn1.dll
5.2.3790.4584
09-Sep-2009
16:27
188,928
IA-64
SP2QFE
wmsasn1.dll
5.2.3790.4584
09-Sep-2009
16:27
58,880
X86
SP2QFE\wow
Windows Vista and Windows Server 2008 file information
The files that apply to a specific product, milestone (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table:
Collapse this tableExpand this table
Version
Product
Milestone
Service branch
6.0.6000.16xxx
Windows Vista
RTM
GDR
6.0.6000.20xxx
Windows Vista
RTM
LDR
6.0.6001.18xxx
Windows Vista SP1 and Windows Server 2008 SP1
SP1
GDR
6.0.6001.22xxx
Windows Vista SP1 and Windows Server 2008 SP1
SP1
LDR
6.0.6002.18xxx
Windows Vista SP2 and Windows Server 2008 SP2
SP2
GDR
6.0.6002.22xxx
Windows Vista SP2 and Windows Server 2008 SP2
SP2
LDR
Service Pack 1 is integrated into the release version of Windows Server 2008. Therefore, RTM milestone files apply only to Windows Vista. RTM milestone files have a 6.0.0000.xxxxxx version number.
GDR service branches contain only those fixes that are widely released to address widespread, critical issues. LDR service branches contain hotfixes in addition to widely released fixes.
For all supported x86-based versions of Windows Vista and Windows Server 2008