3 ms·
> In enterprise agreements, you need to buy Windows licenses for MacOS devices too. Why would you tell Microsoft that you've bought some Macs? It's not like th
by grishka 5y ago
> In enterprise agreements, you need to buy Windows licenses for MacOS devices too.
Why would you tell Microsoft that you've bought some Macs? It's not like they're the IRS, they're just a company. They have no business to know any of this.
- Spooky23 5y agoWhen you enter into an EA, you agree to report annually on the census of devices that meet that criteria. Also, you need CALs to use Windows server based services like AD and file servers (unless you’re using a NAS)
- grishka 5y agoWell, if those devices use Windows server based services, then it makes more sense. But if they do not, Microsoft would have no way to know about their existence.
- wolrah 5y ago> Well, if those devices use Windows server based services, then it makes more sense. But if they do not, Microsoft would have no way to know about their existence. Yes, that's exactly how it works. Windows Server Client Access Licenses (CALs) are sold either by user or by device. User licenses allow one person to use any Windows Server hosted services in the organization from any device. Device licenses allow any number of people to use any Windows Server hosted services from one specific device. If you have a bunch of users with their own personal computers and potentially other devices like a normal office the user CAL model usually makes the most sense, but for environments like classrooms or multi-shift businesses where you have significantly more devices than users the device CAL model can sometimes be beneficial. The catch is that almost any use of Windows services requires a CAL and that includes DHCP/DNS. If you host either of those services primarily from Windows the device count suddenly changes significantly.