Подготовка серверов Windows для поддержки Configuration Manager Prepare Windows Servers to support Configuration Manager

Область применения: Configuration Manager (Current Branch) Applies to: Configuration Manager (current branch)

Прежде чем использовать компьютер Windows в качестве сервера системы сайта для Configuration Manager, убедитесь, что он соответствует требованиям, предъявляемым для применения в качестве сервера сайта или сервера системы сайта. Before you can use a Windows computer as a site system server for Configuration Manager, the computer must meet the prerequisites for its intended use as a site server or site system server.

В эти требования часто входит одна или несколько функций или ролей Windows, которые включаются с помощью диспетчера серверов на компьютере. These prerequisites often include one or more Windows features or roles, which are enabled by using the computers Server Manager.

Так как способ включения функций и ролей Windows в версиях операционной системы отличается, см. документацию со сведениями о настройке используемой версии операционной системы. Because the method to enable Windows features and roles differs among OS versions, refer to the documentation for your OS version for detailed information about how to set up the OS that you use.

Этот раздел содержит обзор типов конфигураций Windows, которые необходимы для поддержки систем сайта Configuration Manager. The information in this article provides an overview of the types of Windows configurations that are required to support Configuration Manager site systems. Подробные сведения о конфигурациях для отдельных ролей системы сайта см. в статье Предварительные требования для сайта и системы сайта в System Center Configuration Manager. For configuration details for specific site system roles, see Site and site system prerequisites.

Функции и роли Windows Windows features and roles

При настройке функций и ролей Windows на компьютере может потребоваться его перезагрузить, чтобы завершить эту настройку. When you set up Windows features and roles on a computer, you might be required to reboot the computer to complete that configuration. Перед установкой сайта или сервера системы сайта Configuration Manager мы рекомендуем определить компьютеры, на которых будут располагаться конкретные роли системы сайта. Therefore, it’s a good idea to identify computers that will host specific site system roles before you install a Configuration Manager site or site system server.

Функции Features

Следующие функции Windows необходимы для определенных серверов системы сайта. Их следует настроить перед установкой роли системы сайта на данном компьютере. The following Windows features are required on certain site system servers and should be set up before you install a site system role on that computer.

.NET Framework. Включает: .NET Framework: Including

• ASP.NET ASP.NET
• Активация по протоколам HTTP HTTP Activation
• Активация по отличным от HTTP протоколам Non-HTTP Activation
• Службы Windows Communication Foundation Windows Communication Foundation (WCF) Services

Разным ролям системы сайта требуются разные версии платформы .NET Framework. Different site system roles require different versions of .NET Framework.

Платформа .NET Framework 4.0 и более поздних версий не является обратно совместимой, чтобы заменить платформу 3.5 и более ранних версий, поэтому если требуется использовать разные версии платформы, планируйте внедрить каждую из них на одном компьютере. Because .NET Framework 4.0 and later isn’t backward compatible to replace 3.5 and earlier versions, when different versions are listed as required, plan to enable each version on the same computer.

Фоновая интеллектуальная служба передачи (BITS) . Точкам управления требуется BITS (и автоматически выбранные параметры) для поддержки связи с управляемыми устройствами. Background Intelligent Transfer Services (BITS): Management points require BITS (and automatically selected options) to support communication with managed devices.

BranchCache. Точки распространения можно настроить с помощью BranchCache для поддержки клиентов, использующих BranchCache. BranchCache: Distribution points can be set up with BranchCache to support clients that use BranchCache.

Дедупликация данных. Точки распространения можно настроить на использование преимуществ дедупликации данных. Data Deduplication: Distribution points can be set up with and benefit from data deduplication.

Удаленное разностное сжатие (RDC) . Каждому компьютеру, на котором размещен сервер сайта или точка распространения, требуется RDC. Remote Differential Compression (RDC): Each computer that hosts a site server or a distribution point requires RDC. RDC используется для формирования подписей пакетов и сравнения подписей. RDC is used to generate package signatures and perform signature comparisons.

Роли Roles

Следующие роли Windows требуются для поддержки определенных функциональных возможностей, таких как развертывания обновлений программного обеспечения и операционных систем, а службы IIS требуются для наиболее типичных ролей системы сайта. The following Windows roles are required to support specific functionality, like software updates and OS deployments, while IIS is required by the most common site system roles.

