|
|
|
|
| Windows Server 2008 : Installing the Web Server Role (part 3) |
| Role services define which specific features and options of the IIS platform are available for use on the local Web server. Once you have installed IIS 7.0 on a computer running Windows Server 2008, you can add components by using Server Manager. |
|
|
|
|
|
| Windows Server 2008 : Recovering Role Services and Features (part 4) |
| When Windows SharePoint Services (WSS) is installed on Windows Server 2008 R2 using the default options, WSS stores configuration and content data in SQL databases on SQL servers or in databases included in the Windows Internal Database feature, which are essentially SQL databases with some limited functionality |
|
|
|
|
|
| Windows Server 2008 : Recovering Role Services and Features (part 1) |
| Each particular role on a Windows Server 2008 R2 system can have very specific backup and recovery procedures. As a general rule, though, performing full backups using Windows Server 2008 R2 Windows Server Backup will enable the restore of a system to a previous point in time, including restoring all Windows Server roles, role services, features, and configuration to that previously backed-up state |
|
|
|
|
|
|
|
| Managing and Accessing Windows Server Backup Media |
| Microsoft has completely changed the way backups and backup media are managed with the release of Windows Server 2008. In previous editions of Windows Server versions, the NT Backup utility could back up the entire system or just a set of folders and files. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Windows Server 2008 : Working with NAP (part 7) |
| IPsec enforcement breaks a network down to three different logical networks by using health certificates provided by the Health Certificate Server (HCS). Any computer can be a member of only one of the three networks at any given time—membership to the network is determined by the status of the computers health certificate. |
|
| Windows Server 2008 : Working with NAP (part 6) |
| Health Policies check the client for compliance via the system health validators (SHVs). If you recall from earlier in this chapter, we discussed Windows Security Health Validator (WSHV). These SHVs are the ones provided with Windows 2008 Server, Windows Vista or Windows XP Service Pack 3. |
|
| Windows Server 2008 : Working with NAP (part 5) |
| NAP Health Policies are a combination of settings for health determination and enforcement of infrastructure compliance. Health requirement policies on the NAP health policy server determine whether a NAP client is compliant or noncompliant, how to treat noncompliant NAP clients and whether they should automatically remediate their health state, and how to treat clients that are not NAP capable for different NAP enforcement methods. |
|
|
|
|
|
| Windows Server 2008 : Working with NAP (part 2) |
| The NAP Health Policy Server is the heart of the NAP-supported network infrastructure. The NAP Health Policy Server runs Windows 2008 Server and has the NPS server role installed. The NPS server role is responsible for storing health requirement policies and provides health state validation for NAP. |
|
| Windows Server 2008 : Working with NAP (part 1) |
| The NAP platform main objective is to validate the state of a client computer before connecting to the private network and offer a source of remediation. To validate access to a network based on system health, NAP provides the following areas of functionality |
|
| Windows Server 2008 : Configuring Remote Access (part 6) |
| Windows Server 2008 features a variety of inbound and outbound features that you will need to be able to implement for your exam. The old version of Windows Firewall has been upgraded and is now called Windows Firewall with Advanced Security (WFAS). |
|
|
|
| Windows Server 2008 : Configuring Remote Access (part 4) |
| Internet Connection Sharing (ICS) is a feature that permits you to use Windows Server 2008 to connect a small office network or home network over the Internet. Not much has changed in this version of Windows Server 2008, and you may find that most of the features and set up procedures are very similar to that of Windows Server 2003 |
|