升级技能到MCSA：Windows Server 2012实战指南

4星 · 超过85%的资源需积分: 9 165 浏览量更新于2024-07-26 1 收藏 30.13MB PDF 举报

"Microsoft.Press.Exam.Ref.70-417.Upgrading Your Skills to MCSA Windows Server 2012 是一本由J.C. Mackin编写的考试参考书籍，旨在帮助读者提升技能以获得MCSA（微软认证解决方案专家）资格，专注于Windows Server 2012平台。该书由微软出版社出版，适用于准备70-417考试的考生。" 本书详细介绍了升级到MCSA Windows Server 2012所需掌握的关键知识点和技术，包括但不限于以下内容： 1. **系统安装与升级**：学习如何在不同的环境中安装Windows Server 2012，了解各种安装选项，如全新安装、升级安装和迁移。此外，还会涵盖服务器核心安装和桌面体验的比较。 2. **活动目录（Active Directory）管理**：讲解如何规划、创建和管理活动目录森林、域和组织单元，以及用户、组和计算机账户。还会涉及DNS（域名系统）配置，以支持活动目录的运行。 3. **网络服务**：涵盖DHCP（动态主机配置协议）和TCP/IP配置，确保服务器能正确分配IP地址并进行网络通信。同时，也会介绍WINS（Windows Internet名称服务）和静态路由的设置。 4. **文件服务和共享**：讨论NTFS和DFS（分布式文件系统）的使用，以及权限管理和文件服务器的优化策略，包括文件和打印服务的配置。 5. **动态存储**：讲解如何使用Storage Spaces、RAID（冗余磁盘阵列）和数据保护技术，如Hyper-V集成的备份和还原。 6. **虚拟化技术**：深入探讨Hyper-V，包括虚拟机的创建、管理、迁移和高可用性设置，以及虚拟网络配置。 7. **系统更新和安全性**：涵盖WSUS（Windows Server Update Services）的部署，以管理组织内的更新流程。同时，讲解安全策略、防火墙、BitLocker驱动器加密和审核日志的使用。 8. **身份验证和访问控制**：介绍Kerberos、NTLM和证书服务，以及如何实施精细的权限策略，如RADIUS（远程访问拨入用户服务）和NAP（网络访问保护）。 9. **故障转移群集**：教授如何构建和管理故障转移群集，以提高关键业务应用的可用性和容错能力。 10. **监控和性能调整**：学习使用性能监视器、事件查看器和其他工具来识别和解决性能问题，以及实施性能计数器和警报。通过本书的学习，读者将能够对Windows Server 2012有全面的理解，并具备成功通过70-417考试的能力。书中包含的实践案例和复习题有助于加深理解，巩固所学知识。同时，微软出版社还提供了技术支持和反馈渠道，以助于读者在学习过程中获取帮助。

xvIntroduction

Preparing for the Exam

Microsoft certication exams are a great way to build your resume and let the world know

about your level of expertise. Certication exams validate your on-the-job experience and

product knowledge. While there is no substitution for on-the-job experience, preparation

through study and hands-on practice can help you prepare for the exam. We recommend

that you round out your exam preparation plan by using a combination of available study

materials and courses. For example, you might use the Training Kit and another study guide

for your "at home" preparation, and take a Microsoft Ofcial Curriculum course for the class-

room experience. Choose the combination that you think works best for you.

2 CHAPTER 1 Install and congure servers

operating system. Fortunately, in this case the hardware requirements are easy to learn:

the minimum hardware requirements for Windows Server 2012 are the same as those for

Windows Server 2008 R2. Here’s a recap:

■

Processor: 1.4 GHz 64-bit processor

■

RAM: 512 MB (allocate more for the Chinese version)

■

Disk space: 32 GB

Don’t miss the obvious here. Windows Server 2012 requires a 64-bit processor, unlike

Windows Server 2008 (but like Windows Server 2008 R2). This fact could easily form the

basis of a test question. If a question states you need to upgrade to Windows Server 2012

on an existing server, make sure the server has a 64-bit processor. If it doesn’t, you need to

replace the hardware. If the hardware is compatible, you can perform an in-place upgrade (as

opposed to a fresh installation) from Windows Server 2008 SP2 or later.

Migrating server roles by using the Windows Server

Migration Tool

