SIMULATION
Task 10
You need to configure Hyper-V to ensure that running virtual machines can be moved between SRV1 and SRV2 without downtime.
You do NOT need to move any virtual machines at this time.
One possible solution to configure Hyper-V to ensure that running virtual machines can be moved between SRV1 and SRV2 without downtime is to use Live Migration. Live Migration is a feature of Hyper-V that allows you to move a running virtual machine from one host to another without any noticeable interruption of service. To set up Live Migration between SRV1 and SRV2, you need to perform the following steps:
On both SRV1 and SRV2, openHyper-V Managerfrom theAdministrative Toolsmenu or by typingvirtmgmt.mscin the Run box.
In the left pane, right-click on the name of the server and selectHyper-V Settings.
In theHyper-V Settingsdialog box, selectLive Migrationsin the navigation pane.
Check the boxEnable incoming and outgoing live migrations.
UnderAdvanced Features, you can optionally enable theUse any available network for live migrationoption, which allows Hyper-V to use any available network adapter on the source and destination servers for live migration. If you do not enable this option, you need to specify one or more network adapters to be used for live migration by clicking on theAddbutton and selecting the network adapter from the list. You can also change the order of preference by using theMove UpandMove Downbuttons.
ClickOKto apply the settings.
Now, you have configured Hyper-V to enable live migration between SRV1 and SRV2. You can use Hyper-V Manager or Windows PowerShell to initiate a live migration of a running virtual machine from one server to another.
SIMULATION
Task 12
You need to create a Group Policy Object (GPO) named GPO1 that only applies to a group named MemberServers.
To create a GPO named GPO1 that only applies to a group named MemberServers, you can follow these steps:
On a domain controller or a computer that has the Remote Server Administration Tools (RSAT) installed, openGroup Policy Managementfrom theAdministrative Toolsmenu or by typinggpmc.mscin the Run box.
In the left pane, expand your domain and right-click onGroup Policy Objects. SelectNewto create a new GPO.
In theNew GPOdialog box, enterGPO1as theNameof the new GPO and clickOK. You can also optionally select a source GPO to copy the settings from.
Close theGroup Policy Management Editorand return to theGroup Policy Managementconsole. Right-click on the new GPO and selectScope. Here, you can specify the scope of management for the GPO, such as the links, security filtering, and WMI filtering.
Under theSecurity Filteringsection, click onAuthenticated Usersand then click onRemove. This will remove the default permission granted to all authenticated users and computers to apply the GPO.
Click onAddand then type the name of the group that you want to apply the GPO to, such asMemberServers. ClickOKto add the group to the security filter. You can also click onAdvancedto browse the list of groups available in the domain.
To link the GPO to an organizational unit (OU) or a domain, right-click on the OU or the domain in the left pane and selectLink an Existing GPO. Select the GPO that you created, such asGPO1, and clickOK. You can also change the order of preference by using theMove UpandMove Downbuttons.
SIMULATION
Task 6
You need to ensure that you can manage DC1 by using Windows Admin Center on SRV1.
The required source files are located in a folder named \\dc1.contoso.com\install.
One possible solution to ensure that you can manage DC1 by using Windows Admin Center on SRV1 is to install Windows Admin Center on SRV1 and add DC1 as a managed server. Windows Admin Center is a web-based management tool that allows you to manage servers, clusters, Windows PCs, and Azure virtual machines (VMs) from a single interface. Here are the steps to install Windows Admin Center on SRV1 and add DC1 as a managed server:
On SRV1, open a web browser and go to the folder named \dc1.contoso.com\install. Download the Windows Admin Center installer file (WindowsAdminCenter.msi) and save it to a local folder, such as C:\Temp.
After the installation is complete, launch Windows Admin Center from the Start menu or the desktop shortcut. If you installed Windows Admin Center as a service, you can access it from a web browser by using the URL https://localhost:6516 or https://<SRV1>:6516, where <SRV1> is the name or IP address of SRV1.
On the Windows Admin Center dashboard, clickAddto add a new connection. SelectServeras the connection type and enter the name or IP address of DC1 in the Server name field. Optionally, you can specify the display name, description, and tags for the connection. ClickSubmitto add DC1 as a managed server.
Now, you can manage DC1 by using Windows Admin Center on SRV1. You can also add more servers or other types of connections to Windows Admin Center and manage them from the same interface
Your network contains an on-premises Active Directory Domain Services (AD DS) domain. The domain contains a user named User1 and the servers shown in the following table.
User1 is a member of the Protected Users security group.
User1 performs the following actions:
* From Server1, establishes a remote PowerShell session on Server2
* From the PowerShell session on Server2, attempts to access a resource on Backup1
The request to access the resource on 8ackup1 is denied.
You need to ensure that User1 can access the resources on Backup1 by using the PowerShell session on Server2. The solution must follow the principle of least privilege and minimize administrative effort.
What should you configure?
SIMULATION
Task 5
You have an application that is copied to a folder named C:\app on SRV1. C:\app also contains also a Dockerfile for the app.
On SRV1. you need to create a container image for the application by using the Dockerfile. The container image mutt be named app1.
Explore
To create a container image named app1 for your application using the Dockerfile in the C:\app directory on SRV1, follow these steps:
Step 1: Open PowerShell or Command Prompt First, open PowerShell or Command Prompt on SRV1.
Step 2: Navigate to the Application Directory Change to the directory where your application and Dockerfile are located:
cd C:\app
Step 3: Build the Container Image Use the docker build command to create the container image. The -t flag tags the image with the name app1:
docker build -t app1 .
The period . at the end of the command tells Docker to use the Dockerfile in the current directory.
Step 4: Verify the Image Creation After the build process completes, verify that the image app1 has been created successfully by listing all images:
docker images
You should see app1 in the list of images.
Step 5: Use the Image Now, you can use the image app1 to run containers or push it to a container registry if needed.
Teddy
4 days agoBrande
13 days agoEvangelina
20 days agoJerry
28 days agoTitus
29 days agoJulene
1 months agoCharlene
1 months agoMalcolm
2 months agoWeldon
2 months agoSelma
2 months agoBuddy
2 months agoAlfred
3 months agoJesusita
3 months agoAnnabelle
3 months agoNell
3 months agoCammy
3 months agoZona
4 months agoPaulina
4 months agoBrock
4 months agoNohemi
4 months agoGlory
4 months agoRoselle
5 months agoStevie
5 months agoClaudia
5 months agoAlecia
6 months agoCecilia
7 months agoXochitl
7 months agoKenny
8 months ago