Get Familiar With Windows Server 2008, Server Administrator
By Certification Magazine —
1 | 2 | 3 | 4 |
The WinRM service provides access to WMI data and enables event collection. For event collection and subscription to events to function, the service must be running. The WinRM service cannot manage server processor and memory usage with standard or custom resource policies.
Security Filtering limits the scope of the GPO to apply to only the users or computers that have permissions to the GPO. For example, you could remove the default permissions of Authenticated Users on a GPO that is linked to a domain and add a particular group to have Read permissions. The GPO would only be read by the particular group in the domain and not everyone in the domain. Since you cannot use WinRM, it would not help use Security Filtering.
References:
Objective: Plan application and data provisioning.
Sub-objective: Provision applications.
Single answer, multiple-choice
You are a server manager for your organization. Your organization has a single Active Directory domain that contains Windows Server 2008 domain controllers and Windows Vista client computers.
You have recently installed Microsoft System Center Configuration Manager 2007 on a Windows Server 2008 server. You plan to use Configuration Manager 2007 to apply software updates to client computers in your organization. What must you do to apply software updates on client computers?
A. Install Windows Installer 2.0.
B. Configure the software Distribution component settings.
C. Install Windows Server Update Services (WSUS) 3.0.
D. Configure a distribution point.
Answer:
C. Install Windows Server Update Services (WSUS) 3.0.
Tutorial:
You should install Windows Server Update Services (WSUS) 3.0 to ensure System Center Configuration Manager 2007 can apply software updates to client computers in your organization. WSUS 3.0 is required to synchronize software updates on client computers. You must install WSUS 3.0 prior to creating a software update point. System Center Configuration Manager 2007 allows client computers to connect to the WSUS server when client computers are performing a scan for software updates. The client computer uses a Windows Update Agent (WUA) to connect to the WSUS server for retrieving relevant software updates that need to be scanned for compliance.
You should not install Windows Installer 2.0 in this scenario. Instead, you should install Windows Installer 3.1 to use with Configuration Manager 2007 and use Configuration Manager 2007 to apply software updates to client computers in your organization.
You should not configure the software Distribution component settings to ensure System Center Configuration Manager 2007 can apply software updates to client computers in your organization. This is required when creating a software distribution point. You would configure a distribution point to distribute software packages to users and computer resources.
You should not configure a distribution point to ensure System Center Configuration Manager 2007 can apply software updates to client computers in your organization. You need to configure a distribution point when planning to distribute software to client computers. You must create and configure at least one distribution point to distribute software to client computers.
Reference:
Objective: Plan for business continuity and high availability.
Sub-objective: Plan high availability.
Multiple answer, multiple-choice
You are the administrator for a company that manufactures industrial chemicals. All servers in the single domain run Windows Server 2008, and all clients run Windows Vista. You want to create a Terminal Services Farm that provides fault tolerance in the event that a server is unavailable. What must you configure to provide load balancing? (Choose all that apply.)
A. Install the TS Session Broker role service.
B. Install the TS Licensing role.
C. Install Windows System Resource Manager 2007 (WSRM).
D. Populate the Session Broker Computers Local Group.
E. Populate the TS Web Access Computers Group.
F. Populate the TS Web Access Administrators group.
G. Manage the terminal servers with WSRM and configure them to participate in the load balancing.
H. Add the DNS entries for the terminal servers.
Answer:
A. Install the TS Session Broker role service.
D. Populate the Session Broker Computers Local Group.
H. Add the DNS entries for the terminal servers.
Tutorial:
You should install the TS Session Broker role service, populate the Session Broker Computers Local group and add the DNS entries for the terminal servers. The TS Session Broker role service is used to support session load balancing between terminal servers in a server farm. This service is used to reconnect an existing session on a terminal server that is a member of a load-balanced terminal server farm.
The TS Session Broker service provides cross-server session reconnection capability and provides load-balancing capability, as well as the Session Broker Load Balancing (SBLB) feature in Windows Server 2008. SBLB is an application-level load-balancing solution that is managed based on the number of sessions running. It has built-in protection against log-on throttling and a max session count. You can combine NLB with SBLB to have complete server and application load balancing.
The Session Broker Computers Local group is used to determine which terminal servers are using the Session Broker to manage sessions. You then must join the terminal servers to the Session Broker and configure them to participate in load balancing.
You should add the DNS entries for the terminal servers. This step is necessary to provide name resolution and also round robin DNS.
You should not populate the TS Web Access Computers local group. Members of this group can query the list of RemoteApp programs that are available from this terminal server. This group is not necessary to configure Network Load Balancing.
You should not populate the TS Web Access Administrators local group. Members of this group can modify the default TS Web Access Web site. This group is not necessary to configure Network Load Balancing.
You should not use the Windows System Resource Manager 2007 (WSRM). WSRM is a component that is used to limit CPU and memory usage on the servers on which the product is installed. WSRM can be useful when you want to run multiple applications on a server while ensuring no application consumes more than a certain amount of resources.
This can be useful to ensure that an application's performance does not hurt another application's performance. WSRM lets you place limits on a process or user level to make sure all processes have the required resources. WSRM is not designed to load balance servers or applications.
1 | 2 | 3 | 4 |
