Update LAB_AK_07_Implementing_and_configuring_network_infrastructure_…

[TomaszWieczorkowski]

…services_in_Windows Server.md

Guys, really? Who wrote this "On SEA-ADM1, switch back to the Ethernet Status window, and then select Disable. Back in the Network and Sharing Center window, select Change adapter settings, select Ethernet, and then select Enable this network device." ??? When you do that on a real life server - Disable Network interface to obtain a new IP from the DHCP - you just disconnected yourself from the server and you won't be able to login again. You just lost you access. If the server is in a far remote location where there is no one from IT on site and there is no Out-Of-Band Management network/ILO you just found yourself a back and forth trip there to manually enable the interface. Who wrote that ??? It should be "To release and renew the IP address from the DHCP run from CMD/PowerShell ipconfig /release and next ipconfig /renew.

Module: 00

Lab/Demo: 00

Fixes # .

Changes proposed in this pull request:

-

-

[JeffKoMS]

The step is to test the DHCP service installed in the lab. You suggested to use ipconfig /release in your note in the PR, but that does essentially the same thing as disabling the interface. ipconfig /release scopes to a local address and will essentially kill your RDP session so you won't be able to enter the ipconfig /renew command. The steps, as written, work in the lab and will test if the DHCP service is working. Suggest just closing this PR.

[TomaszWieczorkowski]

JeffKoMS

The Microsoft trainings for a lot of money are to educat people of how to work and do things on REAL LIFE environments not how to do that on HOME LAB only for fun to play with kids where you have access to everything and you can even delete the whole server to check if it will get a new IP next time when build.

If someone do not understand that - that the Microsoft trainings are to prepare people for a real life work not for fun - then such person should not create any training meterials there.

Disabling the network interface on PRODUCTION or TEST environment in a real life will result in lost access to the server and it is one big NO GO in any reasonable IT. If the server is thousands miles away what would you do? Pay thousands of $ and days to bring back the network interface up (if there is no Out-of-band management of the server available) ?

Tomasz

---

Od: JeffKoMS @.> Wysłane: czwartek, 15 grudnia 2022 18:13 Do: MicrosoftLearning/AZ-800-Administering-Windows-Server-Hybrid-Core-Infrastructure @.> DW: Tomasz Wieczorkowski @.>; Author @.> Temat: Re: [MicrosoftLearning/AZ-800-Administering-Windows-Server-Hybrid-Core-Infrastructure] Update LAB_AK_07_Implementing_and_configuring_networkinfrastructure… (PR #46)

The step is to test the DHCP service installed in the lab. You suggested to use ipconfig /release in your note in the PR, but that does essentially the same thing as disabling the interface. ipconfig /release scopes to a local address and will essentially kill your RDP session so you won't be able to enter the ipconfig /renew command. The steps, as written, work in the lab and will test if the DHCP service is working. Suggest just closing this PR.

— Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftLearning/AZ-800-Administering-Windows-Server-Hybrid-Core-Infrastructure/pull/46#issuecomment-1353423695, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ARGTMERNASHCYJYB57FZWLDWNNGT5ANCNFSM566T7LWQ. You are receiving this because you authored the thread.Message ID: @.***>

[TJGitHubUser]

Thank you for the feedback. This can certainly be looked at, but the PR cannot be merged as it currently is. Will close the PR accordingly.