Opiniones sobre Configura el RDP seguro con un host de bastión de Windows: Lab de desafío

the vm options are not there to select for windows server

Ronak S. · Se revisó hace 3 meses

Disha V. · Se revisó hace 3 meses

quoc h. · Se revisó hace 3 meses

Ankur K. · Se revisó hace 3 meses

the vm options are not there to select for windows server

Ronak S. · Se revisó hace 3 meses

Farid Tri W. · Se revisó hace 3 meses

Nikko A. · Se revisó hace 3 meses

Gary D. · Se revisó hace 3 meses

Fernando M. · Se revisó hace 3 meses

Fernando M. · Se revisó hace 3 meses

Mphethe Andries M. · Se revisó hace 3 meses

patrick s. · Se revisó hace 3 meses

Fernando M. · Se revisó hace 3 meses

David Carlos P. · Se revisó hace 3 meses

Anton T. · Se revisó hace 3 meses

Joaquín Alonso S. · Se revisó hace 3 meses

Zakaria M. · Se revisó hace 3 meses

Completed

MG S. · Se revisó hace 3 meses

José R. · Se revisó hace 3 meses

Anamika N. · Se revisó hace 3 meses

Aj_Myway V. · Se revisó hace 3 meses

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. · Se revisó hace 3 meses

Bhalchandra K. · Se revisó hace 3 meses

Dzikri N. · Se revisó hace 3 meses

johan v. · Se revisó hace 3 meses