|
|
|
|
|
by jm4
2524 days ago
|
|
It hasn’t been that bad for me. I give them an updated user count and tell them what else I’m using once per year and they give me a bill. They’ve never pushed back on anything. We start with a conference call, I send over a spreadsheet and that’s it. They have software I can run on my network, but they have always let me give them the numbers from my asset tracking system. Frankly, they’re one of the easiest software vendors I deal with. |
|
A Microsoft shop needs licenses for each laptop/desktop running windows, but in an office using Microsoft Server to operate its LAN and the requisite services - DNS, DHCP, SMB file sharing, VPN, email, etc - basically any device that touches the Windows Server machine needs a Client Access Licences (CAL), which is available in user-based and device-based flavors.
Let's say the company operates a website and has developers. The development/QA environment requires an (expensive) MSDN account (or whatever it's called now) per-developer. In production, unlimited anonymous/unauthenticated users are allowed to hit IIS (web server). Authenticated access by employees to IIS needs a user CAL, authenticated customer access requires an External Connector (EC) license. But don't worry, the backing MS SQL Server database for the website also needs to be licensed, with per-cpu-core-per-machine licensing available. Except everything's a VM theses day, so the servers sit on top of a VM host (Microsoft Hyper-V), so there's some additional licensing intricacy there to deal with.
On top of that, there's the Services Provider License Agreement (SPLA) licensing model available for ISVs, but OEM licenses cannot coexist wth SPLA licensing on the same system (VMs + host).
Just to make it more fun, different Microsoft reps will have different answers on how some of the more subtle intricacies even apply!
https://www.microsoft.com/en-us/licensing/product-licensing/...
https://www.microsoft.com/en-us/licensing/licensing-programs...