Share via

Release Notes for Windows Server 2008 with Service Pack 2

  • Article

These release notes address late-breaking issues and information related to Windows Server® 2008 Service Pack 2 (SP2). Unless otherwise specified, these notes apply to all editions of Windows Server 2008 with SP2.

Installation

This issue affects Windows Server 2008 Standard, Windows Server 2008 Enterprise, Windows Server 2008 Datacenter, and Windows Server 2008 for Itanium-Based Systems.

If your system is set to boot from an Internet SCSI (iSCSI) device that uses network adapters that do not support iSCSI Boot Firmware Table (IBFT) drivers, the system may fail to boot or may restart repeatedly after you have started a clean installation of Windows Server 2008 Service Pack 2.

To avoid this, ensure that you install the hotfix in article 952942 in the Microsoft Knowledge Base (https://go.microsoft.com/fwlink/?LinkId=149938) in an offline image of Windows Server 2008 before performing a clean installation of the service pack.

Note

This issue only occurs in clean installations of Windows Server 2008. It does not affect upgrade installations, such as upgrading from Windows Server 2008 to Windows Server 2008 with Service Pack 2.

Citrix XenApp

If you are publishing applications with Citrix XenApp and have not installed or configured Terminal Services Licensing (TS Licensing), the Citrix clients will not be able to connect to the server once you install this service pack.

To avoid this, install TS Licensing and configure it with the appropriate number of licenses before you install this service pack. If you have already encountered this, either install and configure TS Licensing, or uninstall the service pack.

For more details, see article 958612 in the Microsoft Knowledge Base (https://go.microsoft.com/fwlink/?LinkId=149967).

Hyper-V

If you have the Hyper-V™ role installed in Windows Server 2008 and have virtual network adapters that are disabled, these virtual network adapters will be enabled after you install this Service Pack.

To avoid this, use Hyper-V Windows® Management Instrumentation (WMI) APIs to delete any disabled virtual network adapters prior to the upgrade. For more information, see Virtualization WMI Provider (https://go.microsoft.com/fwlink/?LinkID=155629).

If this has already occurred, you can either use the Network Connections control panel (Ncpa.cpl) to disable the virtual network adapters or delete them using the Hyper-V APIs.

Information in this document, including URL and other Internet Web site references, is subject to change without notice. Unless otherwise noted, the companies, organizations, products, domain names, e-mail addresses, logos, people, places, and events depicted in examples herein are fictitious. 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.

© 2009 Microsoft Corporation. All rights reserved.

Active Directory, Internet Explorer, Microsoft, Windows, Windows Media, Windows PowerShell, Windows Server, and Windows Vista 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.

2.0