Служба регистрации сертификатов для сетевых устройств (в составе служб сертификатов Active Directory) Эта роль Windows является необходимым условием для использования профилей сертификатов в Configuration Manager. Network Device Enrollment Service (under Active Directory Certificate Services): This Windows role is a prerequisite to use certificate profiles in Configuration Manager.

Веб-сервер (IIS) . Включает: Web server (IIS): Including:

• Общие функции HTTP Common HTTP Features
  — Перенаправление HTTP HTTP Redirection
• Разработка приложения Application Development
  — Расширяемость .NET .NET Extensibility
  — ASP.NET ASP.NET
  — Расширения ISAPI ISAPI Extensions
  — Фильтры ISAPI ISAPI Filters
• Средства управления Management Tools
  — Совместимость управления IIS 6 IIS 6 Management Compatibility
  — Совместимость метабазы IIS 6 IIS 6 Metabase Compatibility
  — Совместимость с инструментарием управления Windows IIS 6 IIS 6 Windows Management Instrumentation (WMI) Compatibility
• Безопасность Security
  — Фильтрация запросов Request Filtering
  — Проверка подлинности Windows Windows Authentication

Следующие роли системы сайта используют одну или несколько указанных конфигураций IIS: The following site system roles use one or more of the listed IIS configurations:

• Тточка веб-службы каталога приложений Application Catalog web service point
• Точка веб-сайта каталога приложений Application Catalog website point
• Точка распространения Distribution point
• Точка регистрации Enrollment point
• Прокси-точка регистрации. Enrollment proxy point
• Резервная точка состояния Fallback status point
• Точка управления Management point
• Точка обновления программного обеспечения Software update point
• точка миграции состояния, State migration point

Минимальная необходимая версия служб IIS представляет собой версию, входящую в состав операционной системы сервера сайта. The minimum version of IIS that’s required is the version that’s supplied with the OS of the site server.

Помимо этих конфигураций IIS может потребоваться настроить фильтрацию запросов служб IIS для точек распространения. In addition to these IIS configurations, you might need to set up IIS Request Filtering for distribution points.

Службы развертывания Windows. Эта роль используется при развертывании операционной системы. Windows Deployment Services: This role is used with OS deployment.

Windows Server Update Services. Эта роль необходима для обновления программного обеспечения. Windows Server Update Services: This role is required for software updates.

Фильтрация запросов служб IIS для точек распространения IIS request filtering for distribution points

По умолчанию службы IIS используют фильтрацию запросов, чтобы заблокировать доступ к различным расширениям имен файлов и расположениям папок для подключений по протоколу HTTP или HTTPS. By default, IIS uses request filtering to block several file name extensions and folder locations from access by HTTP or HTTPS communication. На точке распространения это не позволяет клиентам скачивать пакеты, содержащие заблокированные расширения или папки. On a distribution point, this prevents clients from downloading packages that have blocked extensions or folder locations.

Если исходные файлы пакета содержат расширения, заблокированные в службах IIS конфигурацией фильтрации запросов, необходимо настроить фильтрацию запросов, чтобы разрешить их. When your package source files have extensions that are blocked in IIS by your request filtering configuration, you must set up request filtering to allow them. Это можно сделать, изменив функцию фильтрации запроса в диспетчере IIS на компьютерах точек распространения. This is done by editing the request filtering feature in the IIS Manager on your distribution point computers.

Кроме того, Configuration Manager использует перечисленные ниже расширения имен файлов для пакетов и приложений. Additionally, the following file name extensions are used by Configuration Manager for packages and applications. Убедитесь, что конфигурации фильтрации запросов не блокируют эти расширения имен файлов: Make sure that your request filtering configurations don’t block these file extensions:

Например, в пакете развертывания программного обеспечения могут содержаться исходные файлы, включающие папку с именем bin или файл с расширением MDB. For example, source files for a software deployment might include a folder named bin or have a file that has the .mdb file name extension.

По умолчанию фильтрация запросов IIS блокирует доступ к этим элементам (bin блокируется как скрытый сегмент, а MDB блокируется как расширение имени файла). By default, IIS request filtering blocks access to these elements (bin is blocked as a Hidden Segment and .mdb is blocked as a file name extension).

Если на точке распространения используется конфигурация IIS по умолчанию, клиенты, использующие службу BITS, не смогут загрузить это развертывание программного обеспечения с точки распространения и отображают состояние ожидания содержимого. When you use the default IIS configuration on a distribution point, clients that use BITS fail to download this software deployment from the distribution point and indicate that they’re waiting for content.

