Configure um RDP seguro usando um Bastion Host Windows: laboratório com desafio avaliações

the vm options are not there to select for windows server

Ronak S. · Revisado há 3 months

Disha V. · Revisado há 3 months

quoc h. · Revisado há 3 months

Ankur K. · Revisado há 3 months

the vm options are not there to select for windows server

Ronak S. · Revisado há 3 months

Farid Tri W. · Revisado há 3 months

Nikko A. · Revisado há 3 months

Gary D. · Revisado há 3 months

Fernando M. · Revisado há 3 months

Fernando M. · Revisado há 3 months

Mphethe Andries M. · Revisado há 3 months

patrick s. · Revisado há 3 months

Fernando M. · Revisado há 3 months

David Carlos P. · Revisado há 3 months

Anton T. · Revisado há 3 months

Joaquín Alonso S. · Revisado há 3 months

Zakaria M. · Revisado há 3 months

Completed

MG S. · Revisado há 3 months

José R. · Revisado há 3 months

Anamika N. · Revisado há 3 months

Aj_Myway V. · Revisado há 3 months

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. · Revisado há 3 months

Bhalchandra K. · Revisado há 3 months

Dzikri N. · Revisado há 3 months

johan v. · Revisado há 3 months