070-410日本語試験無料問題集「Microsoft Installing and Configuring Windows Server 2012 (070-410日本語版) 認定」
正解：
Explanation
Virtual machines can be deployed to Hyper-V using Windows Deployment Services (WDS). To accomplish this requires the proper WDS infrastructure be in place and that the VM PXE boot using a Legacy Network Adapter.
By default, there is only a "Standard Network Adapter" installed on the Virtual Machine, but for PXE functionality you will need to add a "Legacy Network Adapter".
Go to the "Legacy Network Adapter" that you just added and specify that it should use the Virtual Switch that you just created.
Last but not least, you should change the BIOS boot priority to make sure that the Virtual Machine always tries to boot first using the "Legacy Network Adapter". Just select the "Legacy Network Adapter" and move it to the top using the buttons.
Start your Virtual Machine and now PXE boot should work.
The Pre-Boot Execution Environment (PXE) provider for Windows Deployment Services provides client boot services over the network. It registers itself with the WDS Server service (the main server-side service of the Windows Deployment Services solution) and requests a remote procedure call (RPC) endpoint.
After the Windows Deployment Services server role is installed, you must configure the server by using either the Windows Deployment Services MMC snap-in or the /Initialize-Server command-line option. The PXE provider must be configured properly before it can provide client boot services over the network.
References:
http://technet.microsoft.com/en-us/library/cc726550%28v=WS.10%29.aspx
正解：
Explanation
Schema -Contains the Schema container, which stores class and attribute definitions for all existing and possible Active Directory objects in cn=schema,cn=configuration,dc= forestRootDomain. Updates to this container are replicated to all domain controllers in the forest. You can view the contents of the Schema container in the Active Directory Schema console.
An Active Directory Lightweight Directory Services (AD LDS) schema defines, using object classes and attributes, the types of objects and data that can be created and stored in an AD LDS directory. The schema can be extended with new classes and attributes, either by administrators or by the applications themselves. In addition, unneeded schema classes and attributes can be deactivated.
References:
http://technet.microsoft.com/en-us/library/cc771975.aspx
http://technet.microsoft.com/en-us/library/cc731547.aspx
正解：
Explanation
Box 1: Shut down VM1.
Box 2: Modify the virtual switch settings of the legacy network adapter.
Box 3: Modify the BIOS settings of VM1.
Note:
Step 1: The VM need to be shutdown first.
Step 2:
1. You need to create a virtual switch. This is needed for the Virtual Machine to be able to communicate with the network. If you already have created a virtual machine for your network, you can skip this step. Start by right-clicking the Hyper-V host in Hyper-V Manager and selecting "Virtual Switch Manager".
2. Create a new Virtual Switch. Select "External", which is similar to "Bridged" if you're used to other virtualization software.
3. Give the new Virtual Switch a name.
4. By default, there is only a "Standard Network Adapter" installed on the Virtual Machine, but for PXE functionality you will need to add a "Legacy Network Adapter".
5. Go to the "Legacy Network Adapter" that you just added and specify that it should use the Virtual Switch that you just created.
Step 3: you should change the BIOS boot priority to make sure that the Virtual Machine always tries to boot first using the "Legacy Network Adapter". Just select the "Legacy Network Adapter" and move it to the top using the buttons.
Step 4: Start your Virtual Machine and now PXE boot should work.
Reference: Guide: How to get PXE boot to work in Hyper-V
正解：
Explanation
1) Remove adatum\user1 from Group1
2) Convert Group1 to a universal group
3) Convert Group1 to a global group
Domain local Groups that are used to grant permissions within a single domain. Members of domain local groups can include only accounts (both user and computer accounts) and groups from the domain in which they are defined.
---- to review. Universal groups can only include objects from its own forest Groups can have - domain local, built-in local, global, and universal. That is, the groups have different areas in different scopes which they are valid.
A domain local group is a security or distribution group that can contain universal groups, global groups, other domain local groups from its own domain, and accounts from any domain in the forest. You can give domain local security groups rights and permissions on resources that reside only in the same domain where the domain local group is located. A global group is a group that can be used in its own domain, in member servers and in workstations of the domain, and in trusting domains. In all those locations, you can give a global group rights and permissions and the global group can become a member of local groups. However, a global group can contain user accounts that are only from its own domain. A universal group is a security or distribution group that contains users, groups, and computers from any domain in its forest as members. You can give universal security groups rights and permissions on resources in any domain in the forest. Universal groups are not supported.
Domain local -Groups that are used to grant permissions within a single domain. Members of domain local groups can include only accounts (both user and computer accounts) and groups from the domain in which they are defined. Built-in local - Groups that have a special group scope that have domain local permissions and, for simplicity, are often referred to as domain local groups. The difference between built-in local groups and other groups is that built-in local groups can't be created or deleted. You can only modify built-in local groups. References to domain local groups apply to built-in local groups unless otherwise noted. Global - Groups that are used to grant permissions to objects in any domain in the domain tree or forest. Members of global groups can include only accounts and groups from the domain in which they are defined. Universal - Groups that are used to grant permissions on a wide scale throughout a domain tree or forest. Members of global groups include accounts and groups from any domain in the domain tree or forest.
Global to universal. This conversion is allowed only if the group that you want to change is not a member of another global scope group.
Domain local to universal. This conversion is allowed only if the group that you want to change does not have another domain local group as a member.
Universal to global. This conversion is allowed only if the group that you want to change does not have another universal group as a member.
Universal to domain local. There are no restrictions for this operation.
正解：
Explanation
The Set-GPPermissions command grants a level of permissions to a security principal for one GPO or all the GPOs in a domain.
The parameter -All <SwitchParameter>
specifies that the permission level is set for the specified security principal for all GPOs in the domain.
The parameter -PermissionLevel <GPPermisssionType>
specifies the permission level to set for the security principal. The valid permission levels are: GpoRead, GpoApply, GpoEdit, GpoEditDeleteModifySecurity or None.
Reference: Set-GPPermissions
https://technet.microsoft.com/en-us/library/ee461038.aspx