Чтобы дать клиентам возможность скачать это содержимое, на каждой соответствующей точке распространения измените значение Фильтрация запросов в диспетчере IIS для разрешения доступа к расширениям файлов и папкам, содержащимся в развертываемых пакетах и приложениях. To let the clients download this content, on each applicable distribution point, edit Request Filtering in IIS Manager to allow access to the file extensions and folders that are in the packages and applications that you deploy.

Правки к фильтру запроса повышают уязвимость компьютера. Edits to the request filter can increase the attack surface of the computer.

• Изменения, вносимые на уровне сервера, применяются ко всем веб-сайтам на сервере. Edits that you make at the server level apply to all websites on the server.
  • Изменения, вносимые для отдельного веб-сайта, применяются только к этому веб-сайту. Edits that you make to individual websites apply to only that website.

В целях безопасности рекомендуется использовать Configuration Manager на выделенном веб-сервере. The security best practice is to run Configuration Manager on a dedicated web server. Если на веб-сервере требуется запускать другие приложения, используйте для Configuration Manager специальный веб-сайт. If you must run other applications on the web server, use a custom website for Configuration Manager. Дополнительные сведения см. в статье Веб-сайты для серверов системы сайта в System Center Configuration Manager. For information, see Websites for site system servers.

Команды HTTP HTTP verbs

Точки управления. Чтобы обеспечить возможность связи клиентов с точкой управления, убедитесь, что на сервере точки управления разрешены следующие HTTP-команды: Management points: To ensure that clients can successfully communicate with a management point, on the management point server ensure the following HTTP verbs are allowed:

• GET GET
• POST POST
• CCM_POST CCM_POST
• HEAD HEAD
• PROPFIND PROPFIND

Точки распространения. Для точек распространения необходимо разрешить следующие HTTP-команды: Distribution points: Distribution points require that the following HTTP verbs as allowed:

• GET GET
• HEAD HEAD
• PROPFIND PROPFIND

Дополнительные сведения см. в статье Configure Request Filtering in IIS (Настройка фильтрации запросов в IIS). For more information, see Configure request filtering in IIS.

Server Manager

Applies To: Windows Server (Semi-Annual Channel), Windows Server 2016, Windows Server 2012 R2, Windows Server 2012

Server Manager is a management console in Windows Server that helps IT professionals provision and manage both local and remote Windows-based servers from their desktops, without requiring either physical access to servers, or the need to enable Remote Desktop protocol (rdP) connections to each server. Although Server Manager is available in Windows Server 2008 R2 and Windows Server 2008, Server Manager was updated in Windows Server 2012 to support remote, multi-server management, and help increase the number of servers an administrator can manage.

In our tests, Server Manager in Windows Server 2016, Windows Server 2012 R2, and Windows Server 2012 can be used to manage up to 100 servers, depending on the workloads that the servers are running. The number of servers that you can manage by using a single Server Manager console can vary depending on the amount of data that you request from managed servers, and hardware and network resources available to the computer running Server Manager. As the amount of data you want to display approaches that computer’s resource capacity, you can experience slow responses from Server Manager, and delays in the completion of refreshes. To help increase the number of servers that you can manage by using Server Manager, we recommend limiting the event data that Server Manager gets from your managed servers, by using settings in the Configure Event Data dialog box. Configure Event Data can be opened from the Tasks menu in the Events tile. If you need to manage an enterprise-level number of servers in your organization, we recommend evaluating products in the Microsoft System Center suite.

This topic and its subtopics provide information about how to use features in the Server Manager console. This topic contains the following sections.

Review initial considerations and system requirements

The following sections list some initial considerations that you need to review, as well as hardware and software requirements for Server Manager.

Hardware requirements

Server Manager is installed by default with all editions of Windows Server 2016. No additional hardware requirements exist for Server Manager.

Software and configuration requirements

Server Manager is installed by default with all editions of Windows Server 2016. You can use Server Manager in Windows Server 2016 to manage Server Core installation options of Windows Server 2016, Windows Server 2012 , and Windows Server 2008 R2 that are running on remote computers. Server Manager does run on the Server Core installation option of Windows Server 2016.

