关于“使用 Windows 堡垒主机配置安全 RDP：实验室挑战赛”的评价

the vm options are not there to select for windows server

Ronak S. · 已于 3 months前审核

Disha V. · 已于 3 months前审核

quoc h. · 已于 3 months前审核

Ankur K. · 已于 3 months前审核

the vm options are not there to select for windows server

Ronak S. · 已于 3 months前审核

Farid Tri W. · 已于 3 months前审核

Nikko A. · 已于 3 months前审核

Gary D. · 已于 3 months前审核

Fernando M. · 已于 3 months前审核

Fernando M. · 已于 3 months前审核

Mphethe Andries M. · 已于 3 months前审核

patrick s. · 已于 3 months前审核

Fernando M. · 已于 3 months前审核

David Carlos P. · 已于 3 months前审核

Anton T. · 已于 3 months前审核

Joaquín Alonso S. · 已于 3 months前审核

Zakaria M. · 已于 3 months前审核

Completed

MG S. · 已于 3 months前审核

José R. · 已于 3 months前审核

Anamika N. · 已于 3 months前审核

Aj_Myway V. · 已于 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. · 已于 3 months前审核

Bhalchandra K. · 已于 3 months前审核

Dzikri N. · 已于 3 months前审核

johan v. · 已于 3 months前审核