These release notes address late-breaking issues and information about Microsoft® Windows® Code Name "Longhorn" beta 1 and Microsoft Windows Server Code Name "Longhorn" beta 1. Unless otherwise specified, these notes apply to both versions of the product.

The following components and features are being phased out and are not present in this beta release of "Longhorn" versions of Windows operating systems.

• The Computer Browser Service used to find other computers in My Network Places. It is disabled starting with this release of "Longhorn" versions of Windows.
  
  
• The concept of interactive services is being phased out, starting with "Longhorn" versions of Windows. Session 0 is now reserved for services and system processes, and users can no longer interactively log on to session 0. Services that assume session 0 is an interactive session might no longer work correctly. Windows and dialog boxes that were displayed directly from services will not be visible to the user, and the service might stop responding if the user interface (UI) requires user input.
  
  
• The following video components and features are being phased out, starting with this release of "Longhorn" versions of Windows, so you should not use them:
  
  
  • IP data (IPSink, SLIP, NabtsFec, MPE, StreamIP, or NDisIP)
    
    
  • Video port-based captions
    
    
  • VBI bit slicing
    
    
  • Teletext rendering
    
    
  • MSWebDVD
    
    

The following issues and workarounds pertain to non-Microsoft assistive technology applications that you can use in conjunction with "Longhorn" versions of Windows.

This information about known directory services issues applies only to Windows Server "Longhorn" beta 1.

• You must prepare your Active Directory forest and domain with Windows Server "Longhorn" beta 1 updates prior to promoting your first Windows Server "Longhorn" domain controller into an existing environment. Use the Windows Server "Longhorn" beta 1 version of the Active Directory Preparation Tool (adprep) located in %WINDIR%\System32\Adprep to prepare the environment. For information about how to use Adprep, see the Microsoft Web site.
  
  

• You cannot use the Active Directory Domain Controller Installation Wizard (Dcpromo.exe) on server core installations. Instead, use the unattended version of dcpromo (Dcpromocmd.exe) to install or remove the domain controller role on servers running a server core installation. Using Dcpromocmd.exe requires an answer file. For more information, see the Microsoft Windows Server Code Name "Longhorn" Beta 1 Server Core Step-By-Step Guide on the Microsoft Connect Web site.
  
  
• You cannot use the Active Directory Domain Controller Installation Wizard (Dcpromo.exe) to promote a read-only domain controller. Instead, use the unattended version of dcpromo (Dcpromocmd.exe). For more information, see the Read-Only Domain Controller Step-by-Step Guide on the Microsoft Connect Web site.
  
  
• When you promote a server core installation to the domain controller role in a new forest and domain, Domain Name System (DNS) is not installed, even if you elect to install it during the promotion. Instead, you must configure DNS manually after you have installed the domain controller role. To enable and start the DNS Server service in Windows Server "Longhorn" beta 1, run Dnsserverrole.cmd from a command line.
  
  

In this release of "Longhorn" versions of Windows, the Group Policy engine uses a new diagnostic logging system, so portions of diagnostic events viewed in Userenv logs might not be visible.

You might be able to view some of the information by using the Group Policy Management Console remotely from a computer running Windows Server™ 2003 or Windows XP.

The following eHome video features have been verified in this release of "Longhorn" versions of Windows:

• Analog TV (both NTSC and PAL) capture and playback in GraphEdit.
  
  
• DVR-MS playback in GraphEdit and Microsoft Windows Media® Player.
  
  
• AVI, WMV, and MPEG1 playback in GraphEdit.
  
  
• DVD playback in GraphEdit.
  
  

The following video capture boards have been verified to work in this release of "Longhorn" versions of Windows:

• Leadtek Conexant NTSC version 5.13.22.6104
  
  
• Hauppauge 32552 NTCS version 1.18.21.22266
  
  

The following features have not been verified to work in this release of "Longhorn" versions of Windows:

• Digital TV capture (ATSC and DVB).
  
  
• 64-bit TV capture and playback.
  
  

This information applies to Windows Server "Longhorn" only.

Help and Support documentation is not included in this release of Windows Server "Longhorn." Specifically:

• Server-related assistance is not available.
  
  
• Assistance documentation cannot be reached from the table of contents.
  
  
• Search results that include online results return information that pertains to Windows "Longhorn," which is the client version of this product.
  
  

For more information about Windows Server "Longhorn" beta 1, you can download Windows Server "Longhorn" beta 1 Server Step-by-Step GuidesStep-by-Step Guides from the Microsoft Connect Web site.

Known network issues include:

• Routing and Remote Access: When the Routing and Remote Access service is configured, performing a walk/browse with Simple Network Management Protocol (SNMP) will cause the SNMP application to stop unexpectedly. There is no workaround at this time.
  
  
• Network Connections Folder: Received Packet statistics are not updated for network connections in the Network Connections Folder. The Received Packet statistics in the Activity section of the General tab of the network connection will be 0. To verify network traffic, use the Networking tab in Task Manager.
  
  
• Infrared (IrDA) Devices: There are known issues with IrDA devices There are no workarounds at this time. These issues include the following:
  
  
  • When you transfer files using an IrDA device, they are saved in C:\Users\Default User\Desktop instead of the desktop for your account.
    
    
  • Certain devices can take up to 20 minutes to discover each other.
    
    
  • Certain IrDA device drivers cannot be uninstalled successfully.
    
    
  • Certain IrDA devices can cause the system to stop responding for up to 40 seconds if the infrared transmission is interrupted.
    
    

For information about server core installations, download the Microsoft Windows Server Code Name "Longhorn" Beta 1 Server Core Step-By-Step Guide.

Microsoft Windows System Resource Manager (WSRM) is included in all versions of Windows Server "Longhorn" beta 1. However, the WSRM administrative snap-in is not available in the 64-bit versions.

You can still administer the WSRM service running on 64-bit Windows Server "Longhorn" in two ways.

• Run the WSRM snap-in or command-line application (Wsrmc.exe) on an x86-based version of Windows Server "Longhorn" beta 1, and connect remotely to the 64-bit computer running the WSRM service.
  
  
• Run the WSRM command-line application (Wsrmc.exe) locally on the 64-bit computer that is running the WSRM service.
  
  

Sounds associated with Windows Program Events or Sound Schemes cannot be changed in this release of "Longhorn" versions of Windows.

There is no workaround for this version.

• Internet Explorer Proxy Settings: This information applies to Windows Server "Longhorn." If Internet Explorer is configured to automatically detect proxy settings, and no proxy is configured, successful product activation might take up to one minute. You might want to clear the Automatically Detect Proxy Settings box to speed up the process. This affects only those users who are directly connected to the Internet. Users connected through a LAN are not affected.
  
  
• User Account Protection: This information applies only to Windows "Longhorn," and not to Windows Server "Longhorn." Windows activation will fail if Least User Access is manually enabled. To successfully activate Windows, ensure LUA is disabled, log on as Administrator, and proceed with activation.
  
  

This document supports a preliminary release of a software product that may be changed substantially prior to final commercial release, and is the confidential and proprietary information of Microsoft Corporation.  It is disclosed pursuant to a non-disclosure agreement between the recipient and Microsoft. This document is provided for informational purposes only and Microsoft makes no warranties, either express or implied, in this document.  Information in this document, including URL and other Internet Web site references, is subject to change without notice.  The entire risk of the use or the results from the use of this document remains with the user.  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.

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.

© 2005 Microsoft Corporation.  All rights reserved.

Active Directory, Microsoft, MS-DOS, Visual Basic, Visual Studio, Windows, Windows NT, Windows Server and Windows Media are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries.

All other trademarks are property of their respective owners.