Server Manager runs in the Minimal Server Graphical Interface; that is, when the Server Graphical Shell feature is not installed. The Server Graphical Shell feature is not installed by default on Windows Server 2016. If you are not running Server Graphical Shell, the Server Manager console runs, but some applications or tools available from the console are not available. Internet browsers cannot run without Server Graphical Shell, so webpages and applications such as HTML help (The mmc F1 help, for example) cannot be opened. You cannot open dialog boxes for configuring Windows automatic updating and feedback when Server Graphical Shell is not installed; commands that open these dialog boxes in the Server Manager console are redirected to run sconfig.cmd.

To manage servers that are running Windows Server releases older than Windows Server 2016, install the following software and updates to make the older releases of Windows Server manageable by using Server Manager in Windows Server 2016.

Operating System	Required Software
Windows Server 2012 R2 or Windows Server 2012	— .NET Framework 4.6 — Windows Management Framework 5.0. The Windows Management Framework 5.0 download package updates Windows Management Instrumentation (WMI) providers on Windows Server 2012 R2 and Windows Server 2012 . The updated WMI providers let Server Manager collect information about roles and features that are installed on the managed servers. Until the update is applied, servers that are running Windows Server 2012 R2 or Windows Server 2012 have a manageability status of Not accessible. — The performance update associated with Knowledge Base article 2682011 is no longer necessary on servers that are running Windows Server 2012 R2 or Windows Server 2012 .
Windows Server 2008 R2	— .NET Framework 4.5 — Windows Management Framework 4.0. The Windows Management Framework 4.0 download package updates Windows Management Instrumentation (WMI) providers on Windows Server 2008 R2 . The updated WMI providers let Server Manager collect information about roles and features that are installed on the managed servers. Until the update is applied, servers that are running Windows Server 2008 R2 have a manageability status of Not accessible. — The performance update associated with Knowledge Base article 2682011 lets Server Manager collect performance data from Windows Server 2008 R2 .
Windows Server 2008	— .NET Framework 4 — Windows Management Framework 3.0 The Windows Management Framework 3.0 download package updates Windows Management Instrumentation (WMI) providers on Windows Server 2008 . The updated WMI providers let Server Manager collect information about roles and features that are installed on the managed servers. Until the update is applied, servers that are running Windows Server 2008 have a manageability status of Not accessible — verify earlier versions run Windows Management Framework 3.0. — The performance update associated with Knowledge Base article 2682011 lets Server Manager collect performance data from Windows Server 2008 .

Manage remote computers from a client computer

The Server Manager console is included with Remote Server Administration Tools for Windows 10. Note that when Remote Server Administration Tools is installed on a client computer, you cannot manage the local computer by using Server Manager; Server Manager cannot be used to manage computers or devices that are running a Windows client operating system. You can only use Server Manager to manage Windows-based servers.

Server Manager Source Operating System	Targeted at Windows Server 2016	Targeted at Windows Server 2012 R2	Targeted at Windows Server 2012	Targeted at Windows Server 2008 R2 or Windows Server 2008	Targeted at Windows Server 2003	Targeted at Windows 10 Enterprise multi-session on Windows Virtual Desktop (WVD)
Windows 10 or Windows Server 2016	Full support	Full support	Full support	After Software and configuration requirements are satisfied, can perform most management tasks, but no role or feature installation or uninstallation	Not supported	Not supported
Windows 8.1 or Windows Server 2012 R2	Not supported	Full support	Full support	After Software and configuration requirements are satisfied, can perform most management tasks, but no role or feature installation or uninstallation	Limited support; online and offline status only	Not supported
Windows 8 or Windows Server 2012	Not supported	Not supported	Full support	After Software and configuration requirements are satisfied, can perform most management tasks, but no role or feature installation or uninstallation	Limited support; online and offline status only	Not supported

To start Server Manager on a client computer

Follow instructions in Remote Server Administration Tools to install Remote Server Administration Tools for Windows 10.

On the start screen, click Server Manager. The Server Manager tile is available after you install Remote Server Administration Tools.

if neither the Administrative Tools nor the Server Manager tiles are displayed on the start screen after installing Remote Server Administration Tools, and searching for Server Manager on the start screen does not display results, verify that the Show administrative tools setting is turned on. To view this setting, hover the mouse cursor over the upper right corner of the start screen, and then click Settings. If Show administrative tools is turned off, turn the setting on to display tools that you have installed as part of Remote Server Administration Tools.

for more information about running Remote Server Administration Tools for Windows 10 to manage remote servers, see Remote Server Administration Tools on the TechNet Wiki.

Configure remote management on servers that you want to manage

By default, Server Manager and Windows PowerShell remote management is enabled in Windows Server 2016.

