We will be using terminal services in a redundant setup so at least 10 RDS cals
Terminal SERVICES doesn't require more CALs when redundancy. But if you mean your TERMINALS (the thin clients) will be redundant, then it will.
One CAL gives you access to unlimited RDS servers.
RDS CALs are also concurrent, aren't they? Or did they change that?
Had this discussion a few years ago. From my understanding, RDS has a "pool" that grabs a license from the pool for each logged in user. It will re-up every 90 days each time the user logs in. So if you have multiple users that only log in once every 89 days, that can waste a ton of licenses, thus having to purchase more than actually is required.
Yeah, all that sounds familar - but don't new (users who haven't tried in the last 89 days) get a 90 temp license? So I would think/hope you wouldn't run afoul of the single off man off once in a while.
It looks like the temp license is only available in Device mode.
From the site you linked:
There is a licensing grace period of 120 Days during which no license server is required.
in combination with
Temporary RDS CALs are not available.
tells me each user likely gets a single 120 day grace, after which they will have to have a license.
this also seems newer than I recall.
RDS CALs are assigned to a user in Active Directory.
Does this mean it's not longer concurrent users? Once an RDS license is assigned, it's there for life? what happens when that user leaves the company?
And then we toss this on top of the pile.
When you use the Per User model, licensing is not enforced and each user is granted a license to connect to an RD Session Host from any number of devices. The license server issues licenses from the available RDS CAL pool or the Over-Used RDS CAL pool. It's your responsibility to ensure that all of your users have a valid license and zero Over-Used CALs—otherwise, you're in violation of the Remote Desktop Services license terms.
So it's basically back on you to track your licenses.
It was never concurrent. MS has always been really clear that concurrent isn't a concept. It's "all users that use the service" within a sliding 90 day period.
I thought about paying for DuoLingo because I can't stand the ads all the time and lack of freedom.
But lately I have been doing a lot on Anki. There's some really great decks in there. I also paired it with Mango which has been great as well. Another one that is great is Beelingual when you want to start doing more reading.
My DuoLingo stopped showing ads a while ago. No idea why.
Facebook is planning to hire 10,000 people in the European Union to develop a so-called metaverse.
A metaverse is an online world where people can game, work and communicate in a virtual environment, often using VR headsets. Facebook CEO Mark Zuckerberg has been a leading voice on the concept. The announcement comes as Facebook deals with the fallout of a damaging scandal and faces increased calls for regulation to curb its influence. "The metaverse has the potential to help unlock access to new creative, social, and economic opportunities. And Europeans will be shaping it right from the start," Facebook said in a blog post. The new jobs being created over the next five years will include "highly specialised engineers".
their remaking 2nd life?
yeah - it's totally going to work this time.
@jaredbusch That is the correct way and the way it's done in most manufacturing plants in the U.S. and International. That has been best practice for the last 25-30 years. I am in 8-10 different manufacturing plants [per week as a consultant and that's how it done.
That's awesome that the plants you work for do it that way - but I agree with JB - it's likely not that common in reality.
Hell - the sure number of SCADA systems on the internet in mind boggling.
This is the solution that my customer went in blindly with and got burned because it didn't have an agent to talk to their applications and their systems were corrupted in a totally predictable way. It's an amazing product, but no product can bypass the system admin's need to know their workloads.
So what your saying is even though they had something backing up blindly on the Hypervisor level (i.e backs up the whole VM), and no agent. Their application kind of corrupted it, so when the VM restored the application just crapped out 😁
As already mentioned this is why you need to test and restore 😁.
We're bad at this at the moment, but in the process of planning a DR exercise.