Exportar (0) Imprimir
Expandir todo

Known Issues When Upgrading to Windows Server 2008 R2

Actualizado: septiembre de 2010

Se aplica a: Windows Server 2008 R2

Following are solutions for known issues that you may experience after you upgrade to Windows Server 2008 R2. For a complete list of known issues, see Release Notes for Windows Server 2008 R2 (http://go.microsoft.com/fwlink/?LinkID=160340).

In this document

Windows Media Services 2008

The following features are not present in Windows Server 2008:

  • The Streaming Media Services role (which includes the latest version of Windows Media® Services)

  • The Streaming Media Services role administration tools for the Remote Server Administration Tools feature in Server Manager.

To obtain these features, you must run the appropriate Streaming Media Services role installer file after upgrading.

For more information about Windows Media Services features and benefits, see http://go.microsoft.com/fwlink/?LinkID=99270.

For more information about how to install the Streaming Media Services role on the full and Server Core installation options of the Windows Server 2008 operating system and about how to install a snap-in for Microsoft Management Console (MMC) that can be used to configure Windows Media Services from a remote computer, see article 934518, "How to install Windows Media Services in Windows Server 2008," in the Microsoft Knowledge Base (http://go.microsoft.com/fwlink/?LinkId=89041).

Windows Deployment Services

When you have upgraded your domain controllers to Windows Server 2008, client computers that only support the Data Encryption Standard (DES) cannot establish a secure channel with the Net Logon service. As a result, installations and attempts to join the domain will fail, including Windows Deployment Services installations of Windows Vista®, Windows® XP, Windows Server 2003, Windows 2000, and Active Directory® Migration Tool. In addition, non-Microsoft server message block (SMB) and network-attached storage devices that do not support the Message Digest 5 (MD5) algorithm standard will also fail to establish a secure channel.

To avoid these failures, do the following:

  • Upgrade all client computers and domain controllers to a Windows operating system that is not earlier than Windows 2000.

  • Contact a vendor of non-Microsoft SMB and network-attached storage devices to obtain a version that supports MD5.

If you must support DES, enable support for Windows NT 4.0 cryptography. When you edit the Group Policy object, under Computer Configuration, navigate to Administrative Templates, and then navigate to and enable the Allow cryptography algorithms compatible with Windows NT 4.0 policy setting.

Print servers running Windows Server 2003

Printers on a computer running Windows Server 2003 R2 or Windows 2003 with R2 Print Management Console are incompatible with Windows Server 2008, so you must back up these printers before you upgrade to Windows Server 2008. Incompatible printers are deleted during the upgrade process. After you upgrade, the restore process removes the Windows 2003 R2 Print Management incompatibilities.

To migrate printers on a remote print server running Windows Server 2003 R2 to Windows Server 2008, you first install Print Management on a computer running Windows Vista. You then add the remote print server.

To install and start Print Management on a computer running Windows Vista

  1. Click the Start button, and then click Run.

  2. In the Open text box, type MMC to open the Microsoft Management Console.

  3. On the File menu, click Add/Remove Snap-in.

  4. In the Available snap-ins list, click Print Management, and then click Add to add it to the Selected snap-ins list.

    You can now add the remote print server.

  5. In the Configuration Print Management window:

    1. Type the name of the remote print server.

    2. Click Add to List.

    3. Click Finish.

  6. Click OK.

Next, back up your source server data to a printer settings file using the Printer Migration Wizard in preparation for exporting printer queues, print drivers, and printer settings.

To back up the source server using the Printer Migration Wizard

  1. Open the Print Management snap-in. Click Start, click Administrative Tools, and then click Print Management.

  2. Do one of the following:

    • Right-click Print Management, and then click Migrate Printers to open the Printer Migration Wizard. Select Export printer queues and printer drivers to a file, and then click Next. Specify the print server to be migrated, and then click Next.

    • In the Print Management tree, under Print Servers, right-click the print server that contains the printer queues to migrate, and then click Export printers to a file to open the Printer Migration Wizard.

  3. Review the list of items to be exported, and then click Next.

  4. In the Export printer data to box, enter the path to the printer settings file to use, or browse to the location where you want to store the file. Click Next to export the printer-specific information for the server to this file.

  5. Verify that the printer settings file is stored on a resource that will be available to the destination server. Optimally, store it on a network share. Click Finish.

The backup file that you create by using either the Printer Migration Wizard or the Printbrm.exe tool inherits the permissions allowed by your user credentials. Only you can access the file if you saved the file directly to a share during the backup file creation process. You must either change the file permissions on the Security tab of the file’s Properties dialog box, or you must perform any restorations or migrations by using that file yourself. If you create the backup file on the computer from which you are running the migration and later copy the file to a share, then file access permissions are inherited from the destination folder.

Then, upgrade the remote print server to Windows Server 2008. After the upgrade is complete, restore the printers on the remote print server.

To restore the printers on the remote print server

  1. From the print server running Windows Server 2008, start Server Manager.

  2. Right-click Roles, and then click Add Roles.

  3. Select Print Services, and then click Next.

  4. Click Next in the two subsequent dialog boxes, and then click Install.

  5. When the installation process is complete, click Close.

  6. Open the Administrative Tools folder, and then click Print Management.

  7. Right-click the Print Management tree, and click Migrate Printers to open the Printer Migration Wizard.

  8. Click Import printer queues and printer drivers from a file, and then click Next.

  9. On the Select the file location page, specify the location of the printer (for example, C:\BACKUP\remoteservername.printerExport), and then click Next.

  10. On the Select import options page, specify the import options you prefer, and then click Next to import the printers.

  11. On the Select a print server page, click Next. (This assumes that you specified This print server as the server that should host the printers.)

  12. On the Select import options page, click Next.

  13. Click Finish.

Review application events with a Printbrm.exe source to determine whether further action is needed.

You can optionally use the following command-line options to migrate print servers to Windows Server 2008.

To migrate print servers to Windows Server 2008 by using a Command Prompt window

  1. Click Start, click All Programs, and then click Accessories.

  2. Right-click Command prompt, and then click Run as administrator.

  3. If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue.

  4. To perform a remote print backup, type

     CD %WINDIR%\System32\Spool\Tools     Printbrm -s \\<sourcecomputername> -b -f <filename>.printerExport

    For <sourcecomputername>, enter the Universal Naming Convention (UNC) of the source computer. For <filename>, enter the file name for the printer settings file. Use the .printerexport or .cab file extensions.

  5. To restore printers, type

    Printbrm -s \\<destinationcomputername> -r -f <filename>.printerExport

    For <sourcecomputername>, enter the Universal Naming Convention (UNC) of the destination computer. For <filename>, enter the file name for the printer settings file. Use the .printerexport or .cab file extensions.

To view the complete syntax for this command, open a Command Prompt window and type Printbrm /?

Upgrading servers with more than one hard drive

If you are using the installation DVD to upgrade a server with two hard drives that is running Windows Server 2003 to Windows Server 2008 R2, the computer will restart during the installation process. When you restart the computer, it continues the installation process from the Windows Server 2008 R2 DVD. However, no upgrade option is available, so when you remove the installation DVD, the computer fails to restart.

By default, the Windows Server 2008 R2 installation DVD will attempt to start the computer from hard disk drive 0 on the computer. If this is a hard disk drive other than drive C (for example, drive E), the installation DVD cannot continue the upgrade process. Remove the other hard disk drive (in this example, drive E) to enable the upgrade process to finish successfully.

Blue screen appears intermittently after upgrading

After upgrading an HP BL460C server to Windows Server 2008 R2, the server may intermittently display a blue screen.

Verify the following:

  • You have the latest version of the HpCISSs2.sys driver installed on the server. Earlier versions of this driver may cause issues when running on Windows Server 2008 R2. The driver is available in the HP Support Pack, which is available from the Hewlett-Packard Web site.

  • The antivirus software on the server is the most current version. Older versions may not be compatible with Windows Server 2008 R2.

If the blue screen continues to appear after you upgrade the driver and antivirus software on the server, consider the following:

  • Enable a special pool. For more information, see article 188831, "How to use the special pool feature to isolate pool damage," in the Microsoft Knowledge Base (http://go.microsoft.com/fwlink/?LinkId=111004).

  • Obtain a new memory dump.

UDDI Services

If you install Windows Server 2008 R2 on a computer running Windows Server 2003 that has Internet Information Services (IIS) but not UDDI Services installed, subsequent installation of UDDI Services will succeed, but UDDI Services will not function.

To avoid this issue, complete the installation of Windows Server 2008 R2, and then reinstall IIS 7.0 before attempting to install UDDI Services.

Windows Firewall

Although the default behavior for Windows Server 2008 R2 is that Windows Firewall is turned on, if you upgrade a Windows Server 2003 computer that had Windows Firewall turned off to Windows Server 2008 R2, the firewall will remain off after the upgrade. To turn on the firewall: from the Control Panel in Windows Server 2008, click Security, and then click Firewall.

¿Te ha resultado útil?
(Caracteres restantes: 1500)
Gracias por sus comentarios

Adiciones de comunidad

AGREGAR
Mostrar:
© 2014 Microsoft