Exportaţi (0) Imprimaţi
Extindeţi tot
EN
Acest conţinut nu este disponibil în limba dvs., dar puteţi consulta aici versiunea în limba engleză.
21 din 41 a(u) evaluat conţinutul ca util - Evaluare subiect

Server Manager Step-by-Step Guide: Scenarios

Applies To: Windows Server 2008

Server Manager is a new tool available with Windows Server® 2008 that guides information technology administrators through the process of installing, configuring, and managing server roles and features that are part of Windows Server 2008.

This step-by-step guide provides an overview of Server Manager and walkthroughs of several common scenarios for using Server Manager in your enterprise, focusing on new and enhanced features of Server Manager. This guide helps you learn about how Server Manager functions as a server role deployment, decommissioning, and management tool. The guide also describes how Server Manager helps improve productivity, so IT pros can spend less time deploying, managing, and maintaining their infrastructures, and spend more time using Windows Server 2008 software packages to add business value.

The scenarios described in this step-by-step guide include initial server configuration tasks as well as deployment, management, and removal of server roles and features.

This step-by-step guide benefits:

  • An IT administrator, planner, or analyst evaluating Windows Server 2008.

  • An enterprise IT planner or designer.

  • An early adopter of Windows Server 2008.

  • An IT architect responsible for computer management and security throughout your organization.

  • An IT operations engineer who is responsible for the day-to-day management and troubleshooting of networks, servers, operating systems, or applications.

  • An IT operations manager who is accountable for network and server management, IT hardware and software budgets, and technical decisions.

Server Manager makes server administration more efficient by allowing administrators to use a single tool to do the following:

  • View and make changes to server roles and features installed on the server.

  • Perform management tasks associated with the operational lifecycle of the server, such as starting or stopping services, and managing local user accounts.

  • Perform management tasks associated with the operational lifecycle of roles, role services, and features installed on the server.

  • Determine server status, identify critical events, and analyze and troubleshoot configuration issues or failures.

