Configurer une session RDP sécurisée à l'aide d'un hôte bastion Windows : atelier challenge avis

the vm options are not there to select for windows server

Ronak S. · Examiné il y a 3 mois

Disha V. · Examiné il y a 3 mois

quoc h. · Examiné il y a 3 mois

Ankur K. · Examiné il y a 3 mois

the vm options are not there to select for windows server

Ronak S. · Examiné il y a 3 mois

Farid Tri W. · Examiné il y a 3 mois

Nikko A. · Examiné il y a 3 mois

Gary D. · Examiné il y a 3 mois

Fernando M. · Examiné il y a 3 mois

Fernando M. · Examiné il y a 3 mois

Mphethe Andries M. · Examiné il y a 3 mois

patrick s. · Examiné il y a 3 mois

Fernando M. · Examiné il y a 3 mois

David Carlos P. · Examiné il y a 3 mois

Anton T. · Examiné il y a 3 mois

Joaquín Alonso S. · Examiné il y a 3 mois

Zakaria M. · Examiné il y a 3 mois

Completed

MG S. · Examiné il y a 3 mois

José R. · Examiné il y a 3 mois

Anamika N. · Examiné il y a 3 mois

Aj_Myway V. · Examiné il y a 3 mois

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. · Examiné il y a 3 mois

Bhalchandra K. · Examiné il y a 3 mois

Dzikri N. · Examiné il y a 3 mois

johan v. · Examiné il y a 3 mois