安装 Steam
登录
|
语言
繁體中文(繁体中文)
日本語(日语)
한국어(韩语)
ไทย(泰语)
български(保加利亚语)
Čeština(捷克语)
Dansk(丹麦语)
Deutsch(德语)
English(英语)
Español-España(西班牙语 - 西班牙)
Español - Latinoamérica(西班牙语 - 拉丁美洲)
Ελληνικά(希腊语)
Français(法语)
Italiano(意大利语)
Bahasa Indonesia(印度尼西亚语)
Magyar(匈牙利语)
Nederlands(荷兰语)
Norsk(挪威语)
Polski(波兰语)
Português(葡萄牙语 - 葡萄牙)
Português-Brasil(葡萄牙语 - 巴西)
Română(罗马尼亚语)
Русский(俄语)
Suomi(芬兰语)
Svenska(瑞典语)
Türkçe(土耳其语)
Tiếng Việt(越南语)
Українська(乌克兰语)
报告翻译问题



Yes, it's pretty useful, especially for IT and network engineers. I still haven't tested it myself to know how it works on remote connections or cloud services.
But it probably has the ability to log in with multiple users, with one IT engineer logging in only to the core environment (to reduce server and VDI consumed resources) and starting to write Python or shell scripts, while another engineer logs in with another user on a normal desktop to manage the domain.
In short, it's easier to multitask, multi-user, multi-monitor, etc. on a single Windows image inside VDI. This is something I expect Task View should do; I'm not sure if it can do it right now or with further updates.
Also, multi-monitor can be very useful for streamers too, like they have one specific desktop/monitor for their main screen and another desktop/monitor to see the chats.
---------------------------------------------------------------------------
What Microsoft is trying to do is to fulfill its lack of bringing Linux engineers to Microsoft. For example: