Tsplus App Download !!TOP!!
Demarcus Smith
With Tsplus remote app here to stay, companies now have to battle with how it shapes business processes, culture, and IT systems into the future. The companies who are proactive, investing in nascent technologies, cloud-based access, and agile infrastructure, will be better prepared to weather future challenges than those who shy away from the challenge.
How prepared was your organization for the sudden shift to working from home? Did you already have a plan in place for events like this? Were your employees able to seamlessly transition to remote working? Or were you clambering for a solution in the moment?
This was a challenge for many companies. IT teams had to ensure that access to data and applications was carefully managed and that data leaks could be avoided. They also had to massively scale up access to core systems and applications while remaining IT compliant. They had to do all of this overnight, with no real room for testing and risk assessment.
Visibility and control are paramount to keeping things working today and enabling your business to thrive in the future. During times of crisis, visibility and control are even more essential because you are more vulnerable to threats. Here are some of the technologies that can cultivate greater visibility and control for IT systems in a Tsplus 2fa remote working environment:
I realize you are interested in the Server side of things, but I bring this up because, IMO, any company that is promoting that they can do the above, which is a clear violation of licensing, isn't to be trusted in what they say about licensing for any other product, like Server.
But, for Server, the MS licensing talks about "Windows Server RemoteDesktop Services". I am not a lawyer. If your lawyer says that "Windows Server RemoteDesktop Services" only means those services created by MS and used inside Server then they may well be right. My (non-legal) reading of it is that remote desktop access of any type is what they mean.
So, my opinion is that you need RDS CALs for Server if you are accessing it in this way. Again, I am not a lawyer and do not work for the MS licensing department, so my opinion is just that - an opinion. Talk to your lawyer and do what makes sense for your company.
And the MS opinion, well, that will depend on who you talk to. MS is a huge company and you get different answers sometimes, depending on who you talk to. That's why it usually makes sense to read the licensing and talk to a lawyer if there's any doubt.
I did not look after Windows 10. I was looking after Windows server 2016. What is definition of loophole here "had a loophole and would be okay to use the software." Is that something like Oracle is saying for softpartitioning on the web and nothing in EULA or contract??? And yes, lawyers went after Oracle and won where Oracle had to retract since no licensing violation was done.
"his own lawyers and decided that they had a loophole" --> not really, there is no loophole. No one from MS was able to give clear answer same as nobody is giving answer clearly how External connector is licensed in multiserver enviroment ???. Once when you put clear EULAs out there it will actually narrow ways for extortion. MS same as Oracle leaving grey areas to play with customers and to see how much money to extract based on size and revenue of the company.
And no, I am not trying to be wise ass or something like that. I just want fair and clean game. That is reason why we always ask vendor officially and if vendor sends unclear answer then we ask again until is 100% clear and in written what is required and why. If vendor is playing dumb, we are good to go. We have proof that we asked and no clear answer is provided by vendor.
Actually, it is based on EULA of the product. I was looking at server products and if I remember, MS changed EULA between 2016 and 2019 if I remember right. So, as far as I understand it and stuff we were getting as explanation, you are good to go with 2016 but not with 2019.
"Device connections. You may allow up to 20 other devices to access the software installed on the licensed device for the purpose of using the following software features: file services, print services, Internet information services, and Internet connection sharing and telephony services on the licensed device. "
So looks like if you configure TSplus to publish apps over web using IIS you are good to go for 20 users ???. Is this loophole? I don't know. But MS wrote this document so ask lawyers what is ambiguity in this case.
Publishing apps isn't allowed though, as stated in another section. IIS wasn't meant for app publication, so... maybe it is a legal loophole. Maybe not. Again, I would say this is lawyer territory. And again, I would remind anyone reading this that MS has a huge legal department so if they do decide to come after you they may just bury you in proceedings because they can afford to do it.
My (non-legal) reading of it is that remote desktop access of any type is what they mean. --> when you are spending somebody's else money, it is easy to buy it "just to make sure". Big vendors in most cases take advantage of these guys. I am simple asking a lot of questions.
Don't forget: Microsoft wrote these documents. If it is unclear, it doesn't matter what they think but what you have understood reading document. Ask lawyers. They will explain to you how this works. They explained to me this way.
"Don't misunderstand or misread the guidance. It's 20 connections, not 20 remote sessions that are allowed, perfect use for a share in a small business." --> If you are utilizing IIS server on Windows 10, what is connection and what is session? Explain it on homepage of IIS server. Is that session or connection? Or what is connection in world of IIS?
df19127ead