Mengonfigurasi RDP yang Aman Menggunakan Bastion Host Windows: Challenge Lab Ulasan

the vm options are not there to select for windows server

Ronak S. · Diulas 3 bulan lalu

Disha V. · Diulas 3 bulan lalu

quoc h. · Diulas 3 bulan lalu

Ankur K. · Diulas 3 bulan lalu

the vm options are not there to select for windows server

Ronak S. · Diulas 3 bulan lalu

Farid Tri W. · Diulas 3 bulan lalu

Nikko A. · Diulas 3 bulan lalu

Gary D. · Diulas 3 bulan lalu

Fernando M. · Diulas 3 bulan lalu

Fernando M. · Diulas 3 bulan lalu

Mphethe Andries M. · Diulas 3 bulan lalu

patrick s. · Diulas 3 bulan lalu

Fernando M. · Diulas 3 bulan lalu

David Carlos P. · Diulas 3 bulan lalu

Anton T. · Diulas 3 bulan lalu

Joaquín Alonso S. · Diulas 3 bulan lalu

Zakaria M. · Diulas 3 bulan lalu

Completed

MG S. · Diulas 3 bulan lalu

José R. · Diulas 3 bulan lalu

Anamika N. · Diulas 3 bulan lalu

Aj_Myway V. · Diulas 3 bulan lalu

Followed instructions, but after creating `vm-bastionhost` with the appropriate NICs, it refused to credit me for it. I understand I may have done something wrong, but by every measurable metric I have access to, it was correct. The name and region were accurate to the course expectation, the first NIC was the external NIC with the correct firewall rule, the second was the default internal NIC, and the instance was a 2016 Windows Server instance with Desktop Experience. Really sure sure what was wrong and there was no indicator of what point was mistaken. Turns out, the firewall rule to enable 3389 ingress traffic has to be custom created. You can't use the one that already exists. This is a frustrating requirement since the two are synonymous. There's no difference. It seems to just be an issue with the test validator.

Michael B. · Diulas 3 bulan lalu

Bhalchandra K. · Diulas 3 bulan lalu

Dzikri N. · Diulas 3 bulan lalu

johan v. · Diulas 3 bulan lalu