I can't even
-
@scottalanmiller said in I can't even:
@bigbear said in I can't even:
@eddiejennings said in I can't even:
@bigbear said in I can't even:
@scottalanmiller said in I can't even:
Claims he knows nothing about what a CAL is. But also claims that he knows that he's never needed them. How he can know so little but then know so much... makes no sense. He's an IT Service Provider, but doesn't know the most basic things about using Windows.
https://community.spiceworks.com/topic/2085827-what-exactly-is-a-cal
Probably managing very small environments where he has never had more than 10 connections. I am not sure Windows Server governs CALs very closely, or at all if you dont configure it.
From my experirence with Windows Server (not using remote desktop services), there's no technical limitations regarding CALs. It's pure licensing costs (and revenue).
Like with RDS Cals, its stops working if you dont add them, but with user/connection Cals for clients I dont think its enforced. More of an issue if you get audited.
That's unique to RDS, nothing like Server CALs.
Right but he is talking about user/connection CALs, which you can configure on the server to keep yourself compliant. But it wont stop you from using excess connections if you dont configure it.
-
@bigbear said in I can't even:
@scottalanmiller said in I can't even:
@bigbear said in I can't even:
@eddiejennings said in I can't even:
@bigbear said in I can't even:
@scottalanmiller said in I can't even:
Claims he knows nothing about what a CAL is. But also claims that he knows that he's never needed them. How he can know so little but then know so much... makes no sense. He's an IT Service Provider, but doesn't know the most basic things about using Windows.
https://community.spiceworks.com/topic/2085827-what-exactly-is-a-cal
Probably managing very small environments where he has never had more than 10 connections. I am not sure Windows Server governs CALs very closely, or at all if you dont configure it.
From my experirence with Windows Server (not using remote desktop services), there's no technical limitations regarding CALs. It's pure licensing costs (and revenue).
Like with RDS Cals, its stops working if you dont add them, but with user/connection Cals for clients I dont think its enforced. More of an issue if you get audited.
That's unique to RDS, nothing like Server CALs.
Right but he is talking about user/connection CALs, which you can configure on the server to keep yourself compliant. But it wont stop you from using excess connections if you dont configure it.
Can, but if he configured them on the server, then he's have been aware of them. And that's purely a voluntary step, it's not a requirement or automated in any way. It's not even obvious that that exists. You have to go looking for it.
-
@bigbear said in I can't even:
@scottalanmiller said in I can't even:
@bigbear said in I can't even:
@eddiejennings said in I can't even:
@bigbear said in I can't even:
@scottalanmiller said in I can't even:
Claims he knows nothing about what a CAL is. But also claims that he knows that he's never needed them. How he can know so little but then know so much... makes no sense. He's an IT Service Provider, but doesn't know the most basic things about using Windows.
https://community.spiceworks.com/topic/2085827-what-exactly-is-a-cal
Probably managing very small environments where he has never had more than 10 connections. I am not sure Windows Server governs CALs very closely, or at all if you dont configure it.
From my experirence with Windows Server (not using remote desktop services), there's no technical limitations regarding CALs. It's pure licensing costs (and revenue).
Like with RDS Cals, its stops working if you dont add them, but with user/connection Cals for clients I dont think its enforced. More of an issue if you get audited.
That's unique to RDS, nothing like Server CALs.
Right but he is talking about user/connection CALs...
Best to call them Windows Server CALs. There is no connection CAL.
-
@scottalanmiller said in I can't even:
@bigbear said in I can't even:
@scottalanmiller said in I can't even:
@bigbear said in I can't even:
@eddiejennings said in I can't even:
@bigbear said in I can't even:
@scottalanmiller said in I can't even:
Claims he knows nothing about what a CAL is. But also claims that he knows that he's never needed them. How he can know so little but then know so much... makes no sense. He's an IT Service Provider, but doesn't know the most basic things about using Windows.
https://community.spiceworks.com/topic/2085827-what-exactly-is-a-cal
Probably managing very small environments where he has never had more than 10 connections. I am not sure Windows Server governs CALs very closely, or at all if you dont configure it.
From my experirence with Windows Server (not using remote desktop services), there's no technical limitations regarding CALs. It's pure licensing costs (and revenue).
Like with RDS Cals, its stops working if you dont add them, but with user/connection Cals for clients I dont think its enforced. More of an issue if you get audited.
That's unique to RDS, nothing like Server CALs.
Right but he is talking about user/connection CALs, which you can configure on the server to keep yourself compliant. But it wont stop you from using excess connections if you dont configure it.
Can, but if he configured them on the server, then he's have been aware of them. And that's purely a voluntary step, it's not a requirement or automated in any way. It's not even obvious that that exists. You have to go looking for it.
Right, but always felt it was odd compared to the way Microsoft enforces other licenses, Exchange is another example. Dont have them, they dont work.
-
@scottalanmiller said in I can't even:
@bigbear said in I can't even:
@scottalanmiller said in I can't even:
@bigbear said in I can't even:
@eddiejennings said in I can't even:
@bigbear said in I can't even:
@scottalanmiller said in I can't even:
Claims he knows nothing about what a CAL is. But also claims that he knows that he's never needed them. How he can know so little but then know so much... makes no sense. He's an IT Service Provider, but doesn't know the most basic things about using Windows.
https://community.spiceworks.com/topic/2085827-what-exactly-is-a-cal
Probably managing very small environments where he has never had more than 10 connections. I am not sure Windows Server governs CALs very closely, or at all if you dont configure it.
From my experirence with Windows Server (not using remote desktop services), there's no technical limitations regarding CALs. It's pure licensing costs (and revenue).
Like with RDS Cals, its stops working if you dont add them, but with user/connection Cals for clients I dont think its enforced. More of an issue if you get audited.
That's unique to RDS, nothing like Server CALs.
Right but he is talking about user/connection CALs...
Best to call them Windows Server CALs. There is no connection CAL.
User/Device not connection... sorry
-
@bigbear said in I can't even:
@scottalanmiller said in I can't even:
@bigbear said in I can't even:
@scottalanmiller said in I can't even:
@bigbear said in I can't even:
@eddiejennings said in I can't even:
@bigbear said in I can't even:
@scottalanmiller said in I can't even:
Claims he knows nothing about what a CAL is. But also claims that he knows that he's never needed them. How he can know so little but then know so much... makes no sense. He's an IT Service Provider, but doesn't know the most basic things about using Windows.
https://community.spiceworks.com/topic/2085827-what-exactly-is-a-cal
Probably managing very small environments where he has never had more than 10 connections. I am not sure Windows Server governs CALs very closely, or at all if you dont configure it.
From my experirence with Windows Server (not using remote desktop services), there's no technical limitations regarding CALs. It's pure licensing costs (and revenue).
Like with RDS Cals, its stops working if you dont add them, but with user/connection Cals for clients I dont think its enforced. More of an issue if you get audited.
That's unique to RDS, nothing like Server CALs.
Right but he is talking about user/connection CALs...
Best to call them Windows Server CALs. There is no connection CAL.
User/Device not connection... sorry
Those are the ways you can license the CALs. But there are Server CALs specifically that he is talking about. Even though he doesn't know the name of them.
-
@scottalanmiller said in I can't even:
@bigbear said in I can't even:
@scottalanmiller said in I can't even:
@bigbear said in I can't even:
@scottalanmiller said in I can't even:
@bigbear said in I can't even:
@eddiejennings said in I can't even:
@bigbear said in I can't even:
@scottalanmiller said in I can't even:
Claims he knows nothing about what a CAL is. But also claims that he knows that he's never needed them. How he can know so little but then know so much... makes no sense. He's an IT Service Provider, but doesn't know the most basic things about using Windows.
https://community.spiceworks.com/topic/2085827-what-exactly-is-a-cal
Probably managing very small environments where he has never had more than 10 connections. I am not sure Windows Server governs CALs very closely, or at all if you dont configure it.
From my experirence with Windows Server (not using remote desktop services), there's no technical limitations regarding CALs. It's pure licensing costs (and revenue).
Like with RDS Cals, its stops working if you dont add them, but with user/connection Cals for clients I dont think its enforced. More of an issue if you get audited.
That's unique to RDS, nothing like Server CALs.
Right but he is talking about user/connection CALs...
Best to call them Windows Server CALs. There is no connection CAL.
User/Device not connection... sorry
Those are the ways you can license the CALs. But there are Server CALs specifically that he is talking about. Even though he doesn't know the name of them.
Yeah. I get loose with my language about CALs when I say user and device CALs.
-
And just found a thread where this guy is all concerned about security and his "friends" convinced him that if he used Azure that he could ignore all security when writing his application and deploying his database and that Microsoft would take care of anything. Talk about getting set up. That's full on social engineering right there.
-
@eddiejennings said in I can't even:
@scottalanmiller said in I can't even:
@bigbear said in I can't even:
@scottalanmiller said in I can't even:
@bigbear said in I can't even:
@scottalanmiller said in I can't even:
@bigbear said in I can't even:
@eddiejennings said in I can't even:
@bigbear said in I can't even:
@scottalanmiller said in I can't even:
Claims he knows nothing about what a CAL is. But also claims that he knows that he's never needed them. How he can know so little but then know so much... makes no sense. He's an IT Service Provider, but doesn't know the most basic things about using Windows.
https://community.spiceworks.com/topic/2085827-what-exactly-is-a-cal
Probably managing very small environments where he has never had more than 10 connections. I am not sure Windows Server governs CALs very closely, or at all if you dont configure it.
From my experirence with Windows Server (not using remote desktop services), there's no technical limitations regarding CALs. It's pure licensing costs (and revenue).
Like with RDS Cals, its stops working if you dont add them, but with user/connection Cals for clients I dont think its enforced. More of an issue if you get audited.
That's unique to RDS, nothing like Server CALs.
Right but he is talking about user/connection CALs...
Best to call them Windows Server CALs. There is no connection CAL.
User/Device not connection... sorry
Those are the ways you can license the CALs. But there are Server CALs specifically that he is talking about. Even though he doesn't know the name of them.
Yeah. I get loose with my language about CALs when I say user and device CALs.
It's tough because it is "User Server CALs" and "Device Server CALs."
-
And most people think that it is just SMB protocol or AD that needs CALs, but it is everything. From DNS and DHCP to web apps running on the machine to people connection to Linux machines running as VMs on top of VirtualBox on top of Windows Server - because those are just "more apps on top" and not a special case. It's amazing how many ways people connect to servers and don't acknowledge it.
-
@scottalanmiller said in I can't even:
And most people think that it is just SMB protocol or AD that needs CALs, but it is everything. From DNS and DHCP to web apps running on the machine to people connection to Linux machines running as VMs on top of VirtualBox on top of Windows Server - because those are just "more apps on top" and not a special case. It's amazing how many ways people connect to servers and don't acknowledge it.
When explaining that, I can usually mitigate the panic by letting folks know that having a Windows Server CAL covers you for pretty much all the services. Getting a CAL for User A means they can use SMB shares, AD, DNS, etc. without having to have a separate CAL for each service. ... Then we get to Exchange
-
@eddiejennings said in I can't even:
@scottalanmiller said in I can't even:
And most people think that it is just SMB protocol or AD that needs CALs, but it is everything. From DNS and DHCP to web apps running on the machine to people connection to Linux machines running as VMs on top of VirtualBox on top of Windows Server - because those are just "more apps on top" and not a special case. It's amazing how many ways people connect to servers and don't acknowledge it.
When explaining that, I can usually mitigate the panic by letting folks know that having a Windows Server CAL covers you for pretty much all the services. Getting a CAL for User A means they can use SMB shares, AD, DNS, etc. without having to have a separate CAL for each service. ... Then we get to Exchange
LOL, and that makes them feel better? People are seriously sheep.
-
-
-
@scottalanmiller said in I can't even:
@eddiejennings said in I can't even:
@scottalanmiller said in I can't even:
And most people think that it is just SMB protocol or AD that needs CALs, but it is everything. From DNS and DHCP to web apps running on the machine to people connection to Linux machines running as VMs on top of VirtualBox on top of Windows Server - because those are just "more apps on top" and not a special case. It's amazing how many ways people connect to servers and don't acknowledge it.
When explaining that, I can usually mitigate the panic by letting folks know that having a Windows Server CAL covers you for pretty much all the services. Getting a CAL for User A means they can use SMB shares, AD, DNS, etc. without having to have a separate CAL for each service. ... Then we get to Exchange
LOL, and that makes them feel better? People are seriously sheep.
Yeah, because they start thinking the need separate CALs for everything. They think they're "getting a deal" with this one CAL covering X stuff
-
-
-
-
unfortunately, dealing with UEFI sometimes makes things not boot, so I'm not surprised by this question.
-
@dashrender said in I can't even:
unfortunately, dealing with UEFI sometimes makes things not boot, so I'm not surprised by this question.
Picture is a link. He posted a screenshot that is obvious he is choosing upgrade.
