Configure Secure RDP using a Windows Bastion Host: Challenge Lab Reviews

the vm options are not there to select for windows server

Ronak S. · Reviewed 3 ay ago

Disha V. · Reviewed 3 ay ago

quoc h. · Reviewed 3 ay ago

Ankur K. · Reviewed 3 ay ago

the vm options are not there to select for windows server

Ronak S. · Reviewed 3 ay ago

Farid Tri W. · Reviewed 3 ay ago

Nikko A. · Reviewed 3 ay ago

Gary D. · Reviewed 3 ay ago

Fernando M. · Reviewed 3 ay ago

Fernando M. · Reviewed 3 ay ago

Mphethe Andries M. · Reviewed 3 ay ago

patrick s. · Reviewed 3 ay ago

Fernando M. · Reviewed 3 ay ago

David Carlos P. · Reviewed 3 ay ago

Anton T. · Reviewed 3 ay ago

Joaquín Alonso S. · Reviewed 3 ay ago

Zakaria M. · Reviewed 3 ay ago

Completed

MG S. · Reviewed 3 ay ago

José R. · Reviewed 3 ay ago

Anamika N. · Reviewed 3 ay ago

Aj_Myway V. · Reviewed 3 ay ago

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. · Reviewed 3 ay ago

Bhalchandra K. · Reviewed 3 ay ago

Dzikri N. · Reviewed 3 ay ago

johan v. · Reviewed 3 ay ago