You can not select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
766 lines
50 KiB
766 lines
50 KiB
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN" "http://www.w3.org/TR/REC-html40/strict.dtd">
|
|
|
|
|
|
<HTML DIR="LTR"><HEAD>
|
|
<META HTTP-EQUIV="Content-Type" Content="text/html; charset=Windows-1252">
|
|
<TITLE>Microsoft Windows Datacenter Server, Limited Edition Release Notes</TITLE>
|
|
|
|
<STYLE type="text/css">H1 {
|
|
CLEAR: both; FONT-SIZE: 140%; MARGIN-BOTTOM: 0.5em
|
|
}
|
|
H2 {
|
|
CLEAR: both; MARGIN-TOP: 1.5em; FONT-SIZE: 130%; MARGIN-BOTTOM: 0.5em
|
|
}
|
|
H3 {
|
|
CLEAR: both; MARGIN-TOP: 1.2em; FONT-SIZE: 120%; MARGIN-BOTTOM: 0.5em
|
|
}
|
|
H4 {
|
|
CLEAR: both; MARGIN-TOP: 1.2em; FONT-SIZE: 110%; MARGIN-BOTTOM: 0.5em; MARGIN-LEFT: 1em
|
|
}
|
|
H5 {
|
|
CLEAR: both; MARGIN-TOP: 1.2em; FONT-SIZE: 100%; MARGIN-BOTTOM: 0.5em; MARGIN-LEFT: 2em
|
|
}
|
|
H6 {
|
|
CLEAR: both; MARGIN-TOP: 0.2em; FONT-SIZE: 70%; MARGIN-BOTTOM: 0.5em
|
|
}
|
|
P {
|
|
MARGIN-TOP: 1.5em; MARGIN-BOTTOM: 0.6em
|
|
}
|
|
P.indent {
|
|
MARGIN-LEFT: 3em
|
|
}
|
|
P.note {
|
|
CLEAR: both; MARGIN-TOP: 1em; FONT-WEIGHT: bold; MARGIN-BOTTOM: -0.25em
|
|
}
|
|
P.tip {
|
|
CLEAR: both; MARGIN-TOP: 1em; FONT-WEIGHT: bold; MARGIN-BOTTOM: -0.25em
|
|
}
|
|
P.important {
|
|
CLEAR: both; MARGIN-TOP: 1em; FONT-WEIGHT: bold; MARGIN-BOTTOM: -0.25em
|
|
}
|
|
P.caution {
|
|
CLEAR: both; MARGIN-TOP: 1em; FONT-WEIGHT: bold; MARGIN-BOTTOM: -0.25em
|
|
}
|
|
P.warning {
|
|
CLEAR: both; MARGIN-TOP: 1em; FONT-WEIGHT: bold; MARGIN-BOTTOM: -0.25em
|
|
}
|
|
P.proclabel {
|
|
CLEAR: both; FONT-WEIGHT: bold; FONT-SIZE: 100%
|
|
}
|
|
OL {
|
|
MARGIN-TOP: 0.5em; PADDING-LEFT: 0em; MARGIN-BOTTOM: 0px; MARGIN-LEFT: 2.1em
|
|
}
|
|
OL.indent {
|
|
MARGIN-TOP: 0.5em; PADDING-LEFT: 3em; MARGIN-BOTTOM: 0px; MARGIN-LEFT: 2.1em
|
|
}
|
|
UL {
|
|
MARGIN-TOP: 0.6em; PADDING-LEFT: 0em; MARGIN-BOTTOM: 0px; MARGIN-LEFT: 1.5em; LIST-STYLE-TYPE: disc
|
|
}
|
|
LI {
|
|
CLEAR: both; MARGIN-BOTTOM: 0.7em
|
|
}
|
|
DD {
|
|
MARGIN-BOTTOM: 0px; MARGIN-LEFT: 1.5em
|
|
}
|
|
BODY {
|
|
FONT-SIZE: 80%; BACKGROUND: #ffffff; COLOR: #000000; FONT-FAMILY: Verdana, Arial, Helvetica, Sans Serif
|
|
}
|
|
TABLE {
|
|
FONT-SIZE: 100%; BACKGROUND: #ffffff; COLOR: #000000; FONT-FAMILY: Verdana, Arial, Helvetica, Sans Serif
|
|
}
|
|
A:link {
|
|
COLOR: #0066cc; TEXT-DECORATION: none
|
|
}
|
|
A:visited {
|
|
COLOR: #0066cc; TEXT-DECORATION: none
|
|
}
|
|
A:hover {
|
|
COLOR: #ff0000; TEXT-DECORATION: underline
|
|
}
|
|
A:active {
|
|
COLOR: #ff0000; TEXT-DECORATION: underline
|
|
}
|
|
HR {
|
|
HEIGHT: 1px
|
|
}
|
|
DIV P {
|
|
MARGIN-LEFT: 2em
|
|
}
|
|
a.finePrint {font-size: 85%;}
|
|
</STYLE>
|
|
|
|
</HEAD>
|
|
<BODY>
|
|
|
|
<A NAME="#top_of_file"></A><img src="logo.gif" width="344" height="110" border="0" alt="Microsoft Windows Datacenter Server, Limited Edition">
|
|
<H1>Release Notes</H1>
|
|
|
|
<H4><A HREF="#how_to_use_these_notes_opsd">How to Use These Notes</A></H4>
|
|
|
|
<H4><A HREF="#applications_eyhz">Applications</A></H4>
|
|
|
|
<H4><A HREF="#clustering_rsrd">Clustering</A></H4>
|
|
|
|
<H4><A HREF="#internet_services_uzsc">Internet Services</A></H4>
|
|
|
|
<H4><A HREF="#network_and_communications_nyrx">Network and Communications</A></H4>
|
|
|
|
<H4><A HREF="#other_sudu">Other</A></H4>
|
|
|
|
<H4><A HREF="#security_kxso">Security</A></H4>
|
|
|
|
<H4><A HREF="#server_management_vdtm">Server Management</A></H4>
|
|
|
|
<H4><A HREF="#additional_resources_uwuy">Additional Resources</A></H4>
|
|
|
|
<P><A HREF="#copyright_gwtm">© 2002 Microsoft Corporation. All rights reserved</A></P>
|
|
|
|
<BR><BR>
|
|
<TABLE border=0 cellPadding=0 cellSpacing=0 width="97%">
|
|
<TBODY>
|
|
<TR vAlign=bottom>
|
|
<TD>
|
|
<H1><A NAME="how_to_use_these_notes_opsd"></A> How to Use These Notes</H1>
|
|
</TD>
|
|
<TD align=right><A class="finePrint"
|
|
href="#top_of_file">Back
|
|
to Top</A></TD></TR></TBODY></TABLE>
|
|
<HR>
|
|
|
|
<P>Welcome to the release notes for Windows Datacenter Server, Limited Edition.</P>
|
|
|
|
<P>These release notes contain important information that was not available when the product documentation for Windows Datacenter Server, Limited Edition was written.</P>
|
|
|
|
<P>Click the headings listed at the top of this document to see whether there is any important information that might apply to your specific setup. </P>
|
|
|
|
<P>In addition, read the other release notes files on the Windows Datacenter Server, Limited Edition compact disc (CD):
|
|
|
|
<UL>
|
|
<LI>Read1st.txt (important preinstallation information, located in the \Docs folder on the CD)</li>
|
|
<LI>Setup text files (located in the \Docs folder on the CD)</li>
|
|
<LI>Readme.htm (compatibility and postinstallation notes, located in the root directory on the CD)</li></UL>
|
|
|
|
<P>A list of additional resources is included at the end of this document. To link to the Microsoft Web sites referenced in this document, you must be connected to the Internet.</P>
|
|
|
|
<BR><BR>
|
|
<TABLE border=0 cellPadding=0 cellSpacing=0 width="97%">
|
|
<TBODY>
|
|
<TR vAlign=bottom>
|
|
<TD>
|
|
<H1><A NAME="applications_eyhz"></A> Applications</H1>
|
|
</TD>
|
|
<TD align=right><A class="finePrint"
|
|
href="#top_of_file">Back
|
|
to Top</A></TD></TR></TBODY></TABLE>
|
|
<HR>
|
|
|
|
<H2><A NAME="application_center_2000_sp1_hknb"></A> Application Center 2000</H2>
|
|
|
|
<P>Servers running this Windows product do not support Application Center 2000 SP1 and earlier versions.</P>
|
|
|
|
<P>To work around this issue, upgrade to Application Center 2000 SP2.</P>
|
|
|
|
<H2><A NAME="bizdesk_navigation_links_wixl"></A> Commerce Server 2000 SP1 BizDesk navigation links</H2>
|
|
|
|
<P>When using Commerce Server 2000 SP1 and earlier versions on this Windows product, all BizDesk navigation links result in Active Server Pages (ASP) errors. To work around this issue, you must modify the IIS security metabase. </P>
|
|
<P class="note">Note</P>
|
|
<P class="indent">IIS must be stopped before you can save the metabase.xml file. The following procedure has not been tested under the Direct Metabase Edit option in the Internet Information Services Properties dialog box. </P>
|
|
|
|
<P class="proclabel">To modify the IIS security metabase</p>
|
|
<OL>
|
|
<LI>Using Notepad, open the metabase.xml file located at %systemsdrive%\windows\system32\inetsrv\metabase.xml. </li>
|
|
<LI>For every virtual directory that requires parent paths to be enabled, add this security statement:
|
|
<PRE><CODE>AspEnableParentPaths=</CODE>"<CODE>TRUE</CODE>"<CODE> </CODE></PRE>
|
|
|
|
<P>This property is inherited, so it is not necessary to add it to any subdirectories of a virtual directory that has this flag set.
|
|
|
|
<P>For better security, this value is not recommended for the root directory, as this will turn on the security setting for every Web directory on your server.
|
|
|
|
<P>The following is an example of a virtual directory header in the metabase.xml file:
|
|
|
|
<PRE><CODE><IIsWebVirtualDir Location = </CODE>"<CODE>/LM/W3SVC/1/ROOT/blanksite</CODE>"<CODE>
|
|
.
|
|
.
|
|
.
|
|
AspEnableParentPaths = </CODE>"<CODE>TRUE</CODE>"<CODE>.
|
|
>
|
|
</IIsWebVirtualDir></CODE></PRE>
|
|
</li>
|
|
<LI>Save the file, and then restart IIS if it is not already running.</li></OL>
|
|
|
|
<H2><A NAME="commerce_server_2000_sp1_uwnl"></A> Commerce Server 2000 SP1</H2>
|
|
|
|
<P>Active Server Pages (ASP) pages containing calls to Commerce Server objects will fail and return error information. This will occur in Commerce Server 2000 SP1 because of changes in IIS for Windows Datacenter Server, Limited Edition.</P>
|
|
|
|
<P>To work around this issue, you must change the Internet Guest Account access control list (ACL) in the Program Files folder. Set the permissions to allow read access but not write access.</P>
|
|
|
|
<H2><A NAME="content_managerment_server_cms_2001_svug"></A> Content Management Server 2001</H2>
|
|
|
|
<H3><A NAME="installing_cms_2001_on_a_server_running_windows_net_datacenter_server_ddtn"></A> Installing Content Management Server 2001 on a server running Windows Datacenter Server, Limited Edition</H3>
|
|
|
|
<P>During the installation of Content Management Server (CMS) 2001 on Windows Datacenter Server, Limited Edition, you are pointed to a Microsoft Web site from whichyou can download the Microsoft virtual machine (VM) for Java. On Windows Datacenter Server, Limited Edition, you do not see that information. </P>
|
|
|
|
<P>To work around this issue, you must first download the Microsoft VM from the <A HREF="http://go.microsoft.com/fwlink/?LinkID=284" TARGET="_blank"><U>Microsoft Windows Update Web site</U></A> before proceeding with the CMS 2001 installation.</P>
|
|
|
|
<H3><A NAME="sample_data_method_systems__wiqy"></A> Resolving CMS issues with Windows Datacenter Server, Limited Edition</H3>
|
|
|
|
<P>Any Web sites managed by CMS 2001 will not work with this Windows product. The following error will be displayed: </P>
|
|
|
|
<PRE><CODE>HTTP Error 404 File not found. </CODE></PRE>
|
|
|
|
<P>The same problem occurs when you use the Site Builder client of CMS 2001 to create content for a CMS Web site.</P>
|
|
|
|
<P>To work around this issue, change the access control list for everyone in the IIS_NR directory (in \Program Files\). </P>
|
|
|
|
<H2><A NAME="internet_connection_firewall_icf_and_internet_security_and_acceleration_isa__opwi"></A> Internet Connection Firewall</H2>
|
|
|
|
<P>Internet Connection Firewall (ICF) is not included in Windows Datacenter Server, Limited Edition.</P>
|
|
|
|
<H2><A NAME="internet_security_and_acceleration_isa_server_2000_yyym"></A> Internet Security and Acceleration Server 2000</H2>
|
|
|
|
<P>Because Internet Security and Acceleration (ISA) Server 2000 is part of the BackOffice® 2000 suite, you must have ISA Server 2000 SP1 installed if you intend to run ISA Server 2000 on computers running Windows Datacenter Server, Limited Edition. </P>
|
|
|
|
<P>To work around this issue, either install ISA Server 2000 SP1 or obtain from the ISA team the QFE for computers running Windows Datacenter Server, Limited Edition.</P>
|
|
|
|
<H2><A NAME="microsoft_systems_network_architecture_sna__qpis"></A> Microsoft Systems Network Architecture</H2>
|
|
|
|
<P>Microsoft Systems Network Architecture (SNA) 4.0 SP4 and earlier are not supported on computers running Windows Datacenter Server, Limited Edition. There is no workaround.</P>
|
|
|
|
<H2><A NAME="server_applications_exchange 2000_clustering_setup_qznt"></A> Server Applications: Exchange 2000 Clustering Setup</H2>
|
|
|
|
<P>To set up Exchange 2000 Clustering on Windows Datacenter Server, Limited Edition, you must first implement Microsoft Distributed Transaction Coordinator (MSDTC) as a resource.</P>
|
|
|
|
<P>To implement this as a resource, see Microsoft Knowledge Base article Q290624: "HOWTO: Configure MSDTC in a Windows 2000 Cluster Environment" on the <A HREF="http://go.microsoft.com/fwlink/?LinkId=4441" TARGET="_blank"><U>Microsoft Knowledge Base Web site</U></A>. Follow the instructions provided there.</P>
|
|
|
|
<P>After MSDTC has been implemented as a resource, proceed with the Exchange 2000 Clustering setup.</P>
|
|
|
|
<H2><A NAME="server_management_elgj"></A> Server Management</H2>
|
|
|
|
<P>Server administrators who use the Web interface for remote administration will not be able to perform the following tasks on their servers if they are using a remote Web client:
|
|
|
|
<UL>
|
|
<LI>Set the server name. </li>
|
|
<LI>Join a domain or workgroup.</li>
|
|
<LI>Set the date and time.</li>
|
|
<LI>Shut down your computer.</li>
|
|
<LI>Restart the computer, and then apply a software update.</li>
|
|
<LI>Change the language.</li>
|
|
<LI>Configure alert e-mail.</li>
|
|
<LI>Connect to the administration Web site at port 8098, using Secure Sockets Layer (SSL). </li></UL>
|
|
|
|
<P>On Windows Datacenter Server, Limited Edition, you can install this feature with Configure Your Server (CYS) or as an optional component under Internet Information Services (IIS). </P>
|
|
|
|
<P class="proclabel">To work around this issue</p>
|
|
<OL>
|
|
<LI>Connect by using Remote Desktop for Administration so that you can carry out these operations from a remote client. </li>
|
|
<LI>Access the administration Web site at port 8098 by using SSL. Follow the instructions in the "Configuring SSL on Your Server" section of the IIS documentation.</li></OL>
|
|
|
|
<H2><A NAME="sharepoint_team_services_sts_and_frontpage_server_extensions_fpse__yiye"></A> SharePoint Team Services from Microsoft and FrontPage Server Extensions</H2>
|
|
|
|
<H3><A NAME="sharepoint_team_services___loxb"></A> Installing SharePoint Team Services with Windows Datacenter Server, Limited Edition</H3>
|
|
|
|
<P>If you try to install SharePoint™ Team Services (STS) on Windows Datacenter Server, Limited Edition and the latter already has STS installed on it, your installation might fail. </P>
|
|
|
|
<P class="proclabel">To work around this installation issue</p>
|
|
<OL>
|
|
<LI>Complete a clean installation of Windows Datacenter Server, Limited Edition.</li>
|
|
<LI>Delete the following folder and all of its contents:
|
|
<P><B>C:\Program Files\Microsoft SQL Server</B>
|
|
</li>
|
|
<LI>At the command prompt, type the following:
|
|
<P>net stop http /y
|
|
</li>
|
|
<LI>Delete the following folder and all of its contents:
|
|
<P><B>C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\50</B>
|
|
</li></OL>
|
|
|
|
<P>You can now install STS.</P>
|
|
|
|
<H3><A NAME="usage_analysis_feature_olws"></A> Usage Analysis feature</H3>
|
|
|
|
<P>The FrontPage® Server Extensions (FPSE) Usage Analysis feature is no longer supported for installations of FPSE in Windows Datacenter Server, Limited Edition.</P>
|
|
|
|
<P>To get this feature, install STS (which ships with Windows Datacenter Server, Limited Edition) and continue to use FPSE as before. You can configure STS by using the Configure Your Server Wizard in Windows Datacenter Server, Limited Edition.</P>
|
|
|
|
<BR><BR>
|
|
<TABLE border=0 cellPadding=0 cellSpacing=0 width="97%">
|
|
<TBODY>
|
|
<TR vAlign=bottom>
|
|
<TD>
|
|
<H1><A NAME="clustering_rsrd"></A> Clustering</H1>
|
|
</TD>
|
|
<TD align=right><A class="finePrint"
|
|
href="#top_of_file">Back
|
|
to Top</A></TD></TR></TBODY></TABLE>
|
|
<HR>
|
|
|
|
<H2><A NAME="cluster_service_account_csa_permissions_wkbx"></A> Cluster Service Account permissions</H2>
|
|
|
|
<P>In Windows Datacenter Server, Limited Edition, new Microsoft Message Queuing (MSMQ) resource installations fail to come online when Cluster Service Account (CSA) does not have permission to create child objects on the computer object associated with the dependent Network Name resource.</P>
|
|
|
|
<P>To work around this issue, you must open the Users and Computers MMC snap-in and then open the computer object properties to view the security descriptor. Select the <B>Create all Child Objects</B> check box to grant the CSA permission to create child objects on the computer object created by the Network Name resource. After that, you can bring the MSMQ resource online.</P>
|
|
|
|
<H2><A NAME="majority_node_set_jshi"></A> Majority Node Set </H2>
|
|
|
|
<H3><A NAME="not_to_be_used_as_a_general_purpose_quorum_mechanism_cjcp"></A> Not to be used as a general-purpose quorum mechanism</H3>
|
|
|
|
<P>The Majority Node Set quorum feature available for server clusters in Windows Datacenter Server, Limited Edition is a new technology that has a number of applications. Note, however, that it works differently from a traditional server cluster using a standard quorum resource. </P>
|
|
|
|
<P>This technology is not designed for use as a general-purpose quorum mechanism in Windows Datacenter Server, Limited Edition. Microsoft is releasing this feature as a technology preview that is designed to enable vendors and non-Microsoft software providers to evaluate the feature and to incorporate it into other value-add products and services. Standard quorum resources (physical disk resources or non-Microsoft resources) are recommended for use in server clusters that are deployed in end-user production environments.</P>
|
|
|
|
<H3><A NAME="only_one_instance_can_exist_in_the_cluster_ucxs"></A> Only one instance can exist in the cluster</H3>
|
|
|
|
<P>In Windows Datacenter Server, Limited Edition, only one instance of the Majority Node Set resource can exist in the cluster.</P>
|
|
|
|
<P>To work around this issue, do not create two or more Majority Node Set resources on the same cluster.</P>
|
|
|
|
<H2><A NAME="message_queuing_msmq_fails_to_install_on_a_cluster1_oqiw"></A> Message Queuing fails to install on a cluster</H2>
|
|
|
|
<P>To install Microsoft Message Queuing (MSMQ) in Windows Datacenter Server, Limited Edition, you must have the new <B>RequireKerberos</B> property on the dependent network name enabled. </P>
|
|
|
|
<P class="proclabel">To install MSMQ on Windows Datacenter Server, Limited Edition</p>
|
|
<OL>
|
|
<LI>Create the Network Name resource and leave it offline. </li>
|
|
<LI>Using Cluster Administrator, set the <B>RequireKerberos</B> property to 1 by selecting the <B>Enable Kerberos Authentication</B> check box on the parameter page for the dependent Network Name resource.</li>
|
|
<LI>If Cluster Service Account (CSA) is a domain user, give it the Create Child Objects permission on the newly created computer object.</li>
|
|
<LI>Create the MSMQ resource, and then bring it online.</li></OL>
|
|
|
|
<P>For more information, click <B>Start</B> and then click <B>Help and Support</B>. In Help and Support Center, search for "Installing a Message Queuing resource." </P>
|
|
|
|
<H2><A NAME="network_load_balancing_dndf"></A> Network Load Balancing</H2>
|
|
|
|
<H3><A NAME="access_denied_nnfn"></A> Access denied</H3>
|
|
|
|
<P>Network Load Balancing Manager fails to get authenticated on a host on which it needs to perform an operation, resulting in the following error message:</P>
|
|
|
|
<P><CODE>Win32: Access Denied</CODE></P>
|
|
|
|
<P>To work around this issue, enter new credentials in Network Load Balancing Manager. The host that denied access to Network Load Balancing Manager will authenticate the new credentials.</P>
|
|
|
|
<H3><A NAME="backwards_compatibility_dmcp"></A> Backward compatibility</H3>
|
|
|
|
<P>Network Load Balancing Manager is not backwards compatible with Windows 2000 products. There is no workaround for this issue.</P>
|
|
|
|
<H3><A NAME="viewing_hosts_in_the_cluster_lqsw"></A> Connecting to existing clusters</H3>
|
|
|
|
<P>When you use the <B>Connect to Existing</B> option in Network Load Balancing Manager in Windows Datacenter Server, Limited Edition to connect to an existing cluster so that you can manage it, Network Load Balancing Manager does not automatically display all of the hosts in the cluster.</P>
|
|
|
|
<P class="proclabel">To see all of the hosts in the cluster</p>
|
|
<OL>
|
|
<LI>Create a text file that lists the host names or their dedicated IP addresses, with each host name or IP address on a separate line.</li>
|
|
<LI>Load this file into Network Load Balancing Manager by clicking <B>File</B> and then clicking <B>Load Host List</B>.
|
|
<P>Network Load Balancing Manager will contact each of the hosts, get the network load balancing information, and then display this information in the Network Load Balancing Manager user interface.
|
|
</li></OL>
|
|
|
|
<P>You can also load the text file by entering it as an argument when starting Network Load Balancing Manager from a command line, as in the following example: </P>
|
|
|
|
<PRE><CODE>nlbmgr.exe -hostlist <host file name></CODE></PRE>
|
|
|
|
<H3><A NAME="encryption_of_user_credentials_hnhb"></A> Encryption of user credentials</H3>
|
|
|
|
<P>Network Load Balancing Manager user credentials are stored in unencrypted form in memory, which may pose a security risk to your system.</P>
|
|
|
|
<P>To work around this issue, do not enter credentials in Network Load Balancing Manager if you have security concerns. To use Network Load Balancing Manager without setting the credentials, ensure that the logon credentials you use to log on to the machine on which Network Load Balancing Manager is being run have system administrator privileges on all of the host servers in the cluster.</P>
|
|
|
|
<H3><A NAME="limited_error_checking_yufn"></A> Limited error checking</H3>
|
|
|
|
<P>The error-checking capabilities in Network Load Balancing Manager for Windows Datacenter Server, Limited Edition are very limited. </P>
|
|
|
|
<P>When creating a new cluster:
|
|
|
|
<UL>
|
|
<LI>Network Load Balancing Manager does not attempt to preempt an IP address conflict by finding out whether the new cluster IP address already exists somewhere on the network. </li></UL>
|
|
|
|
<P>When connecting to an existing cluster:
|
|
|
|
<UL>
|
|
<LI>It does not check to see whether a preconfigured cluster that it is trying to connect to is not configured correctly or is in any state other than converged.</li>
|
|
<LI>It does not check to see whether the dedicated IP address that a user specifies is already being used by some other computer on the network.</li></UL>
|
|
|
|
<P>To work around this issue, refer to the troubleshooting guide in online Help to determine the problem with your cluster. After you identify the problem, you can use Network Load Balancing Manager to change cluster parameters remotely to address the problem.</P>
|
|
|
|
<H3><A NAME="manager_logs_nttc"></A> Manager logs</H3>
|
|
|
|
<P>The Network Load Balancing Manager logs displayed in the lower half of the Network Load Balancing Manager windows are not saved to a log file by default.</P>
|
|
|
|
<P>To work around this issue, save the Network Load Balancing Manager logs to a specific log file using the <B>Log</B> option on the <B>Options</B> menu. All subsequent events will be logged to this log file, and the file will be saved when the user quits Network Load Balancing Manager.</P>
|
|
|
|
<H3><A NAME="mode_changes_fxwg"></A> Mode changes</H3>
|
|
|
|
<P>Mode changes—from unicast to multicast or vice versa—that you make through Network Load Balancing Manager are not supported in Windows Datacenter Server, Limited Edition and might result in unexpected behavior.</P>
|
|
|
|
<P>To work around this issue, change modes only at the host server, one host at a time. For additional information, see Help and Support Center (click <B>Start</B> and then click <B>Help and Support</B>).</P>
|
|
|
|
<H3><A NAME="multiple_web_sites_or_applications_maoz"></A> Multiple Web sites or applications</H3>
|
|
|
|
<P>If you create a network load balancing cluster, Network Load Balancing Manager will automatically add the cluster IP address to TCP/IP for each host server in the cluster. However, when you are load-balancing multiple Web sites or applications on this same network load-balancing cluster, Network Load Balancing Manager in Windows Datacenter Server, Limited Edition will not have support to add these additional IP addresses to the cluster hosts. You must do this manually.</P>
|
|
|
|
<P>To work around this issue, you must manually enter the IP addresses corresponding to the additional Web sites or applications in the TCP/IP properties of each host server in the cluster. You can use Network Load Balancing Manager to configure the Per-IP port rules for these IP addresses. </P>
|
|
|
|
<H3><A NAME="remote_control_password_dlto"></A> Remote control password</H3>
|
|
|
|
<P>Changing remote control passwords by using Network Load Balancing Manager is not supported in Windows Datacenter Server, Limited Edition.</P>
|
|
|
|
<P>To work around this issue, you must change the password by using the Network Load Balancing user interface on each host server.</P>
|
|
|
|
<H3><A NAME="verification_of_user_credentials_reyf"></A> Verification of user credentials</H3>
|
|
|
|
<P>Network Load Balancing Manager requires the user to enter his or her credentials, which are then verified with the local host server on which an operation is being performed by Network Load Balancing Manager. Those credentials are not saved when the user quits Network Load Balancing Manager.</P>
|
|
|
|
<P>There is no workaround for this issue. You must reenter user credentials each time you use Network Load Balancing Manager.</P>
|
|
|
|
<BR><BR>
|
|
<TABLE border=0 cellPadding=0 cellSpacing=0 width="97%">
|
|
<TBODY>
|
|
<TR vAlign=bottom>
|
|
<TD>
|
|
<H1><A NAME="internet_services_uzsc"></A> Internet Services</H1>
|
|
</TD>
|
|
<TD align=right><A class="finePrint"
|
|
href="#top_of_file">Back
|
|
to Top</A></TD></TR></TBODY></TABLE>
|
|
<HR>
|
|
|
|
<H2><A NAME="windows_media_services_wms__zalz"></A> Windows Media Services</H2>
|
|
|
|
<H3><A NAME="enabling_authentication_plug_ins_simultaneously_gfky"></A> Enabling authentication plug-ins simultaneously</H3>
|
|
|
|
<P>It is recommended that you do not enable both the Windows Media™ Services (WMS) Basic Authentication and WMS NTLM Authentication plug-ins at the same time. Authorization might not be completed when a media player is using either the MMSU or MMST protocol.</P>
|
|
|
|
<H3><A NAME="excessive_error_events_causes_access_violation_pydd"></A> Excessive error events can cause an access violation</H3>
|
|
|
|
<P>If the server running WMS receives a large number of diagnostic error events (such as when the connection-rate limit is exceeded several dozen times in rapid succession as a result of a virus), the server might encounter an access violation.</P>
|
|
|
|
<P>To work around this issue, try to avoid excessive error events by periodically checking the server for errors protecting it against viruses.</P>
|
|
|
|
<H3><A NAME="help_documentation_odmn"></A> Help documentation</H3>
|
|
|
|
<P>You cannot access WMS Help by using the F1 key. To work around this issue, use the <B>Help</B> button instead.</P>
|
|
|
|
<H3><A NAME="ntlm_authentication_plug_in_borx"></A> NTLM Authentication plug-in</H3>
|
|
|
|
<P>You can enable the WMS NTLM Authentication plug-in only at the server level. If you enable this plug-in at the publishing point level, authorization might not be completed when a media player uses either the MMSU or MMST protocol.</P>
|
|
|
|
<H3><A NAME="script_debugging_in_beta_release_euzw"></A> Script debugging in the beta release</H3>
|
|
|
|
<P>Do not use the script debugging feature in this beta release of WMS. The tool does not perform as expected and may cause issues with the script itself.</P>
|
|
|
|
<P>To work around this issue, debug scripts manually for this release.</P>
|
|
|
|
<BR><BR>
|
|
<TABLE border=0 cellPadding=0 cellSpacing=0 width="97%">
|
|
<TBODY>
|
|
<TR vAlign=bottom>
|
|
<TD>
|
|
<H1><A NAME="network_and_communications_nyrx"></A> Network and Communications</H1>
|
|
</TD>
|
|
<TD align=right><A class="finePrint"
|
|
href="#top_of_file">Back
|
|
to Top</A></TD></TR></TBODY></TABLE>
|
|
<HR>
|
|
|
|
<H2><A NAME="internet_connection_sharing_xsvh"></A> Internet Connection Sharing</H2>
|
|
|
|
<P>The Internet Connection Sharing feature is not included in Windows Datacenter Server, Limited Edition.</P>
|
|
|
|
<H2><A NAME="network_bridge_ajan"></A> Network Bridge</H2>
|
|
|
|
<P>The Network Bridge feature is not included in Windows Datacenter Server, Limited Edition.</P>
|
|
|
|
<H2><A NAME="real_time_communication_server_yowy"></A> Real-Time Communications service</H2>
|
|
|
|
<P>The version of the Real-Time Communications (RTC) service that ships with Windows Datacenter Server, Limited Edition is not currently compatible with either of the following versions of MSN® Messenger:
|
|
|
|
<UL>
|
|
<LI>Version 4.0, which is included with Windows XP</li>
|
|
<LI>Version 4.5, which is currently available for downloading from the main Microsoft Web site</li></UL>
|
|
|
|
<H3><A NAME="processing_requests_to_msn_messenger_buddies_tjzf"></A> Processing requests to MSN Messenger buddies</H3>
|
|
|
|
<P>The RTC service has the ability to verify the existence of your messenger buddy in Active Directory™ before accepting and processing presence requests targeted to this buddy. Turn off this feature in any of the following situations:
|
|
|
|
<UL>
|
|
<LI>You are not using Active Directory.</li>
|
|
<LI>You are planning to use sign-in names that are not present in Active Directory.</li>
|
|
<LI>You are experiencing problems with propagating presence information.</li>
|
|
<LI>You do not want to use this feature.</li></UL>
|
|
|
|
<P class="proclabel">To disable subscription verification</p>
|
|
<OL>
|
|
<LI>Click <B>Start</B>, click <B>Control Panel</B>, click <B>Administration Tools</B>, and then click <B>Computer Management</B>.</li>
|
|
<LI>In <B>Extension Modules</B>, click <B>Routing</B>. </li>
|
|
<LI>Right-click the <B>Registrar</B> module in the right pane, and then click <B>Properties</B>. </li>
|
|
<LI>On the <B>Authentication</B> tab, clear the <B>Verify offline subscribes</B> check box.</li></OL>
|
|
|
|
<H3><A NAME="remote_administration_cqqg"></A> Remote administration</H3>
|
|
|
|
<P>Remote administration of the RTC service is not supported in this release of Windows Datacenter Server, Limited Edition.</P>
|
|
|
|
<H3><A NAME="supported_authentication_methods_dfzh"></A> Supported authentication methods</H3>
|
|
|
|
<P>Only Basic Authentication is supported in this release of Windows Datacenter Server, Limited Edition. Other authentication methods (such as Integrated Windows Authentication and Digest Authentication) will be supported in future releases.</P>
|
|
|
|
<H3><A NAME="using_basic_authentication_iezb"></A> Using Basic Authentication</H3>
|
|
|
|
<P>To use Basic Authentication, you must change the realm value on a server. This value should be equal to the domain portion of the user's Uniform Resource Identifier (URI).</P>
|
|
|
|
<P>For example, if your sign-in name is [email protected], you must configure the realm to adatum.com. To do this, create a file named realm.vbs with the following contents: </P>
|
|
|
|
<PRE><CODE>----- code start--------------------------------------
|
|
' VBScript source code Dim oSvc, oUser, oCtx, oProx
|
|
Set objArgs = WScript.Arguments
|
|
if (objArgs.count <> 1) then WScript.echo </CODE>"<CODE>Usage: setrealm </CODE>"<CODE>else set oSvc =
|
|
CreateObject(</CODE>"<CODE>WbemScripting.SWbemLocator</CODE>"<CODE>).ConnectServer(</CODE>"<CODE>.</CODE>"<CODE>,</CODE>"<CODE>root\cimv2</CODE>"<CODE>)
|
|
set oCtx = CreateObject(</CODE>"<CODE>WbemScripting.SWbemNamedValueSet</CODE>"<CODE>)
|
|
set oUser = oSvc.InstancesOf(</CODE>"<CODE>MSFT_SIPProxySecuritySetting</CODE>"<CODE>)
|
|
if (oUser.count > 1 ) then WScript.echo </CODE>"<CODE>More than one instance of Securitysetting. Not setting the realm</CODE>"<CODE>else
|
|
for each oProx in oUser WScript.echo </CODE>"<CODE>Setting the realm attribute to : </CODE>"<CODE> &
|
|
objArgs(0) oProx.realm = objArgs(0) oProx.Put_ 1, oCtx
|
|
next
|
|
end if
|
|
end if
|
|
---------code end-----------------------------------</CODE></PRE>
|
|
|
|
<P>Run this file from a command line with the syntax "realm ." Note that you must have administrator privileges to do this.</P>
|
|
|
|
<H3><A NAME="using_phones_in_rtc_deployments_wbxq"></A> Using phones in Real-Time Communications deployments</H3>
|
|
|
|
<P>To use Session Initiation Protocol (SIP) phones in your deployment, you need to add a new domain entry to the Registrar domain table. To do this, open the Real-Time Communications (RTC) service Microsoft Management Console (MMC) snap-in, right-click the Registrar Module icon in the Routing Extension module, and then add a new domain with the name "<CODE>*;user=phone</CODE>".</P>
|
|
|
|
<P>To use Public Switched Telephone Network (PSTN) phones by routing calls through the IP to the PSTN gateway, create an entry in the routing table. To do this, open the RTC server MMC snap-in. In the routing pane, add two routes, as described in the following procedures.</P>
|
|
|
|
<P class="proclabel">To add the first route</p>
|
|
<OL>
|
|
<LI>Type <B>User *</B>.</li>
|
|
<LI>Type <B>domain name <Fully Qualified Domain Name (FQDN) of the SIP proxy server></B>.</li>
|
|
<LI>Select <B>Phone URI</B>.</li>
|
|
<LI>Type the IP address of the gateway.</li>
|
|
<LI>Select <B>Replace URI</B>.</li></OL>
|
|
|
|
<P class="proclabel">To add the second route</p>
|
|
<OL>
|
|
<LI>Type <B>User *</B>.</li>
|
|
<LI>Type <B>domain name <IP address of the SIP proxy server></B>.</li>
|
|
<LI>Select <B>Phone URI</B>.</li>
|
|
<LI>Type the IP address of the gateway.</li>
|
|
<LI>Select <B>Replace URI</B>.</li></OL>
|
|
|
|
<P>If the user is registered as a phone number and the route "*@*" is used, incoming calls will not be routed to registered users.</P>
|
|
|
|
<BR><BR>
|
|
<TABLE border=0 cellPadding=0 cellSpacing=0 width="97%">
|
|
<TBODY>
|
|
<TR vAlign=bottom>
|
|
<TD>
|
|
<H1><A NAME="other_sudu"></A> Other</H1>
|
|
</TD>
|
|
<TD align=right><A class="finePrint"
|
|
href="#top_of_file">Back
|
|
to Top</A></TD></TR></TBODY></TABLE>
|
|
<HR>
|
|
|
|
<H2><A NAME="configure_your_server_wizard_hzcp"></A> Configure your Server Wizard</H2>
|
|
|
|
<P>If you select the file-server role and install the Web user interface for file server administration, you will be unable to view the FTP and Shares site logs by using the Web user interface. The displayed logs are actually the Administration site logs.</P>
|
|
|
|
<P>There is no workaround for this issue. </P>
|
|
|
|
<H2><A NAME="finding_information_about_making_shadow_copies_of_shared_folders_gdmw"></A> Finding information about making shadow copies of shared folders</H2>
|
|
|
|
<P>To find information about making shadow copies of shared folders, open Help from the command line by clicking <B>Start</B>, clicking <B>Run</B>, and then typing the following:</P>
|
|
|
|
<P>hh windows.chm</P>
|
|
|
|
<P>Click the <B>Contents</B> tab, and then click the following (in order): <B>Disks and Data</B>,<B> Backing Up and Recovering Data</B>, and <B>Shadow Copies of Shared Folders</B>. Under <B>Shadow Copies of Shared Folders</B>, click the titles of the topics you want to see.</P>
|
|
|
|
<H2><A NAME="hardware_acceleration_for_direct3d_and_opengl_pbmy"></A> Hardware acceleration for Direct3D and OpenGL</H2>
|
|
|
|
<P>Hardware acceleration for Direct3D® and OpenGL is not available in Windows Datacenter Server, Limited Edition.</P>
|
|
|
|
<H2><A NAME="microsoft_virtual_machine_for_java1_yeph"></A> Microsoft virtual machine for Java</H2>
|
|
|
|
<P>The Microsoft virtual machine (Microsoft VM) is now available only as a Web download. The latest 32-bit edition of the Microsoft VM can be obtained at the <A HREF="http://go.microsoft.com/fwlink/?LinkId=284" TARGET="_blank"><U>Microsoft Windows Update Web site</U></A>. If you do not already have a virtual machine on your system and visit a Web site with a Java applet, Internet Explorer will automatically ask if you wish to install the Microsoft VM.</P>
|
|
|
|
<H2><A NAME="terminal_services_fgvj"></A> Terminal Server</H2>
|
|
|
|
<P>Terminal Server (formerly known as Terminal Services in application server mode) is not supported with this release of Windows Datacenter Server, Limited Edition. Remote Desktop for Administration (formerly known as Terminal Services in remote administration mode) is supported for Windows Datacenter Server, Limited Edition. </P>
|
|
|
|
<H2><A NAME="using_dfs_between_forests_with_established_trust_relationships_fnxb"></A> Using DFS between forests with established trust relationships</H2>
|
|
|
|
<P>When you create a trust relationship between two forests Distributed File System (DFS) will not be able to resolve the address in the remote forest. DFS obtains the list of trusted domains from the directory and uses this information to access the namespace. </P>
|
|
|
|
<P>To work around this issue, set up a direct trust with every domain on which you need domain DFS to work.</P>
|
|
|
|
<BR><BR>
|
|
<TABLE border=0 cellPadding=0 cellSpacing=0 width="97%">
|
|
<TBODY>
|
|
<TR vAlign=bottom>
|
|
<TD>
|
|
<H1><A NAME="security_kxso"></A> Security</H1>
|
|
</TD>
|
|
<TD align=right><A class="finePrint"
|
|
href="#top_of_file">Back
|
|
to Top</A></TD></TR></TBODY></TABLE>
|
|
<HR>
|
|
|
|
<H2><A NAME="applications_using_local_security_authority_lsa__hxzg"></A> Applications using Local Security Authority </H2>
|
|
|
|
<P>Security has been upgraded for Windows Datacenter Server, Limited Edition. </P>
|
|
|
|
<P>Applications that try to open a Local Security Authority (LSA) handle anonymously will not be permitted access. This might result in some applications failing and returning an "Access Denied" error message.</P>
|
|
|
|
<P>For example, if you have a Structured Query Language (SQL) database hosted on a computer running Windows Datacenter Server, Limited Edition, with an Internet Information Services (IIS) server using Named Pipes accessing the SQL database, the following error might be reported:</P>
|
|
|
|
<P>0x80004005 on an Access Data Object (ADODB) Open. </P>
|
|
|
|
<P>To verify that the failure is caused by the application trying to make an anonymous call, check the computer's event log for Event ID=6033. This log tells you how to disable this security feature if it does block functionality. </P>
|
|
|
|
<P>You are advised to follow up with the application vendor who is making this call to ensure that the application is updated and able to make secure calls.</P>
|
|
|
|
<H2><A NAME="certificate_services_xxfx"></A> Certificate Services</H2>
|
|
|
|
<H3><A NAME="failed_enrollment_on_a_windows_2000_client_acqh"></A> Failed enrollment on a Windows 2000 client</H3>
|
|
|
|
<P>A Windows 2000 enrollment station cannot enroll against a Windows Datacenter Server, Limited Edition certification authority and domain controller unless Service Pack 2 for Windows 2000 is installed on the enrollment station. Otherwise, an error will occur on the Windows 2000 client and the enrollment will fail.</P>
|
|
|
|
<P>To work around this issue, install Windows 2000 Service Pack 2.</P>
|
|
|
|
<H3><A NAME="version_2_templates_mkdt"></A> Version 2 templates</H3>
|
|
|
|
<P>A Windows Datacenter Server, Limited Edition certification authority will not be able to issue any new version 2 templates in a Windows 2000 forest that has been upgraded to a Windows Datacenter Server, Limited Edition schema unless Service Pack 3 for Windows 2000 is used for all domain controllers. This is because a Windows Datacenter Server, Limited Edition certification authority expects only signed Lightweight Directory Access Protocol (LDAP) responses from domain controllers. This only applies to any new version 2 template that is created or duplicated.</P>
|
|
|
|
<P>To work around this issue, apply the QFE provided in Microsoft Knowledge Base article Q308385 on all domain controllers.</P>
|
|
|
|
<BR><BR>
|
|
<TABLE border=0 cellPadding=0 cellSpacing=0 width="97%">
|
|
<TBODY>
|
|
<TR vAlign=bottom>
|
|
<TD>
|
|
<H1><A NAME="server_management_vdtm"></A> Server Management</H1>
|
|
</TD>
|
|
<TD align=right><A class="finePrint"
|
|
href="#top_of_file">Back
|
|
to Top</A></TD></TR></TBODY></TABLE>
|
|
<HR>
|
|
|
|
<H2><A NAME="help_for_shutdown_exe_rqzq"></A> Help for Shutdown.exe</H2>
|
|
|
|
<P>In this release, Shutdown.exe Help is not accessible through the interactive shutdown dialog box activated from the command prompt. Neither F1 nor the Help button link to the Help file. </P>
|
|
|
|
<P>To view this Help file, click <B>Start</B>, click <B>Help and Support</B>, and then search for "shutdown."</P>
|
|
|
|
<H2><A NAME="system_state_data_feature_works_for_administrators_only_jfpc"></A> System State Data feature works for administrators only</H2>
|
|
|
|
<P>Any shutdown initiated by pressing CTRL+AL +DELETE and then clicking the <B>Shut Down</B> button will activate the System State Data feature. However, this feature works only if the user shutting down the computer is an administrator on the computer.</P>
|
|
|
|
<P>In all cases, only administrators on the computer can report the system state information to Microsoft if the error-reporting functionality is turned on. </P>
|
|
|
|
<BR><BR>
|
|
<TABLE border=0 cellPadding=0 cellSpacing=0 width="97%">
|
|
<TBODY>
|
|
<TR vAlign=bottom>
|
|
<TD>
|
|
<H1><A NAME="additional_resources_uwuy"></A> Additional Resources</H1>
|
|
</TD>
|
|
<TD align=right><A class="finePrint"
|
|
href="#top_of_file">Back
|
|
to Top</A></TD></TR></TBODY></TABLE>
|
|
<HR>
|
|
|
|
<P>To review the latest hardware compatibility information, see the <A HREF="http://go.microsoft.com/fwlink/?LinkId=1858" TARGET="_blank"><U>Windows Hardware Compatibility Web site</U></A>.</P>
|
|
|
|
<P>Please note, if you require support for Windows Datacenter, Limited Edition, you must contact your Original Equipment Manufacturer (OEM).</P>
|
|
|
|
<BR><BR>
|
|
<TABLE border=0 cellPadding=0 cellSpacing=0 width="97%">
|
|
<TBODY>
|
|
<TR vAlign=bottom>
|
|
<TD>
|
|
<H1><A NAME="copyright_gwtm"></A> Copyright</H1>
|
|
</TD>
|
|
<TD align=right><A class="finePrint"
|
|
href="#top_of_file">Back
|
|
to Top</A></TD></TR></TBODY></TABLE>
|
|
<HR>
|
|
|
|
<P>Information in this document, including URL and other Internet Web site references, is subject to change without notice and is provided for informational purposes only. The entire risk of the use or results of the use of this document remains with the user, and Microsoft Corporation makes no warranties, either express or implied. Unless otherwise noted, the example companies, organizations, products, domain names, e-mail addresses, logos, people, places and events depicted herein are fictitious, and no association with any real company, organization, product, domain name, e-mail address, logo, person, place or event is intended or should be inferred. Complying with all applicable copyright laws is the responsibility of the user. Without limiting the rights under copyright, no part of this document may be reproduced, stored in or introduced into a retrieval system, or transmitted in any form or by any means (electronic, mechanical, photocopying, recording, or otherwise), or for any purpose, without the express written permission of Microsoft Corporation. </P>
|
|
|
|
<P>Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this document. Except as expressly provided in any written license agreement from Microsoft, the furnishing of this document does not give you any license to these patents, trademarks, copyrights, or other intellectual property.</P>
|
|
|
|
<P>© 2002 Microsoft Corporation. All rights reserved.</P>
|
|
|
|
<P>Microsoft, Active Directory, BackOffice, Direct3D, FrontPage, MSN, SharePoint, Windows, and Windows Media are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries.</P>
|
|
|
|
<P>The names of actual companies and products mentioned herein may be the trademarks of their respective owners.</P>
|
|
|
|
<H2><A NAME="acknowledgements_jrun"></A> Acknowledgements</H2>
|
|
|
|
<P>Portions of this product are based in part on the work of Mark H. Colburn and sponsored by the USENIX Association. Copyright © 1989 Mark H. Colburn. All rights reserved.</P>
|
|
|
|
<P>This product includes software developed by the University of California, Berkeley and its contributors.</P>
|
|
|
|
<P>Portions of this product are based in part on the work of the Regents of the University of California, Berkeley and its contributors. Because Microsoft has included the Regents of the University of California, Berkeley, software in this product, Microsoft is required to include the following text that accompanied such software:</P>
|
|
|
|
<P class="indent">Copyright © 1985, 1988 Regents of the University of California. All rights reserved. </P>
|
|
|
|
<P class="indent">Redistribution and use in source and binary forms are permitted provided that the above copyright notice and this paragraph are duplicated in all such forms and that any documentation, advertising materials, and other materials related to such distribution and use acknowledge that the software was developed by the University of California, Berkeley. The name of the University may not be used to endorse or promote products derived from this software without specific prior written permission. THIS SOFTWARE IS PROVIDED "AS IS" AND WITHOUT ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF MERCHANTIBILITY AND FITNESS FOR A PARTICULAR PURPOSE.</P>
|
|
|
|
<P>Portions of this product are based in part on the work of Greg Roelofs. Because Microsoft has included the Greg Roelofs software in this product, Microsoft is required to include the following text that accompanied such software:</P>
|
|
|
|
<P class="indent">Copyright © 1998-1999 Greg Roelofs. All rights reserved.</P>
|
|
|
|
<P class="indent">This software is provided "as is," without warranty of any kind, express or implied. In no event shall the author or contributors be held liable for any damages arising in any way from the use of this software.</P>
|
|
|
|
<P class="indent">Permission is granted to anyone to use this software for any purpose, including commercial applications, and to alter it and redistribute it freely, subject to the following restrictions:
|
|
|
|
<OL>
|
|
<LI>Redistributions of source code must retain the above copyright notice, disclaimer, and this list of conditions.</li>
|
|
<LI>Redistributions in binary form must reproduce the above copyright notice, disclaimer, and this list of conditions in the documentation and/or other materials provided with the distribution.</li>
|
|
<LI>All advertising materials mentioning features or use of this software must display the following acknowledgment:</li></OL>
|
|
|
|
<P class="indent">This product includes software developed by Greg Roelofs and contributors for the book, <I>PNG: The Definitive Guide</I>, published by O'Reilly and Associates.</P>
|
|
|
|
<P>Portions of this software are based in part on the work of Hewlett-Packard Company. Because Microsoft has included the Hewlett-Packard Company software in this product, Microsoft is required to include the following text that accompanied such software:</P>
|
|
|
|
<P class="indent">Copyright © 1994 Hewlett-Packard Company</P>
|
|
|
|
<P class="indent">Permission to use, copy, modify, distribute and sell this software and its documentation for any purpose is hereby granted without fee, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation. Hewlett-Packard Company makes no representations about the suitability of this software for any purpose. It is provided "as is" without express or implied warranty.</P>
|
|
|
|
<P>Portions of this software are based in part on the work of the University of Southern California. Because Microsoft has included the University of Southern California software in this product, Microsoft is required to include the following text that accompanied such software:</P>
|
|
|
|
<P class="indent">Copyright © 1996 by the University of Southern California. All rights reserved.</P>
|
|
|
|
<P class="indent">Permission to use, copy, modify, and distribute this software and its documentation in source and binary forms for any purpose and without fee is hereby granted, provided that both the above copyright notice and this permission notice appear in all copies — and that any documentation, advertising materials, and other materials related to such distribution and use acknowledge that the software was developed in part by the University of Southern California, Information Sciences Institute. The name of the University may not be used to endorse or promote products derived from this software without specific prior written permission.</P>
|
|
|
|
<P class="indent">THE UNIVERSITY OF SOUTHERN CALIFORNIA makes no representations about the suitability of this software for any purpose. THIS SOFTWARE IS PROVIDED "AS IS" AND WITHOUT ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.</P>
|
|
|
|
<P>Portions of this software are based in part on the work of Luigi Rizzo. Because Microsoft has included the Luigi Rizzo software in this product, Microsoft is required to include the following text that accompanied such software:</P>
|
|
|
|
<P class="indent">© 1997-98 Luigi Rizzo ([email protected])</P>
|
|
|
|
<P class="indent">Portions derived from code by Phil Karn ([email protected]), Robert Morelos-Zaragoza ([email protected]) and Hari Thirumoorthy ([email protected]), Aug 1995</P>
|
|
|
|
<P class="indent">Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
|
|
|
|
<OL>
|
|
<LI>Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.</li>
|
|
<LI>Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.</li></OL>
|
|
|
|
<P class="indent">THIS SOFTWARE IS PROVIDED BY THE AUTHORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.</P>
|
|
|
|
<P>Portions of this software are based in part on the work of Massachusetts Institute of Technology. Because Microsoft has included the Massachusetts Institute of Technology software in this product, Microsoft is required to include the following text that accompanied such software:</P>
|
|
|
|
<P class="indent">Copyright © 1989,1990 by the Massachusetts Institute of Technology. All Rights Reserved.</P>
|
|
|
|
<P class="indent">WITHIN THAT CONSTRAINT, permission to use, copy, modify, and distribute this software and its documentation for any purpose and without fee is hereby granted, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation, and that the name of M.I.T. not be used in advertising or publicity pertaining to distribution of the software without specific, written prior permission. M.I.T. makes no representations about the suitability of this software for any purpose. It is provided "as is" without express or implied warranty.</P>
|
|
|
|
<P class="indent">Under U.S. law, this software may not be exported outside the US without license from the U.S. Commerce department.</P>
|
|
|
|
<P>Portions of this software are based in part on the work of Regents of The University of Michigan. Because Microsoft has included the Regents of The University of Michigan software in this product, Microsoft is required to include the following text that accompanied such software:</P>
|
|
|
|
<P class="indent">Copyright © 1995,1996 Regents of The University of Michigan. All Rights Reserved.</P>
|
|
|
|
<P class="indent">Permission to use, copy, modify, and distribute this software and its documentation for any purpose and without fee is hereby granted, provided that the above copyright notice appears in all copies and that both that copyright notice and this permission notice appear in supporting documentation, and that the name of The University of Michigan not be used in advertising or publicity pertaining to distribution of the software without specific, written prior permission. This software is supplied as is without expressed or implied warranties of any kind.</P>
|
|
|
|
</body>
|
|
</HTML>
|