skip to content »

Mirdatinga ru

mirdatinga ru-40

WSUS servers can be configured to use Windows® Internal Database, the database software that is included with WSUS, or the full version of SQL Server.

Or, you can use Windows Server Migration Tools to migrate all local users and groups (including the WSUS Administrators and WSUS Reporters local security groups) from the source server to the destination server.Use your preferred method (Windows Server Migration Tools, Windows Explorer, Xcopy, or Robocopy, for example) to copy WSUS update binaries in the WSUS folder from the source server to the destination server.If you decide to use Windows Server Migration Tools to migrate WSUS update binaries to a destination server that is running Windows Server 2008 R2, see Appendix B: Migrate WSUS Update Binaries from the Source Server to the Destination Server Using Windows Server Migration Tools.After you restore a SQL Server 2005 database to SQL Server 2008, the database becomes available immediately and is then automatically upgraded.The WSUS server identity on the destination server must be changed.For an overview of backup and command-line syntax, see the following articles on SQL Server Tech Center: SQL Server Management Studio must be run with elevated administrator permissions throughout this guide.

To run SQL Server Management Studio with elevated administrator permissions in Windows Server 2008 and Windows Server 2008 R2, click Start, point to All Programs, point to SQL Server 2005 or SQL Server 2008, right-click SQL Server Management Studio, and then click Run As Administrator.

Refer to the settings that you recorded on Appendix A: Migration Data Collection Worksheet.

Complete the following tasks to apply any security settings that you were using on the source server to the destination server.

If the source and destination servers are in different domains, the destination server must be able to contact a global catalog server for the forest in which the source domain user accounts are located.

If the source server is a domain member server, and the destination server is a domain controller: Imported local users are elevated to domain users, and imported local groups become Domain Local groups on the destination server.

Performing this step guarantees that WSUS-managed clients are not affected during the migration process.