Don’t forget about the Windows Server Migration Tool (WSMT), a command-line tool that

helps you migrate certain roles to servers running Windows Server. WSMT is a built-in, install-

able feature of Windows Server 2012. When you use WSMT, the source computer can be

running Windows Server 2003 (SP2 or later), Windows Server 2008, Windows Server 2008 R2,

or Windows Server 2012.

You don’t need to remember the specics of how to use WSMT for the 70-417 exam.

However, it’s a good idea to review the procedure for setting up a role migration from

a server running Windows Server 2008 R2. Some of these elements, such as Install-

WindowsFeature Migration, SmigDeploy.exe, or Get-SmigServerFeature, could possibly

appear in a test question.

To set up a role migration from a server running Windows Server 2008 R2, take the follow-

ing steps:

1. Install WSMT on the destination server running Windows Server 2012. At an elevated

Windows PowerShell prompt, type the following:

Install-WindowsFeature Migration

2. Create deployment folders on the destination server running Windows Server 2012.

For this step, use the SmigDeploy.exe command at an elevated command prompt. For

example, to create a deployment folder to migrate from Windows Server 2008 R2, type

the following:

SmigDeploy.exe /package /architecture amd64 /os WS08R2 /path <deployment folder

path>

3. Copy the deployment folders from the destination server to the source server.

Objective 1.1: Install servers CHAPTER 1 3

4. Register WSMT on source servers by typing the following at an elevated command

prompt in the copied directory on the source server:

.\Smigdeploy.exe

5. Load WSMT into your Windows PowerShell session. To load WSMT, type the following

and then press Enter.

Add-PSSnapin Microsoft.Windows.ServerManager.Migration

6. Type Get-SmigServerFeature at an elevated Windows PowerShell prompt to nd out

which features can be exported from the local server.

At this point, you would use cmdlets such as Export-SmigServerSettings, Import-

SmigServerSettings, Send-SmigServerData, and Receive-SmigServerData to migrate

data and settings to the destination server.

MORE INFO For more information about using WSMT to migrate to Windows Server

2012, visit http://technet.microsoft.com/en-us/library/jj134202. For cmdlets that apply to

Windows Server 2008 R2, visit http://technet.microsoft.com/en-us/library/dd871125.

Features on Demand

A copy of the binary les for all features and roles that are installed during Windows Setup

is stored in a directory called the side-by-side store, located in Windows\WinSxS. Keeping a

copy of the feature les available on disk in this way enables you to add a role or enable a

feature after Windows Server installation without needing to access Windows Server media.

In previous versions of Windows Server, these features les remained on disk for the life of

the operating system. The disadvantage of this approach was that these les took up space

on the disk even if you never wanted to install the associated feature or role. In addition, you

weren’t able to reduce the size of the installation image, which you might want to do when

creating custom installation media for your organization.

In Windows Server 2012, you can minimize the footprint of your installation by deleting

the les for features you’re not using from the side-by-side store. This ability to delete feature

les is called Features on Demand. To later reinstall a role or feature for which les have been

deleted, you need access to the Windows Server 2012 source les.

To completely remove all les for a role or feature from disk, use the Uninstall-

WindowsFeature cmdlet of Windows PowerShell and specify the name of the feature by using

the –Remove option. For example, to delete the DHCP server binaries from server storage,

run the following Windows PowerShell command:

Uninstall-WindowsFeature DHCP –Remove

EXAM TIP

Windows PowerShell is heavily emphasized on the 70-417 exam.

剩余379页未读，继续阅读

fl19871104

粉丝: 0
资源: 2

升级技能到MCSA：Windows Server 2012实战指南

All the 5 fits failed. It is very likely that your model is misconfigured. You can try to debug the ...

ImportError: cannot import name 'url' from 'django.conf.urls'

Error: Node Sass does not yet support your current environment: OS X 64-bit with Unsupported runtime (93)

提示You should consider upgrading via the 'D:\Program Files (x86)\pythonnnnn\python.exe -m pip install --upgrade pip' command.

grpc版本是1.33.2；protoc版本是3.13.0 官网对应的 编译报错： #error: This file was generated by a newer version of protoc which is

最新资源

grpc版本是1.33.2；protoc版本是3.13.0 官网对应的编译报错： #error: This file was generated by a newer version of protoc which is