To perform management tasks on remote servers by using Server Manager, remote servers that you want to manage must be configured to allow remote management by using Server Manager and Windows PowerShell. If remote management has been disabled on Windows Server 2012 R2 or Windows Server 2012 , and you want to enable it again, perform the following steps.

To configure Server Manager remote management on Windows Server 2012 R2 or Windows Server 2012 by using the Windows interface

The settings that are controlled by the Configure remote Management dialog box do not affect parts of Server Manager that use DCOM for remote communications.

Do one of the following to open Server Manager if it is not already open.

On the Windows taskbar, click the Server Manager button.

On the start screen, click Server Manager.

In the Properties area of the Local Servers page, click the hyperlinked value for the remote management property.

Do one of the following, and then click OK.

To prevent this computer from being managed remotely by using Server Manager (or Windows PowerShell if it is installed), clear the Enable remote management of this server from other computers check box.

To let this computer be managed remotely by using Server Manager or Windows PowerShell, select Enable remote management of this server from other computers.

To enable Server Manager remote management on Windows Server 2012 R2 or Windows Server 2012 by using Windows PowerShell

Do one of the following.

To run Windows PowerShell as an administrator from the start screen, right-click the Windows PowerShell tile, and then click Run as Administrator.

To run Windows PowerShell as an administrator from the desktop, right-click the Windows PowerShell shortcut in the taskbar, and then click Run as Administrator.

type the following, and then press Enter to enable all required firewall rule exceptions.

Configure-SMremoting.exe -Enable

This command also works in a command prompt that has been opened with elevated user rights (Run as Administrator).

if enabling remote management fails, see about_remote_Troubleshooting on Microsoft TechNet for troubleshooting tips and best practices.

To enable Server Manager and Windows PowerShell remote management on older operating systems

Do one of the following.

To enable remote management on servers that are running Windows Server 2008 R2 , see remote Management with Server Manager in the Windows Server 2008 R2 help.

To enable remote management on servers that are running Windows Server 2008 , see Enable and Use remote Commands in Windows PowerShell.

Tasks that you can perform in Server Manager

Server Manager makes server administration more efficient by allowing administrators to do tasks in the following table by using a single tool. In Windows Server 2012 R2 and Windows Server 2012 , both standard users of a server and members of the Administrators group can perform management tasks in Server Manager, but by default, standard users are prevented from performing some tasks, as shown in the following table.

Administrators can use two Windows PowerShell cmdlets in the Server Manager cmdlet module, Enable-ServerManagerStandardUserremoting and Disable-ServerManagerStandardUserremoting, to further control standard user access to some additional data. The Enable-ServerManagerStandardUserremoting cmdlet can provide one or more standard, non-Administrator users access to event, service, performance counter, and role and feature inventory data.

Server Manager cannot be used to manage a newer release of the Windows Server operating system. Server Manager running on Windows Server 2012 or Windows 8 cannot be used to manage servers that are running Windows Server 2012 R2 .

Task Description	Administrators (including the built-in Administrator account)	Standard Server Users
add remote servers to a pool of servers that Server Manager can be used to manage.	Yes	No
create and edit custom groups of servers, such as servers that are in a specific geographic location or serve a specific purpose.	Yes	Yes
Install or uninstall roles, role services, and features on the local or on remote servers that are running Windows Server 2012 R2 or Windows Server 2012 . For definitions of roles, role services, and features, see Roles, Role Services, and Features.	Yes	No
View and make changes to server roles and features that are installed on either local or remote servers. Note: In Server Manager, role and feature data is displayed in the base language of the system, also called the system default GUI language, or the language selected during installation of the operating system.	Yes	Standard users can view and manage roles and features, and perform tasks such as viewing role events, but cannot add or remove role services.
start management tools such as Windows PowerShell or mmc snap-ins. You can start a Windows PowerShell session targeted at a remote server by right-clicking the server in the Servers tile, and then clicking Windows PowerShell. You can start mmc snap-ins from the Tools menu of the Server Manager console, and then point the mmc toward a remote computer after the snap-in is open.	Yes	Yes
Manage remote servers with different credentials by right-clicking a server in the Servers tile, and then clicking Manage As. You can use Manage As for general server and File and Storage Services management tasks.	Yes	No
Perform management tasks associated with the operational lifecycle of servers, such as starting or stopping services; and start other tools that allow you to configure a server’s network settings, users and groups, and Remote Desktop connections.	Yes	Standard users cannot start or stop services. They can change the local server’s name, workgroup, or domain membership and Remote Desktop settings, but are prompted by User Account Control to provide Administrator credentials before they can complete these tasks. They cannot change remote management settings.
Perform management tasks associated with the operational lifecycle of roles that are installed on servers, including scanning roles for compliance with best practices.	Yes	Standard users cannot run Best Practices Analyzer scans.
Determine server status, identify critical events, and analyze and troubleshoot configuration issues or failures.	Yes	Yes
Customize the events, performance data, services, and Best Practices Analyzer results about which you want to be alerted on the Server Manager dashboard.	Yes	Yes
Restart servers.	Yes	No
Refresh data that is displayed in the Server Manager console about managed servers.	Yes	No

