If you think this is bad, then you haven't tried navigating the MS academic offerings. Over the last 10 or so years, I think it's been called "dreamspark", "imagine", "MSDN Academic Alliance" (I liked this one, it actually made sense), "MSDN AA", and now "Azure Dev Tools for Teaching" or "adt4t" when talking with support.
rant mode ON
Everytime the name is changed, it seems something else changes (OK it's a new product) and the way to access installers and activate it differs. I just want to teach, but every couple of years I have to spend days trying to figure out how to get my iso's and how to renew the subscription. A couple of years ago, and mind you this was after I had had an active academic relationship with Microsoft for 8 years, and my predecessor even longer than that before me, we had to submit invoices proving that the school owned the domainname for our emails and website, as well as a letter from the ministry of education that we were licensed to teach this course.
The support staff is very professional and helpful, and we've always been able to resolve renewal issues. But each year we have to go through the process of getting through a maze of support pages linking to chatbots, to find the correct form to contact support. I think the link to support form had the text "Beware of the leopard".
Only it comes standard with the multiyear bugs only just patched in remote desktop for windows, like an inability to remember where you monitors have always been.
I use RDP app today to log on to my Pc remotely by using vpn to my home network. It looks like they are adding bloat for services that I have zero interest in. Or maybe they are adding authentication services so the vpn wouldn't be necessary.
How can they expect regular people to remember what the Windows app does? It would seriously be better to pick a word at random than to overload the meaning of "Windows" again.
Here are some way better names right off the top of my head:
They literally ran out of ideas, like, 20 years ago?
They've just been trying to say random-ass shit to justify their marketing budget since then.
Windows basically stopped around 7 and mostly went backwards, and when is the last time you thought about the version of office you use? Do you even use office, or can you get by with google docs?
OneDrive is by far more of a pain in the ass than anything else, nobody ever WANTS to use it, they mostly get hijacked by it early on and try to ignore it like a masturbating hobo on a subway car.
It's like how they made the Xbox, then the Xbox one, then the Xbox one X, then the Xbox series X. (Yeah there were other options between/simultaneous, but this sequence is a nice clean illustration.)
The Android version of the app still has the zoom/cursor offset bug when using a software keyboard from when they sunset RDP 8. That has been a severe usability bug for over three years now.
If you would read the article you would know that the title is perfectly correct, as currently it's only available to Win, other platforms are just planned.
It's an RDP client you can connect to pcs on the network or vms on azure
Gold medal of tautology.
At this point, people still using windows voluntarily don't deserve any better. And IT departments having a choice but forcing windows on users deserve to be burned at the stake.
Ah yes, the always shitty, "I know everything because I am that business and person all the time and better than them." Shit fucking comment.
At this point people who are like, "just use Linux" sound like, "just buy an iPhone." The only difference is the Linux people don't end up actually knowing shit about enterprise environments
I will get down voted because Lemmy is an Echo Chamber with people circle jerking their self justified opinions.
But seriously fuck off, dude. Anyone that literally says this doesn't know shit about an actual environment.
Let me know when fucking Oracle's shitty products work better on Linux boxes over Windows when their own fucking Linux products don't work. I will go to the business I am a part of right now and let them know we should just hire you to make all of our financial and enterprise setup choices because you said so.
But they don't have to make any OS "office-wide". All they have to do is
move from a centralized micro-management of every workstation to a scenario where users can be provided a prepared workstation, but may configure one themselves
transition to a security policy that assumes every single workstation is insecure, and regulate the network traffic to allow only those protocols that are required for the business, protecting each machine from the next (this would prevent so many major security incidents where a single machine gets compromised and then the whole network is affected)
provide central infrastructure as open protocols - IMAP (or POP3/SMTP), HTTPS, FTPS + file & printer sharing as desired
enforce open formats within the enterprise
If necessary (assuming you have really irresponsible users), before authorizing users to set up their own machine, they can do a qualification check - or have the user's line manager approve the "individual setup".
This would enable power users productivity and even if you don't change anything for the vast amount of users, it would pay off rapidly. If you can move regular workstations away from the bloatware that is Windows, you would boost the overall productivity immensely.
Specifically, what I am arguing against is:
locking users into an eco-system for any kind of service (e.g. MS Exchange servers, MS Active Directory)
outsourcing your IT competences to Microsoft (because let's be real, that's the actual reason IT departments go for Microsoft: corporate IT is outsourced as a service, this means lowest bidder, and the lowest bidder will happily take Microsoft's offer to take care of any "real" issues and only provide a really, really dumb and helpless first level support)
having tons of services listening on every workstation that no one ever needs (just open your windows control panel (while it's still around) and check out all the running services, of which you could disable > 50% if Windows would let you, without impacting the operational state of your machine) and each one presenting a vulnerable interface to the network
Much more interesting is the part about Relayed RDP Shortpath. With STUN and TURN and even a relay it sounds like this will enable some usecases similar to TeamViewer