[FREE NEW UPDATED QUESTIONS] Microsoft 70-417 Practice Exam Questions and Answers Sample Papers Shared By Braindump2go (191-200)
2015 Free Download of Latest Microsoft 70-417 Practce Exam Questions from Braindump2go will help you have a 100% success of 70-417 real exam! All questions are the latest checked and released! Answers are 100% correct guaranteed! In order to increase your confidence, 100% Full Money Back Guarantee is promised by Braindump2go! Instant Download Now!
Exam Code: 70-417
Exam Name: Upgrading Your Skills to MCSA Windows Server 2012 R2 Exam
Your network contains an Active Directory domain named contoso.com. The domain contains a server named Server1 that runs Windows Server 2012 R2 and a server named Server2 that runs Windows Server 2008 R2 Service Pack 1 (SP1). Both servers are member servers.
On Server2, you install all of the software required to ensure that Server2 can be managed remotely from Server Manager.
You need to ensure that you can manage Server2 from Server1 by using Server Manager.
Which two tasks should you perform on Server2? (Each correct answer presents part of the solution.
A. Run the Configure-SMRemoting.ps1 script.
B. Run the Enable-PSSessionConfigurationcmdlet.
C. Run the Set-ExecutionPolicycmdlet.
D. Run the systempropertiesremote.exe command
E. Run the Enable-PSRemotingcmdlet.
First, installed a 2008 R2 SP1 server and installed .Net 4 and WFM 3 on it.
When tried to connect with server manager from 2012 received this error:
Next ran these commands on the 2008 R2 server from an elevated PowerShell:
Set-ExecutionPolicyRemoteSigned Configure-SMRemoting.ps1 -force –enable
Finally, you can see where the machine is now showing as ready to be managed by 2012:
The above mentioned link gives an exact step-by-step example of how to do this, which includes setting the execution policy of PowerShell and Running the SMRemoting.ps1 script. http://technet.microsoft.com/en-us/library/hh849694.aspx
This link describes that you cannot use the Enable-PSRemoting command on a machine that has both PS 2.0 and 3.0. Since 2008 R2 ships with 2.0, and WMF 3 installs 3.0, that means the 2008 R2 box would have both.
CAUTION: On systems that have both Windows PowerShell 3.0 and the Windows PowerShell 2.0 engine, do not use Windows PowerShell 2.0 to run the Enable configured correctly. Remote commands, and later attempts to enable and disable remoting, are likely to fail.
Other Windows Server from Server Manager 2012
Now the new Server Manager is a lifesaver, it allows to manage multiple servers from one console. By default it is only supported for Windows Server 2012 R2 but by downloading Windows Management Framework 3.0 and, Net 4 you can manage older versions as well. (2008, 2008R2)
You can download the needed files from here ?
And you need to install these on the servers you need to manage. After these are installed you need to run some commands.
Configure-SMRemoting.ps1 -force enable
After that is done, you can now manage your other servers.
You can see that now the AD server (DC) is added and AD role is added on the side as well Smile
Your network contains an Active Directory domain named contoso.com. The network contains a server named Server1 that runs Windows Server 2012 R2 and a server named Server2 that runs Windows Server 2008 R2 Service Pack 1 (SP1). Server1 and Server2 are member servers.
You need to ensure that you can manage Server2 from Server1 by using Server Manager.
Which two tasks should you perform? (Each correct answer presents part of the solution. Choose two.)
A. Install Windows Management Framework 3.0 on Server2.
B. Install Remote Server Administration Tools on Server1.
C. Install the Windows PowerShell 2.0 engine on Server1.
D. Install Microsoft .NET Framework 4 on Server2.
E. Install Remote Server Administration Tools on Server2.
Your network contains an Active Directory domain named contoso.com. All servers run either Windows Server 2008 R2 or Windows Server 2012 R2. All client computers run either Windows 7 or Windows 8. The domain contains a member server named Server1 that runs Windows Server 2012 R2. Server1 has the File and Storage Services server role installed. On Server1, you create a share named Share1.
You need to ensure that users can use Previous Versions to restore the files in Share1.
What should you configure on Server1?
A. A data recovery agent
B. The Shadow Copies settings
C. The Recycle Bin properties
D. A Windows Server Backup schedule
You have a server named Server1 that runs Windows Server 2012 R2.
Server1 has the HyperV server role installed.
Server1 is connected to two Fibre Channel SANs and is configured as shown in the following table.
You have a virtual machine named VM1.
You need to configure VM1 to connect to SAN1.
What should you do first?
A. Create a virtual Fibre Channel SAN.
B. Configure network adapter teaming.
C. Add one HBA.
D. Create a Hyper-V virtual switch.
You have a file server named Server1 that runs Windows Server 2012 R2. Server1 has following hardware configurations:
– 16 GB of RAM
– A single quad-core CPU
– Three network teams that have two network adapters each
You add additional CPUs and RAM to Server1.
You repurpose Server1 as a visualization host.
You install the Hyper-V server role on Server1.
You need to create four external virtual switches in Hyper-V.
Which cmdlet should you run first?
C. Remove- NetLbfoTeam
Here we’re talking about hardware network adapters which belong to NIC teams Each external virtual switch must be connected to a NIC or a NIC team, so we need 4 NICs or NIC teams but currently only have 3 teams available.
=>we need to break a team first and then connect the two last external virtual switches to each of the 2 “liberated” NIC
(an other solution could be to add one physical NIC and connect the last external virtual switch to it or add several (two or more) NICs, create a NIC team containing them and connect the external virtual switch to the NIC team)
NIC Teaming (NetLBFO) Cmdlets in Windows PowerShell
Remove-NetLbfoTeam: Removes the specified NIC team from the host.
http://technet.microsoft.com/en-us/library/hh831648.aspx NIC Teaming Overview
NIC Teaming, also known as load balancing and failover (LBFO), allows multiple network adapters on a computer to be placed into a team for the following purposes:
Bandwidth aggregation Traffic failover to prevent connectivity loss in the event of a network component failure This feature has been a requirement for independent hardware vendors (IHVs) to enter the server network adapter market, but until now NIC Teaming has not been included in Windows Server operating systems.
Requirements NIC Teaming requires the presence of a single Ethernet network adapter, which can be used for separating traffic that is using VLANs. All modes that provide fault protection through failover require at least two Ethernet network adapters.
Windows Server?2012 supports up to 32 network adapters in a team.
Drag and Drop Question
Your network contains three servers. The servers are configured as shown in the following table.
Your company plans to standardize all of the servers on Windows Server 2012 R2.
You need to recommend an upgrade path for each server.
The solution must meet the following requirements:
– Upgrade the existing operating system whenever possible.
– Minimize hardware purchases.
Which upgrade path should you recommend for each server? To answer, drag the appropriate upgrade path to each server in the answer area. Each upgrade path may be used once, more than once, or not at all.
You perform a Server Core Installation of Windows Server 2012 R2 on a server named Server1. You need to add a graphical user interface (GUI) to Server1.
Which tool should you use?
A. The setup.exe command
B. The imagex.exe command
C. The Install-RoleServicecmdlet
D. The Add-WindowsFeaturecmdlet
From the MSPress book “Upgrading your skills to MCSA Windows Server 2012 R2” Converting a server with a GUI to or from Server Core You can switch between a Server Core installation and full installation in Windows Server 2012 R2 because the difference between these installation options is contained in two specific Windows features that can be added or removed. The first feature, Graphical Management Tools and Infrastructure (Server-Gui-Mgmt-Infra), provides a minimal server interface and server management tools such as Server Manager and the Microsoft Management Console (MMC). The second feature, Server Graphical Shell (Server-Gui-Shell), is dependent on the first feature and provides the rest of the GUI experience, including Windows Explorer. In Figure 1-9, you can see these two features in the Add Roles And Features Wizard, on the Select Features page, beneath User Interfaces And Infrastructure.
To convert a full installation to a Server Core installation, just remove these two features in Server Manager.
Note that removing the first feature will automatically remove the second, dependent feature.
You can also remove these graphical interface features in Windows PowerShell. If you have deployed a full installation of Windows Server 2012 R2 and want to convert it to a Server Core installation, run the following Windows PowerShell command:
Uninstall-WindowsFeature Server-GUI-MgmtiInfra -restart Remember that you only need to specify Server-Gui-Mgmt-Infra for removal to remove both this feature and Server-Gui-Shell. Once the graphical management tools and graphical shell have been removed, the server restarts. When you log back on, you are presented with the Server Core user interface.
The process can be reversed by replacing both features.
You can do this from a remote server by using the Add Roles And Features Wizard in Server Manager.
You can also do it locally by running the following Windows PowerShell command:
Install-WindowsFeature Server-Gui-Shell restart
Note that when you install these two features from Windows PowerShell, you must specify them both.
To configure Minimal Server Interface, you can either start with a Server Core installation and add Graphical Management Tools and Infrastructure or start with a Server with a GUI and remove Server Graphical Shell.
The Graphical Management Tools and Infrastructure feature includes Server Manager and some other basic administrative tools, but it does not include (i.e among tohers) Windows Explorer.
NB: http://technet.microsoft.com/en-us/library/jj205467.aspx Install-WindowsFeature
Installs one or more Windows Server roles, role services, or features on either the local or a specified remote server that is running Windows Server 2012 R2.
This cmdlet is equivalent to and replaces Add-WindowsFeature, the cmdlet that was used to install roles, role services, and features in Windows Server 2008 R2.
Minimal Server Interface
This is new. In Windows Server 2012 R2, with a Server with GUI installation one can remove the Server Graphical Shell (which provides full GUI for server) to set a full server installation with the so-called Minimal Server Interface option with the following PowerShell comlet.
Unstall-WindowsFeature Server-Gui-Shell restart.
This basically provides a Server with GUI, but without installing Internet Explorer 10, Windows Explorer, the desktop, and the Start screen.
Additionally, Microsoft Management Console (MMC), Server Manager, and a subset of Control Panel are still in place.
Minimal Server Interface requires 4 GB more disk space than Server Core alone
You have a server named Served that runs Windows Server 2012 R2. Server1 has five network adapters. Three of the network adapters are connected to a network named LAN1. The two other network adapters are connected to a network named LAN2.
You create a network adapter team named Team1 from two of the adapters connected to LAN1. You create a network adapter team named Team2 from the two adapters connected to LAN2. A company policy states that all server IP addresses must be assigned by using a reserved address in DHCP.
You need to identify how many DHCP reservations you must create for Server1.
How many reservations should you identify?
1 reservation for the NIC team on LAN1
1 reservation for the stand-alone NIC on LAN1
1 reservation for the NIC team on LAN2
=> 3 reservations.
You have a server named Served that runs Windows Server 2012 R2.
You connect three new hard disks to Server 1.
You need to create a storage space that contains the three disks.
The solution must meet the following requirements:
– Provide fault tolerance if a single disk fails.
– Maximize the amount of useable storage space.
What should you create?
A. A spanned volume
B. A simple space
C. A parity space
D. A mirrored space
Simple space does not provide fault tolerance, neither does spanned volumes, whereas parity & mirrored spaces do. So the question is parity space or mirrored space to maximize the amount of useable storage space?
Unlike RAID, spanned volumes have no fault- tolerance, so if any disk fails, the data on the whole volume could be lost.
Storage Spaces explained: a great feature, when it works Three-way mirroring gives you less usable space than two-way mirroring, but can tolerate the failure of up to two disks at once.
Parity mirroring gives more usable space than either mirroring mode (a 20GB storage space configured with two-way mirroring will require about 40GB of physical disk space, but a 20GB parity storage space requires only about 30GB) but comes with the aforementioned performance hit.
NB: Parity spaces are not supported in a failover cluster configuration.
You have a server named Server1 that runs a full installation of Windows Server 2012 R2.
You need to uninstall the graphical user interface (GUI) on Server1.
You must achieve this goal by using the minimum amount of administrative effort.
What should you do?
A. From Server Manager, uninstall the User Interfaces and Infrastructure feature.
B. From Windows PowerShell, run Uninstall-WindowsFeature PowerShell-ISE.
C. From Windows PowerShell, run Uninstall-WindowsFeature Desktop-Experience.
D. Reinstall Windows Server 2012 R2on the server.
Braindump2go Regular Updates of Microsoft 70-417 Preparation Materials Exam Dumps, with Accurate Answers, Keeps the Members One Step Ahead in the Real 70-417 Exam. Field Experts with more than 10 Years Experience in Certification Field work with us.