Server Manager cannot be used to add roles and features to servers that are running Windows Server 2008 R2 or Windows Server 2008 .

Start Server Manager

Server Manager starts automatically by default on servers that are running Windows Server 2016 when a member of the Administrators group logs on to a server. If you close Server Manager, restart it in one of the following ways. This section also contains steps for changing the default behavior, and preventing Server Manager from starting automatically.

To start Server Manager from the start screen

• On the Windows start screen, click the Server Manager tile.

To start Server Manager from the Windows desktop

• On the Windows taskbar, click Server Manager.

To prevent Server Manager from starting automatically

In the Server Manager console, on the Manage menu, click Server Manager Properties.

In the Server Manager Properties dialog box, fill the check box for Do not start Server Manager automatically at logon. Click OK.

Alternatively, you can prevent Server Manager from starting automatically by enabling the Group Policy setting, Do not start Server Manager automatically at logon. The path to this policy setting, in the Local Group Policy editor console, is computer Configuration\Administrative Templates\System\Server Manager.

Restart remote servers

You can restart a remote server from the Servers tile of a role or group page in Server Manager.

Restarting a remote server forces the server to restart, even if users are still logged on to the remote server, and even if programs with unsaved data are still open. This behavior is different from shutting down or restarting the local computer, on which you would be prompted to save unsaved program data, and verify that you wanted to force logged-on users to log off. Be sure that you can force other users to log off of remote servers, and that you can discard unsaved data in programs that are running on the remote servers.

if an automatic refresh occurs in Server Manager while a managed server is shutting down and restarting, refresh and manageability status errors can occur for the managed server, because Server Manager cannot connect to the remote server until it is finished restarting.

To restart remote servers in Server Manager

Open a role or server group home page in Server Manager.

select one or more remote servers that you have added to Server Manager. Press and hold Ctrl as you click to select multiple servers at one time. For more information about how to add servers to the Server Manager server pool, see add Servers to Server Manager.

Right-click selected servers, and then click Restart Server.

Export Server Manager settings to other computers

In Server Manager, your list of managed servers, changes to Server Manager console settings, and custom groups that you have created are stored in the following two files. You can reuse these settings on other computers that are running the same release of Server Manager (or Windows 10 with Remote Server Administration Tools installed). Remote Server Administration Tools must be running on Windows client-based computers to export Server Manager settings to those computers.

• Manage As (or alternate) credentials for servers in your server pool are not stored in the roaming profile. Server Manager users must add them on each computer from which they want to manage.
• The network share roaming profile is not created until a user logs on to the network, and then logs off for the first time. The Serverlist.xml file is created at this time.

You can export Server Manager settings, make Server Manager settings portable, or use them on other computers in one of the following two ways.

To export settings to another domain-joined computer, configure the Server Manager user to have a roaming profile in active directory Users and computers. You must be a Domain Administrator to change user properties in active directory Users and computers.

To export settings to another computer in a workgroup, copy the preceding two files to the same location on the computer from which you want to manage by using Server Manager.

To export Server Manager settings to other domain-joined computers

In active directory Users and computers, open the Properties dialog box for a Server Manager user.

On the Profile tab, add a path to a network share to store the user’s profile.

Do one of the following.

On U.S. English (en-us) builds, changes to the Serverlist.xml file are automatically saved to the profile. Go on to the next step.

On other builds, copy the following two files from the computer that is running Server Manager to the network share that is part of the user’s roaming profile.

Click OK to save your changes and close the Properties dialog box.

To export Server Manager settings to computers in workgroups

On a computer from which you want to manage remote servers, overwrite the following two files with the same files from another computer that is running Server Manager, and that has the settings you want.