Before using Server Manager, it is recommended that you familiarize yourself with the functions, terminology, requirements, and day-to-day management tasks of any roles you plan to install on your server. For more detailed information about server roles, see the Windows Server TechCenter (http://go.microsoft.com/fwlink/?LinkId=48541).

Server Manager is installed by default as part of the Windows Server 2008 setup process. To use Server Manager, you must be logged on to the computer as a member of the Administrators group on the local computer.

The following scenarios guide you through several common uses for Server Manager and its related technologies Initial Configuration Tasks and Remote Server Administration Tools.

After Windows Server 2008 Setup is finished, an administrator logs on to the server for the first time, and the Initial Configuration Tasks window automatically opens. The administrator completes configuration of the new server by using commands in the Initial Configuration Tasks window.

noteNote
If you accidentally close Initial Configuration Tasks, click Start, and then click Run. Type oobe in the Open text box, and then click OK or press ENTER.

  1. In the Initial Configuration Tasks window, in the Provide Computer Information area, click Provide computer name and domain.

  2. On the Computer Name tab of the System Properties dialog box, click Change to change the computer name.

  3. In the Computer Name/Domain Changes dialog box, type a name for this computer, and provide the name of a domain or workgroup to which you want to join the computer. Click OK.

  4. For the computer name and domain changes to take effect, restart the computer. You can wait to do this until after you have completed your work in Initial Configuration Tasks.

  5. Configure network settings for this server, such as how the server obtains an IP address. For example, you can configure settings that determine how the IP address is assigned. In the Initial Configuration Tasks window, in the Provide Computer Information area, click Configure networking.

  6. In the Network Connections window, click File, and then click New Incoming Connection to create a new network connection for this computer.

  7. Configure Enable automatic updating and feedback according to your organization’s policies.

  8. Configure the server’s use of Remote Desktop according to your organization’s policies.

  9. If you do not want to open Initial Configuration Tasks every time an administrator logs on to the computer, select Do not show this window at logon, and then close the Initial Configuration Tasks window.

Although initial configuration tasks have been completed and the Initial Configuration Tasks window is now closed, an administrator has decided to enable automatic updating and feedback on the computer running Windows Server 2008. The administrator uses Server Manager to modify settings, instead of running Initial Configuration Tasks once again. The administrator enrolls the server in the Customer Experience Improvement Program (CEIP), and turns on automatic updating and Windows Error Reporting.

  1. Click Start. Point to Administrative Tools, and then click Server Manager.

  2. Expand the Resources and Support area, if it is not already open.

  3. Click Configure CEIP to open the Customer Experience Improvement Program Configuration dialog box.

  4. Select Yes, I want to participate in the CEIP. Click OK.

  1. If Server Manager is not already open, open Server Manager by clicking Start, pointing to Administrative Tools, and then clicking Server Manager.

  2. Expand the Server Summary area, if it is not already open.

  3. Expand the Security Information area, if it is not already open. Click Configure Updates.

  4. In the Windows Update dialog box, select one of the following:

    • Click Have Windows install updates automatically to download and install updates as they become available. This is recommended.

    • Click Let me choose to open the Change Settings window, which allows you to turn off updates, or to select how updates are downloaded and installed on the server, if you want automatic updates turned on.

  5. If you opened the Change Settings window by clicking Let me choose, when you are done making changes, click OK.

  1. Open Server Manager by clicking Start, pointing to Administrative Tools, and then clicking Server Manager.

  2. Expand the Resources and Support area, if it is not already open.

  3. Click Turn on Windows Error Reporting.

  4. In the Windows Error Reporting Configuration dialog box, select one of the following options:

    • Yes, automatically send detailed reports.

    • Yes, automatically send summary reports.

    The other settings—Ask me about sending reports every time an error occurs, and I don't want to participate, and don't ask me again—disable Windows Error Reporting. Ask me about sending reports every time an error occurs prompts you to report errors only as they occur.

  5. Click OK.

A company has just purchased a new server. The new computer must run Terminal Services to provide centralized access to individual applications without the necessity of providing Remote Desktop access to each employee.

The administrator performs the following steps to add and configure Terminal Services.

The system administrator installs the Terminal Services role on the new computer.

  1. If Server Manager is not already open, open Server Manager by clicking Start, pointing to Administrative Tools, and then clicking Server Manager.

  2. Add Terminal Services by using the Add Roles Wizard in Server Manager. Select the role services Terminal Server and TS Web Access on the Select Role Services page of the Add Roles Wizard.

    noteNote
    The TS Web Access role service depends on Web Server (IIS) and Windows System Resource Manager (WSRM). Server Manager prompts you to install IIS and WSRM if they are not already installed on the computer.

  3. The Terminal Services installation process requires an administrator to specify several configuration options. Complete the configuration pages of the Add Roles Wizard based on what is most appropriate for your organization. For more information about configuring Terminal Services, and detailed step-by-step guides, see the Terminal Services page on the Windows Server TechCenter (http://go.microsoft.com/fwlink/?LinkId=48555).

The administrator opens the Terminal Services snap-ins and performs Terminal Services management tasks in the Server Manager window.

  1. If Server Manager is not already open, open Server Manager by clicking Start, pointing to Administrative Tools, and then clicking Server Manager.

  2. In the hierarchy pane, expand Roles, and then expand Terminal Services.

  3. If Terminal Services is installed, but Terminal Services snap-ins and management tools do not appear in the hierarchy pane, close and then reopen Server Manager.

  4. Open the Terminal Services Configuration and then the Terminal Services Manager snap-ins by selecting their objects in the hierarchy pane.

  5. On the role home page for Terminal Services, open the Summary area and the System Services area, if they are not already open.

  6. In the System Services area, click Stop and then Restart to stop and then restart the Terminal Services service.

  7. In the Server Manager hierarchy pane, expand Diagnostics.

  8. Expand Event Viewer, expand Custom Views, and then expand Server Roles.

  9. If Terminal Services does not appear as a child object of Server Roles, press F5 to refresh the Server Manager console. If Terminal Services still fails to appear, close and then reopen Server Manager.

  10. To check for new event messages, press F5 or right-click the Event Viewer node, and then click Refresh. Check for critical, warning, or informational events for Terminal Services, view event properties, and change filter preferences for events.

After several months, the system administrator wants to install Terminal Services on a more powerful computer, and remove Terminal Services completely from the server on which it currently is running.

  1. If Server Manager is not already open, open Server Manager by clicking Start, pointing to Administrative Tools, and then clicking Server Manager.

  2. Open the Roles Summary area, if it is not already open.

  3. Click Remove roles.

  4. On the Remove Server Roles page of the Remove Roles Wizard, clear the check box for Terminal Services. Click Next.

  5. After confirming that you want to remove Terminal Services, on the Confirm Removal Selections page, click Remove.

An administrator is running the Server Core installation option of Windows Server 2008. The administrator installs the Print Services role on this server. After that, the administrator wants to manage the server remotely from another computer that is running a full installation of Windows Server 2008.

To manage the Print Services role remotely from the computer running the full installation of Windows Server 2008, the administrator installs Remote Server Administration Tools.

  1. Open Server Manager by clicking Start, pointing to Administrative Tools, and then clicking Server Manager. In the Features section of the Server Manager home page, click Add features.

  2. On the Select Features page of the Add Features Wizard, expand Remote Server Administration Tools.

  3. Expand Role Administration Tools, and then select Print Services Tools.

    noteNote
    Installing Remote Server Administration Tools does not install any roles, role services, or features on a computer. For each role, role service, or feature you select within Remote Server Administration Tools, you are installing only management tools and snap-ins that allow you to perform administration tasks for specified roles, role services, or features installed on other computers.

  4. Click Next, and then click Install.

  5. When installation is complete, close the wizard.

To manage the remote print server and make sure it is discoverable on the network, the administrator restarts the print spooler service on the computer running the Server Core installation of Windows Server 2008. To restart the spooler services on the computer running the Print Services role, type the commands net stop spooler, followed by net start spooler, at the command prompt.

After restarting the spooler service, the administrator is ready to manage Print Services remotely from the computer running the full installation of Windows Server 2008.

  1. Open the Print Management snap-in by clicking Start, pointing to Administrative Tools, and then clicking Print Management.

  2. Right-click the Print Management node at the top of the hierarchy pane, and then click Add/Remove Servers.

  3. Add or browse for the name of the server that is running the Print Services role.

  4. Click OK.

Later, the administrator decides that Print Services should not be managed from this computer. The administrator removes the remote administration tools for Print Services from the computer running the full installation of Windows Server 2008.

  1. Open Server Manager by clicking Start, pointing to Administrative Tools, and then clicking Server Manager. In the Features section of the Server Manager home page, click Remove features.

  2. On the Select Features page of the Remove Features Wizard, expand Remote Server Administration Tools, and then expand Role Administration Tools.

  3. Clear the check box for Print Services Tools. Click Next.

  4. On the Confirm Removal Options page, click Remove.

    noteNote
    Removing Remote Server Administration Tools does not remove any roles, role services, or features from a computer. For each role, role service, or feature you select within Remote Server Administration Tools, you are removing only management tools and snap-ins that allow you to perform administration tasks for specified roles, role services, or features installed on other computers.

  5. When removal is complete, close the wizard.

A company has purchased a new server. The new computer must run Print Services for the engineering department. After installing Windows Server 2008 on the computer and completing initial configuration tasks, a system administrator adds the Print Services role to the server by using the Server Manager command line.

The administrator can start the Server Manager command line and add Print Services from any directory on the local computer. At first, the administrator adds only the Print Server role service, but then decides to add the role services LPD Service and Internet Printing Service.

noteNote
The Server Manager command is not case sensitive.

  1. Open a Command Prompt window with elevated privileges by right-clicking the Command Prompt executable or the Command Prompt object on the Start menu, and then clicking Run as administrator.

  2. At the prompt, type the following, and then press ENTER:

    ServerManagerCmd.exe -install Print-Server

    noteNote
    ServerManagerCmd.exe also automatically installs all required roles, role services, or features. In this scenario, Server Manager automatically installs Web Server (IIS) and Windows Process Activation Services.

  3. When installation is complete, the Command Prompt window displays the following message:

    Success: Installation succeeded.

  4. Verify that the Print Server role service of Print Services was installed by typing the following at the prompt:

    ServerManagerCmd.exe -query

    Ensure that the Print Services line item in the -query command results is checked and highlighted, and that the Print Server child object is checked and highlighted. Also ensure that other role services of Print Services are not checked.

  5. At the command prompt, type the following, and then press ENTER:

    ServerManagerCmd.exe -install Print-Internet Print-LPD-Service

    noteNote
    You can install each additional role service one at a time, or use the
    –allSubFeatures option to install all the child elements of a role or feature. Server Manager automatically skips those elements already installed on the computer, in this case the Print Server role service.

  6. When installation is complete, the Command Prompt window displays the following message:

    Success: Installation succeeded.

  7. Verify that the LPD Service and Internet Printing Service role services were installed by typing the following at the command prompt:

    ServerManagerCmd.exe -query

    Ensure that the Print Services line item in the -query command results is checked and highlighted, and that all role services of Print Services are now checked and highlighted.

After several days, the administrator decides to use a different computer for serving the print needs of UNIX-based computers, and removes LPD Service from the current computer. However, the administrator wants to continue using the current computer as a basic print server, with the Print Server role service remaining. The administrator uses the Server Manager command line to remove only LPD Service.

  1. If a Command Prompt window is not already open, open a Command Prompt window with elevated privileges by right-clicking the Command Prompt executable, or the Command Prompt object on the Start menu, and then clicking Run as administrator.

  2. At the command prompt, type the following, and then press ENTER:

    ServerManagerCmd.exe -remove Print-LPD-Service -restart

    Adding -restart to the command line restarts the computer automatically when removal is complete, if restarting is required by the software that you are removing. In this instance, a restart of the server is required to remove LPD Service completely.

  3. Verify that LPD Service has been removed from the computer by typing the following at the command prompt:

    ServerManagerCmd.exe -query

    Ensure that, although the Print Services object in the query results is checked and highlighted, the LPD Service is not.

After several months, the administrator moves core printing services to a different server, so that this server can be repurposed. The administrator removes the Print Services role completely from this computer by using the command line.

  1. If a Command Prompt window is not already open, open a Command Prompt window with elevated privileges by right-clicking the Command Prompt executable or the Command Prompt object on the Start menu, and then clicking Run as administrator.

  2. At the command prompt, type the following, and then press ENTER:

    ServerManagerCmd.exe -remove Print-Services -restart

    Adding -restart to the command line restarts the computer automatically when removal is complete, if restarting is required by the software that you are removing. In this instance, a restart of the server is not required to remove Print Services.

  3. Verify that Print Services has been removed from the computer by typing the following at the command prompt:

    ServerManagerCmd.exe -query

    Ensure that the Print Services object in the query results is neither checked nor highlighted.

noteNote
roles, role services, or features that are installed due to dependencies, such as Web Server (IIS) and Windows Process Activation Service, are not removed with the removal of Print Services.

An administrator wants to create a DFS namespace to facilitate file sharing among company employees. Because important data is hosted on the server running File Services, it is important to back up the server by using Windows Server Backup.

noteNote
For the complete Server Manager command-line schema, see the Microsoft Web site (http://go.microsoft.com/fwlink/?LinkId=81203).

The administrator creates an XML answer file to use with the Server Manager command line to add the File Services role and the Windows Server Backup subfeature on the server.

  1. Create the following answer file for the Server Manager command line, and save it to a convenient location as an XML document:

    <?xml version="1.0" encoding="utf-8" ?>
    <ServerManagerConfiguration Action="Install" xmlns="http://schemas.microsoft.com/sdm/Windows/ServerManager/Configuration/2007/1" xmlns:xs="http://www.w3.org/2001/XMLSchema">
       <RoleService Id="FS-DFS-Namespace" />
       <Feature Id="Backup" />
    </ServerManagerConfiguration>
    
    noteNote
    Although the only role service of File Services installed by this answer file is DFS Namespace, the File Services role is installed.

  2. If a Command Prompt window is not already open, open a Command Prompt window with elevated privileges by right-clicking the Command Prompt executable or the Command Prompt object on the Start menu, and then clicking Run as administrator.

  3. At the prompt, type the following, and then press ENTER:

    ServerManagerCmd.exe -inputPath < answerfile .xml> -whatIf -restart

    The placeholder answerfile represents the path and name of the XML answer file created in Step 1. The -whatIf parameter displays a list of all software installed as a result of the command, including dependent roles, role services, and features.

    Adding -restart to the command line restarts the computer automatically when installation is complete, if restarting is required by the software that you are removing. In this instance, a restart of the server is required to install Windows Server Backup.

  4. When installation is complete, the Command Prompt window displays the following message:

    Success: Installation succeeded.

  5. Open the Server Manager console by clicking Start, pointing to Administrative Tools, and then clicking Server Manager.

  6. Verify that the File Services role is installed with the DFS Namespace role service, and that the Windows Server Backup subfeature of Windows Server Backup Features is also installed.

After DFS Namespace and Windows Server Backup are installed, the administrator uses File Services and Windows Server Backup tools in Server Manager to manage the server.

  1. Back up the server. For more information about backing up your server, see the Help provided with Windows Server Backup Features.

  2. If Server Manager is not already open, open Server Manager by clicking Start, pointing to Administrative Tools, and then clicking Server Manager.

  3. In the Server Manager hierarchy pane, expand Roles, and then select File Services to view the role management home page for File Services.

  4. View the status of event messages and services related to File Services. Expand the File Services node in the hierarchy pane.

  5. Select the DFS Management node to open the DFS Management snap-in. Add, remove, or modify namespaces. Add a new replication group, following the steps in the wizard.

Six months later, the administrator wants to use this computer to run a different server role. The administrator modifies the answer file to remove all roles, role services, and features installed on this computer, by replacing the –install parameter with the –remove parameter. The administrator adds the -whatIf parameter to the end of the command line to generate a full list of roles, role services, and features that are removed by the command.

  1. Create the following answer file for the Server Manager command line, and save it to a convenient location as an XML document:

    <?xml version="1.0" encoding="utf-8" ?>
    <ServerManagerConfiguration Action="Remove" xmlns="http://schemas.microsoft.com/sdm/Windows/ServerManager/Configuration/2007/1" xmlns:xs="http://www.w3.org/2001/XMLSchema">
       <RoleService Id="FS-DFS-Namespace" />
       <Feature Id="Backup-Features" />
    
  2. If a Command Prompt window is not already open, open a Command Prompt window with elevated privileges by right-clicking the Command Prompt executable or the Command Prompt object on the Start menu, and then clicking Run as administrator.

  3. At the prompt, type the following, and then press ENTER:

    ServerManagerCmd.exe -inputPath < answerfile .xml> -whatIf -restart

    The placeholder answerfile represents the path and name of the XML answer file created in Step 1. The -whatIf parameter displays a list of all software removed as a result of the command, including dependent roles, role services, and features.

    Adding -restart to the command line restarts the computer automatically when installation is complete, if restarting is required by the software that you are removing.

  4. When removal is complete, the Command Prompt window displays the following message:

    Success: Removal succeeded.

  5. Open the Server Manager console by clicking Start, pointing to Administrative Tools, and then clicking Server Manager.

  6. Verify that the File Services role and Windows Server Backup are no longer installed on the computer.

An enterprise wants to use Hyper-V™ to run virtual machines. The system administrator installs Hyper-V on the computer, and then manages it by using snap-ins in Server Manager.

ImportantImportant
The Hyper-V scenario is only for computers running The 64-bit edition of Windows Server 2008, and that have support at the processor level for virtualization. More specific hardware requirements for Hyper-V are described in the Hyper-V Step-by-Step Guide on the Windows Server TechCenter (http://go.microsoft.com/fwlink/?LinkId=98822). It is strongly recommended that you review these hardware requirements before completing any of the tasks in this scenario.

The administrator's first task is to run Setup for the two Hyper-V update packages. After the updates are complete, Hyper-V is available for installation by using Server Manager.

  1. Double-click the following two update packages stored in %windir%\WSV to make Hyper-V available for installation by using Server Manager:

    • Windows6.0-KB939854-x64.msu

    • Windows6.0-KB939853-x64.msu

  2. If Server Manager is not already open, open Server Manager by clicking Start, pointing to Administrative Tools, and then clicking Server Manager.

  3. In the Roles Summary area, click Add Roles.

  4. On the Select Server Roles page of the Add Roles Wizard, select Hyper-V.

  5. Complete the Add Roles Wizard. For more information about specific configuration pages and settings for Hyper-V, see the Hyper-V Step-by-Step Guide on the Windows Server TechCenter (http://go.microsoft.com/fwlink/?LinkId=98822).

After installing Hyper-V, the administrator uses snap-ins available in Server Manager to manage the role.

  1. If Server Manager is not already open, open Server Manager by clicking Start, pointing to Administrative Tools, and then clicking Server Manager.

  2. In the hierarchy pane, expand Roles, and then expand Windows Server Virtualization.

  3. With the Server Manager window active, press F5 to refresh the console if Hyper-V is installed, but Hyper-V snap-ins and management tools do not show in the hierarchy pane.

After several months, the company no longer requires this server to be used as a virtual machine running multiple operating systems, and the system administrator removes the Hyper-V role.

  1. If Server Manager is not already open, open Server Manager by clicking Start, pointing to Administrative Tools, and then clicking Server Manager.

  2. Open the Roles Summary area if it is not already open. Click Remove roles.

  3. On the Remove Server Roles page of the Remove Roles Wizard, clear the check box for Windows Server virtualization. Click Next.

  4. After confirming that you want to remove Hyper-V, on the Confirm Removal Selections page, click Remove.

  5. Verify that Hyper-V has been removed from the server by refreshing Server Manager and viewing the Roles Summary area.

Informaţiile au fost utile?
(Caractere rămase: 1500)
Vă mulţumim pentru părere

Conţinut pentru comunitate

Adăugare
Afişare:
© 2014 Microsoft. Toate drepturile rezervate.